Processing commands for cont...@bugs.debian.org:
> fixed 980928 7.4.3+ds-2
Bug #980928 [npm] npm: Installing any package gives "npm ERR! current.merge is
not a function"
Marked as fixed in versions npm/7.4.3+ds-2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
9
Your message dated Tue, 26 Jan 2021 04:48:27 +
with message-id
and subject line Bug#957187: fixed in ezquake 3.2.2-1
has caused the Debian Bug report #957187,
regarding ezquake: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Tue, 26 Jan 2021 04:18:21 +
with message-id
and subject line Bug#979054: fixed in john 1.8.0-3
has caused the Debian Bug report #979054,
regarding src:john: invalid maintainer address
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Processing commands for cont...@bugs.debian.org:
> tags 977054 + ftbfs
Bug #977054 [src:aiorwlock] aiorwlock FTBFS with pytest 6
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
977054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977054
De
Your message dated Tue, 26 Jan 2021 04:03:45 +
with message-id
and subject line Bug#952253: fixed in oneliner-el 0.3.6-9
has caused the Debian Bug report #952253,
regarding oneliner-el: FTBFS: Malformed UTF-8 character (fatal) at
/usr/share/texinfo/Texinfo/ParserNonXS.pm line 3387.
to be mark
Processing commands for cont...@bugs.debian.org:
> tags 973061 + patch
Bug #973061 [src:nototools] nototools: FTBFS: dpkg-buildpackage: error:
dpkg-source -b . subprocess returned exit status 2
Added tag(s) patch.
> found 981009 4.1.2-1
Bug #981009 [charybdis] charybdis abandoned upstream, do not
Your message dated Tue, 26 Jan 2021 03:03:30 +
with message-id
and subject line Bug#979530: fixed in blag-fortune 1.2-2
has caused the Debian Bug report #979530,
regarding src:blag-fortune: invalid maintainer address
to be marked as done.
This means that you claim that the problem has been de
Your message dated Tue, 26 Jan 2021 02:48:32 +
with message-id
and subject line Bug#979055: fixed in extra-xdg-menus 1.0-5
has caused the Debian Bug report #979055,
regarding src:extra-xdg-menus: invalid maintainer address
to be marked as done.
This means that you claim that the problem has b
Package: request-tracker4
Version: 4.4.4-2
Severity: serious
Justification: DFSG
During packaging of RT5 it was noticed that the ckeditor source
shipped in third-party does not correspond to the preferred form
of modification - it is still minified (like that shipped in the main
tarball). This is
Processing commands for cont...@bugs.debian.org:
> # Preparing a QA upload
> tags 979054 + pending
Bug #979054 [src:john] src:john: invalid maintainer address
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
979054: https://bugs.debian.org/cgi
Processing control commands:
> retitle -1 python-scrapy: FTBFS without network access due to
> test_command_check.py
Bug #980901 [src:python-scrapy] python-scrapy: FTBFS in pbuilder without
--use-network=yes due to tests in test_command_check.py
Changed Bug title to 'python-scrapy: FTBFS without
Source: mpi4py
Followup-For: Bug #976404
mpi4py tests seem to have started passing stably on ppc64el after the
upgrade of libpmix2 from 3.2.0-1 to 3.2.1-1
(other test errors after that are other known openmpi problems,
recently fixed, not these timeout errors)
Tests are now passing reliably in b
Your message dated Tue, 26 Jan 2021 01:33:24 +
with message-id
and subject line Bug#979357: fixed in libloki 0.1.7-4
has caused the Debian Bug report #979357,
regarding src:libloki: invalid maintainer address
to be marked as done.
This means that you claim that the problem has been dealt with
Control: tags -1 +help
Quoting Lucas Nussbaum (2020-10-27 18:00:12)
> Source: monero
> Version: 0.16.0.0-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201027 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package fa
Processing control commands:
> tags -1 +help
Bug #973196 [src:monero] monero: FTBFS: optional.hpp:1591:3: error: static
assertion failed: If you want to output boost::optional, include header
Added tag(s) help.
--
973196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973196
Debian Bug Tra
Followup-For: Bug #979301
Control: tag -1 patch pending
Hi,
I've uploaded the attached NMU to DELAYED/5. It updates the package to
debhelper-compat (= 13) and sanitizes the debhelper usage.
Andreas
diff -Nru namazu2-2.0.21/debian/changelog namazu2-2.0.21/debian/changelog
--- namazu2-2.0.21/debi
Processing control commands:
> tag -1 patch pending
Bug #979301 [namazu2-index-tools] namazu2-index-tools: contains namazu.1
manpage after separate arch-indep build
Added tag(s) pending and patch.
--
979301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979301
Debian Bug Tracking System
Con
Your message dated Mon, 25 Jan 2021 23:48:33 +
with message-id
and subject line Bug#979363: fixed in dovecot 1:2.3.13+dfsg1-1
has caused the Debian Bug report #979363,
regarding dovecot: CVE-2020-24386 CVE-2020-25275
to be marked as done.
This means that you claim that the problem has been de
Processing commands for cont...@bugs.debian.org:
> severity 980803 normal
Bug #980803 [qtbase5-examples] The examples don't show up in Qt Creator
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
980803: https://bugs.debian.org/
severity 980803 normal
thanks
Hi!
El vie., 22 ene. 2021 14:23, Limon Kiwi escribió:
> Package: qtbase5-examples
> Version: 5.15.2+dfsg-2
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> Qt Creator 4.14.0 doesn't show the examples after installing the package
On Sat, Jan 02, 2021 at 12:24:05AM +, Debian Bug Tracking System wrote:
> Source: lazr.config
> Source-Version: 2.2.2-1
> Done: Jonas Meurer
[...]
>[ Jonas Meurer ]
>* New upstream release. (Closes: #971093)
>* d/control:
> - Add myself to Uploaders
> - Remove Barry Warsa
Completely disabling the autoupdater was an extremely bad idea. Now
even various autoupdater scripts to update the global version in
/usr/lib/chromium/WidevineCdm don't work anymore - so leaving users in
a broken state.
See also #981069
Your message dated Mon, 25 Jan 2021 22:00:23 +
with message-id
and subject line Bug#972747: fixed in sbuild 0.81.0
has caused the Debian Bug report #972747,
regarding sbuild: bullseye: /updates -> -security
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing control commands:
> severity -1 normal
Bug #969597 [libzstd] libzstd: Please correct version in symbol file
Severity set to 'normal' from 'serious'
--
969597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problem
Control: severity -1 normal
Hi Sebastian,
On Sat, Sep 05, 2020 at 09:03:20PM +0200, Sebastian Andrzej Siewior wrote:
> The symbol file records for instance the following symbols:
> ZSTD_minCLevel
> ZSTD_compressStream2
>
> as present in 1.3.8. This isn't entirely correct. Both symbo
Processing control commands:
> severity 976697 serious
Bug #976697 [webext-umatrix] webext-umatrix: no longer developed upstream,
remove or switch to LibreMatrix or?
Severity set to 'serious' from 'normal'
--
976697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976697
Debian Bug Tracking S
On 2021-01-25 22:20:38, Dr. Tobias Quathamer wrote:
> Am 25.01.21 um 16:35 schrieb Antoine Beaupré:
>> On 2021-01-24 23:53:20, Damon Lynch wrote:
>>> On Sun, Jan 24, 2021 at 8:44 PM Antoine Beaupré wrote:
>>>
Maybe then there is an easy fix to keep RPD in Debian if
rawkit disappears.
>>
Am 25.01.21 um 16:35 schrieb Antoine Beaupré:
> On 2021-01-24 23:53:20, Damon Lynch wrote:
>> On Sun, Jan 24, 2021 at 8:44 PM Antoine Beaupré wrote:
>>
>>> Maybe then there is an easy fix to keep RPD in Debian if
>>> rawkit disappears.
>>>
>>>
>> There is no need for any kind of fix in the code i
Your message dated Mon, 25 Jan 2021 22:20:01 +0100
with message-id <312cb50d-30d2-4df3-b21b-92ca41807...@fishpost.de>
and subject line xfsprogs: FTBFS with glibc 2.27: error: conflicting types for
'copy_file_range'
has caused the Debian Bug report #890716,
regarding xfsprogs: FTBFS with glibc 2.27
Processing commands for cont...@bugs.debian.org:
> tags 890716 - bullseye buster sid
Bug #890716 [src:xfsprogs] xfsprogs: FTBFS with glibc 2.27: error: conflicting
types for 'copy_file_range'
Removed tag(s) bullseye, buster, and sid.
>
End of message, stopping processing here.
Please contact me
Hi
On 24-01-2021 22:31, Chris Hofstaedtler wrote:
> Also: it would be great if I could get email for test failures.
We have RSS feeds on ci.d.n that can be used for that purpose.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
Hi Chris,
On 25-01-2021 09:33, Chris Hofstaedtler wrote:
> * Chris Hofstaedtler [210125 09:30]:
>> Lets see what the pdns-recursor 4.4.2-4 test run brings.
> ^^^
>
> That should have been 4.4.2-3.
>
>> Paul, can you expedite that test run? Possibly in a way
Processing commands for cont...@bugs.debian.org:
> forwarded 943405 https://github.com/sopel-irc/sopel/issues/2022
Bug #943405 [sopel] unsuitable for release: no upstream patch releases
Set Bug forwarded-to-address to
'https://github.com/sopel-irc/sopel/issues/2022'.
> thanks
Stopping processing
Processing commands for cont...@bugs.debian.org:
> found 980928 7.4.0+ds-1
Bug #980928 [npm] npm: Installing any package gives "npm ERR! current.merge is
not a function"
Marked as found in versions npm/7.4.0+ds-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
9
Your message dated Mon, 25 Jan 2021 20:50:04 +
with message-id
and subject line Bug#979218: fixed in renrot 1.2.0-1
has caused the Debian Bug report #979218,
regarding src:renrot: invalid maintainer address
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Mon, 25 Jan 2021 20:48:54 +
with message-id
and subject line Bug#980837: fixed in icewm 2.1.1-1
has caused the Debian Bug report #980837,
regarding icewm-common: Icewm crashes and/or doesn't start when Infadel2 theme
is selected as default.
to be marked as done.
This means
Your message dated Mon, 25 Jan 2021 20:34:16 +
with message-id
and subject line Bug#978624: fixed in fbxkb 0.6-3
has caused the Debian Bug report #978624,
regarding src:fbxkb: invalid maintainer address
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated Mon, 25 Jan 2021 19:49:16 +
with message-id
and subject line Bug#979345: fixed in maildirsync 1.2-3
has caused the Debian Bug report #979345,
regarding src:maildirsync: invalid maintainer address
to be marked as done.
This means that you claim that the problem has been deal
Processing control commands:
> close -1 8.15-1
Bug #981061 [src:iwyu] src:iwyu: fails to migrate to testing for too long:
FTBFS everywhere except amd64/i386
Marked as fixed in versions iwyu/8.15-1.
Bug #981061 [src:iwyu] src:iwyu: fails to migrate to testing for too long:
FTBFS everywhere except
Source: iwyu
Version: 8.0-4
Severity: serious
Control: close -1 8.15-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 976486
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync betw
Dear Maintainer,
attached patch makes your package to build correctly
in a sid chroot environment.
Kind Regards
--- debian/rules 2021-01-25 16:23:50.215639571 +0100
+++ debian/rules.new 2021-01-25 16:23:40.541020908 +0100
@@ -22,3 +22,4 @@
override_dh_auto_clean:
dh_auto_clean
rm -rf nototoo
Your message dated Mon, 25 Jan 2021 19:18:27 +
with message-id
and subject line Bug#979435: fixed in archmbox 4.10.0-3
has caused the Debian Bug report #979435,
regarding src:archmbox: invalid maintainer address
to be marked as done.
This means that you claim that the problem has been dealt w
Hi,
The maintainer email of your packages is not reachable anymore. Could
you please update it so your packages make it into the next stable
release?
If you do not intend to maintain those you also have the possibility to
orphan them.
Best,
On 2020/12/08 12:30 PM, Ansgar wrote:
> Source: crashm
Hi Leo,
The email on your package isn't reachable anymore. Could you fix it so
it gets into the next stable release?
If you do not intend to maintain this package anymore, another
possibility is to orphan it.
Best,
On 2021/01/05 04:47 PM, Ansgar wrote:
> Source: apt-venv
> Version: 1.0.0-2
> Se
Your message dated Mon, 25 Jan 2021 19:41:49 +0100
with message-id <20210125184149.oorsfvzz5g6ds...@aio.lmfnet.de>
and subject line Re: src:gwhois: invalid maintainer address
has caused the Debian Bug report #979221,
regarding src:gwhois: invalid maintainer address
to be marked as done.
This means
Hallo,
* Adrian Bunk [Mon, Jan 25 2021, 07:15:35AM]:
> On Sun, Jan 10, 2021 at 12:10:16PM +0100, Eduard Bloch wrote:
> >...
> > I am setting this to RC severity because it's just NOT ok and obvious to
> > fix. Going to change mentioned things and NMU this in a couple of weeks
> > if there is no fur
On Mon, 04 Jan 2021 12:29:56 +0100 Ansgar wrote:
> Source: gwhois
> Version: 20120626-1.2
> Severity: serious
> X-Debbugs-Cc: Holger Levsen
>
> The maintainer address is invalid, see below.
>
> Ansgar
>
> Start of forwarded message
> From: Mail Deliver
Dear Maintainer,
I was able to build your package in a sid chroot environment
without any issue.
Maybe this FTBFS was triggered by old bugged versions of Sphinx?
Kind Regards
Your message dated Mon, 25 Jan 2021 17:49:45 +
with message-id
and subject line Bug#979675: fixed in nvidia-graphics-drivers-tesla-450
450.102.04-1
has caused the Debian Bug report #979675,
regarding nvidia-graphics-drivers-tesla-450: CVE-2021-1052, CVE-2021-1053,
CVE-2021-1056
to be marked
Your message dated Mon, 25 Jan 2021 17:50:11 +
with message-id
and subject line Bug#979513: fixed in wsl 0.2.1-2
has caused the Debian Bug report #979513,
regarding src:wsl: invalid maintainer address
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Processing commands for cont...@bugs.debian.org:
> severity 981005 important
Bug #981005 [src:linux] linux-image-5.10.0-2-amd64: Bluetooth stopped working
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
981005: https://b
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:supertuxkart
> # 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.or
Processing commands for cont...@bugs.debian.org:
> tags 980609 + pending
Bug #980609 [src:gcc-10] missing i386-cpuinfo.h
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
980609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980609
Debian B
Hello dovecot folks,
Thanks for maintaining dovecot in Debian! I received an alert on my
dovecot-fts-xapian package that it is due to be removed from bullseye due
to security issues in the current dovecot package.
Just wanted to ask if there's anything I can do to help? I could try
updating the p
On Mon, Jan 25, 2021 at 11:51:11AM -0500, Joe Nahmias wrote:
> Just wanted to ask if there's anything I can do to help? I could try
> updating the package to the latest upstream release, which should fix
> those issues, but hesitate to do that without maintainer agreement. Given
> the timing, I'd h
Processing commands for cont...@bugs.debian.org:
> notfixed 980792 2:2.3.4-2~bpo10+1
Bug #980792 {Done: Guilhem Moulin } [cryptsetup-initramfs]
Cannot decrypt encrypted root at boot with cryptsetup-initramfs
2:2.3.4-2~bpo10+1 (buster-backports)
No longer marked as fixed in versions cryptsetup/2
Processing commands for cont...@bugs.debian.org:
> close 980792 2:2.3.4-2~bpo10+1
Bug #980792 [cryptsetup-initramfs] Cannot decrypt encrypted root at boot with
cryptsetup-initramfs 2:2.3.4-2~bpo10+1 (buster-backports)
Marked as fixed in versions cryptsetup/2:2.3.4-2~bpo10+1.
Bug #980792 [cryptse
Processing commands for cont...@bugs.debian.org:
> tags 980429 + pending
Bug #980429 [src:gcc-10] g++-10: spurious c++17 mode segmentation fault in
append_to_statement_list_1 (tree-iterator.c:65)
Bug #980629 [src:gcc-10] nheko: FTBFS: internal compiler error
Added tag(s) pending.
Added tag(s) pen
On Mon, Jan 25, 2021 at 04:51:18PM +0200, Adrian Bunk wrote:
> this bug report is from 24 Dec, so the breakage was not caused by the
> libsbml 5.19 upgrade.
>
> python-cobra seems to have been broken by Python 3.8 -> 3.9
Yes, but it seems cobra 0.20 is broken by libsbml 5.19 which is no
real los
On 2021-01-24 23:53:20, Damon Lynch wrote:
> On Sun, Jan 24, 2021 at 8:44 PM Antoine Beaupré wrote:
>
>> Maybe then there is an easy fix to keep RPD in Debian if
>> rawkit disappears.
>>
>>
> There is no need for any kind of fix in the code itself. Just remove the
> mention of rawkit from the Rap
Package: charybdis
Severity: serious
Tags: upstream
After a somewhat long period of uncertainty, Charybdis has been
finally abandoned upstream. The official git repository here:
https://github.com/charybdis-ircd/charybdis
.. is marked as "archived by the owner [and] read-only". It is unclear
wha
Your message dated Mon, 25 Jan 2021 15:06:26 +
with message-id
and subject line Bug#979529: fixed in libdbix-class-htmlwidget-perl 0.16-6
has caused the Debian Bug report #979529,
regarding src:libdbix-class-htmlwidget-perl: invalid maintainer address
to be marked as done.
This means that you
On Mon, Jan 25, 2021 at 03:04:03PM +0100, Andreas Tille wrote:
> Hi Adrian,
Hi Andreas,
>...
> I'm not sure whether this is related to libsbml 5.19 upgrade (I admit I
> failed to
> realise that upgrading libsbml might mean a transition since I lived under the
> impression that libsbml has no rde
Your message dated Mon, 25 Jan 2021 14:49:59 +
with message-id
and subject line Bug#979875: fixed in goban 1.1-6
has caused the Debian Bug report #979875,
regarding src:goban: invalid maintainer address
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Package: src:linux
Version: 5.10.9-1
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
After upgrading to Linux 5.10, Bluetooth no longer works. Bluetooth
adapter still shows up in rfkill:
```
$ rfkill
ID TYPE DEVICE SOFT HARD
0 bluetooth Tos
Control: tags -1 + unreproducible moreinfo
On Sun, 24 Jan 2021 08:28:21 +0100 lenny wrote:
> Package: libpython3.9
> Version: 3.9.1-3
> Severity: critical
> Justification: breaks the whole system
> X-Debbugs-Cc: lenni_...@yahoo.de
>
> Dear Maintainer,
>
> after running a normal apt update and a
Processing control commands:
> tags -1 + unreproducible moreinfo
Bug #980906 [libpython3.9] libpython3.9: _collections_abc.py :type
'types.GenericAlias' is not an acceptable base type
Added tag(s) unreproducible and moreinfo.
--
980906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980906
D
Hi Adrian,
On Mon, Jan 25, 2021 at 12:07:27AM +0200, Adrian Bunk wrote:
> > __ ERROR at setup of TestManipulation.test_escape_ids
> > __
> >
> > filename = '/usr/lib/python3/dist-packages/cobra/test/data/textbook.xml.gz'
> > number =
> > f_replace = {'F_GENE': ,
> > 'F_G
I have almost backported to Buster pytorch and I have found the same error, and
probably it's something related with rules file.
In the rules file, CMake options are configured and there's a line:
ifneq (,$(filter $(DEB_HOST_ARCH),amd64 arm64 ppc64el))
export USE_MKLDNN = ON
else
export USE_MKL
Processing commands for cont...@bugs.debian.org:
> found 967170 1.1.0-1
Bug #967170 {Done: Stephen Kitt } [src:markupsafe]
markupsafe: Unversioned Python removal in sid/bullseye
Marked as found in versions markupsafe/1.1.0-1.
> notfound 967170 1.1.1-1
Bug #967170 {Done: Stephen Kitt } [src:markup
Your message dated Mon, 25 Jan 2021 12:49:08 +
with message-id
and subject line Bug#978305: fixed in python-libusb1 1.9.1-1
has caused the Debian Bug report #978305,
regarding python-libusb1: FTBFS: dh_auto_test: error: pybuild --test -i
python{version} -p 3.9 returned exit code 13
to be mark
Hi Jonas,
could you take a look at this issue? Seems not a big bug, all tests
passed except this one:
> not ok 438 formatter:html when passing a single message with illegal
characters should return a string in HTML format with 1 issue in 1 file
> Check that message is correct: expected 'Unexpec
Processing commands for cont...@bugs.debian.org:
> affects 980429 nheko
Bug #980429 [src:gcc-10] g++-10: spurious c++17 mode segmentation fault in
append_to_statement_list_1 (tree-iterator.c:65)
Bug #980629 [src:gcc-10] nheko: FTBFS: internal compiler error
Added indication that 980429 affects nh
Processing commands for cont...@bugs.debian.org:
> reassign 979970 src:glibc 2.30-1
Bug #979970 [libselinux1] libselinux1: dependency to newer libc6 ignored
by/missing for aptitude
Bug reassigned from package 'libselinux1' to 'src:glibc'.
No longer marked as found in versions libselinux/3.1-1.
Ig
reassign 979970 src:glibc 2.30-1
affects 979970 + libselinux1
thanks
On Tue, 12 Jan 2021 13:31:19 +0100 Charlemagne Lasse
wrote:
> Right now, an update from buster to bullseye on amd64 completely
> bricks the system because libselinux1 is requiring a libc6 which is
> not yet installed on the
On Tue, 12 Jan 2021 13:31:19 +0100 Charlemagne Lasse
wrote:
Hello
> Right now, an update from buster to bullseye on amd64 completely
> bricks the system because libselinux1 is requiring a libc6 which is
> not yet installed on the system:
>
> Preparing to unpack .../0-libselinux1_3.1-2+b2_amd64
Your message dated Mon, 25 Jan 2021 10:34:34 +
with message-id
and subject line Bug#978275: fixed in python-pluggy 0.13.0-6
has caused the Debian Bug report #978275,
regarding python-pluggy: FTBFS: dpkg-buildpackage: error: dpkg-source -b .
subprocess returned exit status 2
to be marked as do
Processing control commands:
> tags -1 + pending
Bug #980928 [npm] npm: Installing any package gives "npm ERR! current.merge is
not a function"
Added tag(s) pending.
--
980928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tags -1 + pending
Le 25/01/2021 à 10:35, Xavier a écrit :
> Le 24/01/2021 à 15:52, Jan Kiszka a écrit :
>> Package: npm
>> Version: 7.4.0+ds-1~bpo10+2
>> Severity: grave
>> Justification: renders package unusable
>>
>> Tried out via, e.g., "npm install serialport" inside a debian:buster-s
Processing control commands:
> tag -1 pending
Bug #978275 [src:python-pluggy] python-pluggy: FTBFS: dpkg-buildpackage: error:
dpkg-source -b . subprocess returned exit status 2
Added tag(s) pending.
--
978275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978275
Debian Bug Tracking System
C
Control: tag -1 pending
Hello,
Bug #978275 in python-pluggy 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/packages/python-pluggy/-/commit/f5b53b64
Your message dated Mon, 25 Jan 2021 09:49:13 +
with message-id
and subject line Bug#976847: fixed in radare2-cutter 1.12.0-1
has caused the Debian Bug report #976847,
regarding radare2-cutter FTBFS with Qt 5.15
to be marked as done.
This means that you claim that the problem has been dealt wi
Le 24/01/2021 à 15:52, Jan Kiszka a écrit :
> Package: npm
> Version: 7.4.0+ds-1~bpo10+2
> Severity: grave
> Justification: renders package unusable
>
> Tried out via, e.g., "npm install serialport" inside a debian:buster-slim
> container. Happens with both "npm node-*" as well only the required
>
Processing commands for cont...@bugs.debian.org:
> tags 980928 + confirmed
Bug #980928 [npm] npm: Installing any package gives "npm ERR! current.merge is
not a function"
Added tag(s) confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
980928: https://bugs.
* Chris Hofstaedtler [210125 09:30]:
> Lets see what the pdns-recursor 4.4.2-4 test run brings.
^^^
That should have been 4.4.2-3.
> Paul, can you expedite that test run? Possibly in a way it runs on
> the problematic worker?
Actually it already ran, but su
* Chris Hofstaedtler [210124 22:24]:
> I don't see why this would "just fail randomly". I don't think its a
> timing thing. Maybe this worker is weird in a different way.
Having now looked at the (not very granular) timestamps, it looks
like the 30sec "service did not finish starting" timeout fro
On 2021/01/25 12:18 AM, Antonio Ospite wrote:
> On Sun, 24 Jan 2021 21:12:54 +0100
> Baptiste Beauplat wrote:
>
> > Hi Antonio,
> >
> > kboot-utils, one of the packages you maintain in Debian has an old,
> > unreachable
> > Maitainer address. Could you please update it to prevent it from gettin
Package: libpython3.9
Followup-For: Bug #980906
The correct workaround is:
class _CallableGenericAlias(type(list[int])):
i.e. with type(), because GenericAlias = type(list[int]) in _collections_abc.py.
Semantically, it is intended to make a generic type and list[int] be of the
same type.
Th
88 matches
Mail list logo
