Control: tags -1 moreinfo
Hi Paul,
On Fri, Jan 03, 2020 at 09:40:44PM +0100, Paul Gevers wrote:
>
> With a recent upload of hyphy the autopkgtest of hyphy fails in testing
> when that autopkgtest is run with the binary packages of hyphy from
> unstable. It passes when run with only packages
Processing control commands:
> tags -1 moreinfo
Bug #948093 [src:hyphy] hyphy: autopkgtest regression: Duplicate analysis
keyword
Added tag(s) moreinfo.
--
948093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> tags 945633 + fixed
Bug #945633 {Done: Sandro Tosi } [src:debian-multimedia]
debian-multimedia: Python2 removal in sid/bullseye
Added tag(s) fixed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
945633:
Thanks Håvard. Placing @pytest.mark.skip will get the job so worse come
to worse we can deal with it that way. The reason why I'd prefer not to
do it that way is that that here we only want to control the tests being
run from debian/tests. The @pytest.mark.skip will disable them for all
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
Processing control commands:
> forwarded -1 https://bugs.kde.org/show_bug.cgi?id=415089
Bug #948207 [kio-gdrive] kio-gdrive: No more work because google temoprarilly
supressed the access
Set Bug forwarded-to-address to 'https://bugs.kde.org/show_bug.cgi?id=415089'.
> severity -1 important
Bug
Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=415089
Control: severity -1 important
Justification: kio-gdrive is not unusable for everyone
Hi Eric,
Thank you for reporting this bug, and especially for providing a link to
the upstream bug :-)
I've reduced the severity to important,
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
Processing control commands:
> reassign -1 ftp.debian.org
Bug #938827 [src:winpdb] winpdb: Python2 removal in sid/bullseye
Bug reassigned from package 'src:winpdb' to 'ftp.debian.org'.
No longer marked as found in versions winpdb/1.4.8-3.
Ignoring request to alter fixed versions of bug #938827 to
Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: winpdb -- RoQA; semi-dead upstream; unmaintained; low
popcon; blocking py2 removal
The existing maintainer doesn't intend to maintain it anymore, so let's
just RM it.
Hi Martin, Sunil, all,
Thanks for looking into this issue while we were all off, Martin and Sunil!
To summarise where I understand things are at now: Martin's uploaded
a pcp package for rebuild which drops the python2 build steps. I think
this is fine and solves the immediate, pressing issue.
Salvatore,
Am 06.01.20 um 22:46 schrieb Salvatore Bonaccorso:
> I think the whole problem is placed at multiple levels. You seem to
> use systemd as init, but when lgorotate comes into action, the
> postrotate is
Yes. I use systemd. I updated my unit file to `Type=simple`, because I
wanted
On 07/01/2020 00.09, Emmanuel Bouthenot wrote:
> Andreas,
>
> On Mon, Nov 25, 2019 at 09:44:14PM +0100, Andreas Beckmann wrote:
> [...]
>
>> during a test with piuparts I noticed your package fails to upgrade from
>> 'buster'.
>> It installed fine in 'buster', then the upgrade to 'bullseye'
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
Andreas,
On Mon, Nov 25, 2019 at 09:44:14PM +0100, Andreas Beckmann wrote:
[...]
> during a test with piuparts I noticed your package fails to upgrade from
> 'buster'.
> It installed fine in 'buster', then the upgrade to 'bullseye' fails.
>
> From the attached log (scroll to the bottom...):
It
Hi Andreas, hi Mike,
On Sun, Jan 05, 2020 at 12:41:32AM +0100, Andreas Beckmann wrote:
> Are you trying to use dpkg-divert on conffiles? That does not work ...
[..]
> PS: If you tell me what exactly you want to achieve, I might think about it
> ... ;-)
The vanilla lightdm.conf file should be
On 06/01/2020 18.19, Giovanni Mascellani wrote:
>> To simplify such future transitions, I created a patch (#948273) to
>> actually make use of the virtual packages introduced in -12.
>> Please include it along with the reintroduction of python2 support in
>> *sid*. Then we can binNMU all rdepends
Your message dated Mon, 06 Jan 2020 22:32:09 +
with message-id
and subject line Bug#941266: fixed in netty 1:4.1.33-1+deb10u1
has caused the Debian Bug report #941266,
regarding netty: CVE-2019-16869
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> fixed 934951 5.8.1-1
Bug #934951 {Done: Håvard Flaget Aasen }
[src:elasticsearch-curator] elasticsearch-curator: build-dependency
python-elasticsearch (< 6.0.0) unsatisfiable in sid
Marked as fixed in versions elasticsearch-curator/5.8.1-1.
>
Hi Tim,
[Dislaimer: not the maintainer here, just looked at it briefly]
On Mon, Jan 06, 2020 at 02:44:48PM +0100, Tim Duesterhus wrote:
> Package: tinyproxy
> Version: 1.10.0-2
> Severity: critical
> Justification: breaks unrelated software
>
> Dear Maintainer,
>
>* What led up to the
Processing commands for cont...@bugs.debian.org:
> tags 948283 + security
Bug #948283 [tinyproxy] tinyproxy: If no PidFile is configured logrotate will
change the owner of the root directory
Added tag(s) security.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Hi Paul,
Quoting Paul Gevers (2020-01-06 21:38:56)
> The autopkgtest of mmdebstrap fails on arm64 with the following message:
> """
> script only supports being run on amd64
> """
>
> You should fix the failure. If you don't want to spend time on making
> the script work on non-amd64, than at
Dear maintainer,
I've prepared an NMU for sinntp (versioned as 1.6-0.2) and uploaded
it to DELAYED/5. Please feel free to tell me if I should cancel it.
cu
Adrian
diff -Nru sinntp-1.6/debian/changelog sinntp-1.6/debian/changelog
--- sinntp-1.6/debian/changelog 2019-12-26 08:55:37.0 +0200
Your message dated Mon, 6 Jan 2020 21:54:20 +0100
with message-id <3aa499e8-9b67-4df0-b8e4-fce4870c3...@yahoo.no>
and subject line close bug
has caused the Debian Bug report #934951,
regarding elasticsearch-curator: build-dependency python-elasticsearch (<
6.0.0) unsatisfiable in sid
to be marked
Your message dated Mon, 6 Jan 2020 21:54:20 +0100
with message-id <3aa499e8-9b67-4df0-b8e4-fce4870c3...@yahoo.no>
and subject line close bug
has caused the Debian Bug report #907498,
regarding elasticsearch-curator: autopkgtest fails:
python-elasticsearch-curator uninstallable with
Your message dated Mon, 06 Jan 2020 20:45:24 +
with message-id
and subject line Bug#947896: fixed in wal2json 2.0-1
has caused the Debian Bug report #947896,
regarding wal2json: autopkgtest regression: output different
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 06 Jan 2020 20:45:33 +
with message-id
and subject line Bug#947733: fixed in watson 1.8.0-0.1
has caused the Debian Bug report #947733,
regarding watson: FTBFS in bullseye and sid
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On 06/01/2020 15.20, Dimitri John Ledkov wrote:
>> Please include it along with the reintroduction of python2 support in
>> *sid*. Then we can binNMU all rdepends of libboost-python1.67.0,
>> libboost-mpi-python1.67.0, libboost-numpy1.67.0 to add more strict
>> dependencies on the required python
Source: mmdebstrap
Version: 0.5.1-2
Severity: important
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: alwaysfails
Hi josch,
The autopkgtest of mmdebstrap fails on arm64 with the following message:
"""
script only supports being run on amd64
Processing commands for cont...@bugs.debian.org:
> reassign 948301 initramfs-tools
Bug #948301 [libkmod2] libkmod2: update-initramfs fails in lookup_builtin_file()
Bug reassigned from package 'libkmod2' to 'initramfs-tools'.
No longer marked as found in versions kmod/26+20191223-1.
Ignoring
Processing control commands:
> tag -1 pending
Bug #948299 [osc-plugins-dput] osc-plugins-dput: Doesn't work with Python 3
version of osc
Added tag(s) pending.
--
948299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hi,
On Mon, 6 Jan 2020 at 21:15, Simon McVittie wrote:
> I attach a possible patch, although this seems to have been fixed
> differently upstream.
Thanks for the patch, I was going to roll an upstream tarball and
upload it to Debian, you shouldn’t have spent effort on
Processing control commands:
> tag -1 pending
Bug #948299 [osc-plugins-dput] osc-plugins-dput: Doesn't work with Python 3
version of osc
Ignoring request to alter tags of bug #948299 to the same tags previously set
--
948299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948299
Debian Bug
Package: libkmod2
Version: 26+20191223-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
upgrading:
kmod (26-3 => 26+20191223-1)
libkmod-dev (26-3 => 26+20191223-1)
libkmod2 (26-3 => 26+20191223-1)
fails with:
[...]
Preparing to unpack
Package: osc-plugins-dput
Version: 20180227.1-1
Severity: grave
Justification: renders package unusable
Tags: patch upstream
$ osc -A xxx dput xxx:xxx ~/tmp/build-area/xxx_source.changes
Traceback (most recent call last):
File "/usr/bin/osc", line 41, in
r = babysitter.run(osccli)
...
W dniu 21.12.2019 o 11:27, Graham Inggs pisze:
Hi, does this message have the wrong bug number?
To: cont...@bugs.debian.org
From: Mateusz Łukasik
Subject: Re: New mpv in sid breaks smplayer
Message-ID: <8d5a8d18-b29a-179f-4701-b97226937...@linuxmint.pl>
Date: Thu, 12 Dec 2019 08:56:03 +0100
Processing commands for cont...@bugs.debian.org:
> severity 942487 important
Bug #942487 [reprepro] reprepro imposes arbitrary limits on control files that
are successfully parsed by other debian tools
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.
Please contact
Control: tag -1 pending
Hello,
Bug #947896 in wal2json 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 #947896 [src:wal2json] wal2json: autopkgtest regression: output different
Added tag(s) pending.
--
947896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: severity -1 normal
On Sun, Dec 01, 2019 at 11:38:39AM +0100, Andreas Beckmann wrote:
> Followup-For: Bug #936557
> Control: severity -1 serious
>
> freeorion now FTBFS in sid:
>...
> -- Found PythonInterp: /usr/bin/python2.7 (found suitable version "2.7.17",
> minimum required is
Processing control commands:
> severity -1 normal
Bug #936557 [src:freeorion] freeorion: Python2 removal in sid/bullseye
Severity set to 'normal' from 'serious'
--
936557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
On Fri, 13 Dec 2019, Jamie Strandboge wrote:
> I can confirm this. It looks like iptables-restore and iptables6-restore
> in 1.8.4 has broken -n behavior with the nft varieties.
This is https://bugzilla.netfilter.org/show_bug.cgi?id=1394
--
Email: ja...@strandboge.com
IRC: jdstrand
Hello Michael,
I was able to hit the bug again. It seems I have to go to another wifi
network, then back to my home network to hit the bug. On the
client-side, I get:
janv. 06 18:57:13 zoro NetworkManager[75721]: [1578333433.9474] dhcp4
(wlp3s0): activation: beginning transaction (timeout in
Package: src:python-dateutil
Version: 2.7.3-3
Severity: serious
Tags: sid bullseye
python-dateutils's autopkg tests fail for Python2, python-freezegun was already
removed. Maybe for now just stop testing for Python2.
Processing commands for cont...@bugs.debian.org:
> severity 945875 grave
Bug #945875 [openmw] openmw: Crash when saving
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
945875:
Your message dated Mon, 06 Jan 2020 17:34:48 +
with message-id
and subject line Bug#937307: fixed in polenum 1.4-2
has caused the Debian Bug report #937307,
regarding polenum: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Dear Maintainer,
just as a side note, a similar bug was submitted
against the basilisk2 package.
https://bugs.debian.org/922323
Another user of slirp is qemu, which had some changes in
that area, which seems to have evolved into this library:
Your message dated Mon, 06 Jan 2020 17:20:51 +
with message-id
and subject line Bug#945840: fixed in boost1.67 1.67.0-16.1
has caused the Debian Bug report #945840,
regarding libboost-python1.67.0 must not drop the Python 2.7 library
to be marked as done.
This means that you claim that the
Your message dated Mon, 06 Jan 2020 17:20:51 +
with message-id
and subject line Bug#945840: fixed in boost1.67 1.67.0-16.1
has caused the Debian Bug report #945840,
regarding Server fails for missing boost library
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 06 Jan 2020 17:20:51 +
with message-id
and subject line Bug#945840: fixed in boost1.67 1.67.0-16.1
has caused the Debian Bug report #945840,
regarding libboost-python1.67.0 must not drop the Python 2.7 library
to be marked as done.
This means that you claim that the
Hi,
Il 06/01/20 13:54, Andreas Beckmann ha scritto:
> This bug is not about the python2 removal. This bug is about removing a
> shared library without doing a proper transition, i.e. renaming the
> package (which will happen with boost1.71) or adding a bunch of Breaks.
> The same will happen
On Sun, Jan 5, 2020 at 11:24 PM intrigeri wrote:
>
> Hi,
>
> Roger Shimizu (2020-01-05):
> > I find this is due to below files were shipped by previous version of
> > torbrowser-launcher, but not as conffile.
> > /etc/apparmor.d/local/torbrowser.Tor.tor
> >
Processing control commands:
> severity -1 serious
Bug #936105 [src:abinit] abinit: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
--
936105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> # fixed in 7.0.0 but bug was not closed
> close 948224 7.0.0-1
Bug #948224 [pillow] pillow: CVE-2019-19911 CVE-2020-5310 CVE-2020-5311
CVE-2020-5312 CVE-2020-5313
There is no source info for the package 'pillow' at version '7.0.0-1' with
Your message dated Mon, 06 Jan 2020 15:34:20 +
with message-id
and subject line Bug#947479: fixed in antimony 0.9.3-1.1
has caused the Debian Bug report #947479,
regarding antimony: fails to start due to broken library dependency
to be marked as done.
This means that you claim that the
Your message dated Mon, 06 Jan 2020 15:34:19 +
with message-id
and subject line Bug#947326: fixed in antimony 0.9.3-1.1
has caused the Debian Bug report #947326,
regarding FTBFS: unable to load addon python3: Can't locate
to be marked as done.
This means that you claim that the problem has
Control: severity -1 normal
Control: tags -1 patch
Control: reassign -1 initramfs-tools
On Jan 06, crvi wrote:
>* What outcome did you expect instead?
>
> Successful ramfs generation
Do you have any reason to believe that the initrfamfs was not generated
successfully?
This is only
Processing control commands:
> severity -1 normal
Bug #948257 [kmod] depmod: ERROR: ../libkmod/libkmod.c:515
lookup_builtin_file() could not open builtin file
'/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
Severity set to 'normal' from 'serious'
> tags -1 patch
Bug
Processing commands for cont...@bugs.debian.org:
> severity 925473 wishlist
Bug #925473 [tomcat9] tomcat9: sysvinit script missing (Policy §9.11¶2 “must”)
Severity set to 'wishlist' from 'serious'
> retitle 925473 tomcat9: sysvinit script
Bug #925473 [tomcat9] tomcat9: sysvinit script missing
James McCoy wrote...
> Autopkgtests already run against packages in experimental, albeit at a
> slower pace than those in unstable. It seems those did catch the issue
> -- https://release.debian.org/britney/pseudo-excuses-experimental.html#file
TIL - now added to the list of things to check
Your message dated Mon, 06 Jan 2020 14:49:38 +
with message-id
and subject line Bug#948195: fixed in nvidia-graphics-drivers-legacy-340xx
340.108-2
has caused the Debian Bug report #948195,
regarding nvidia-legacy-340xx-driver: Xorg fails to start with a kernel panic
after the upgrade to
On Mon, 6 Jan 2020 at 12:54, Andreas Beckmann wrote:
>
> On Sat, 4 Jan 2020 16:18:44 + Dimitri John Ledkov
> wrote:
> > I would be ok to reintroduce boost-python2.7 in experimental only.
>
> > > On Sat, 4 Jan 2020, 06:45 Giovanni Mascellani, wrote:
> > >
> > >> Hi,
> > >>
> > >> Il 03/01/20
Hi,
I'm fine with the NMU, thanks.
Bests,
On 2020-01-06 06:26, Håvard Flaget Aasen wrote:
> Control: tags 947326 + patch
> Control: tags 947326 + pending
> Control: tags 947479 + patch
> Control: tags 947479 + pending
>
>
> Dear maintainer,
>
> I've prepared an NMU for antimony (versioned as
Package: tinyproxy
Version: 1.10.0-2
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
* What led up to the situation?
I configured tinyproxy without a PidFile.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I removed the
Control: tag -1 pending
Hello,
Bug #937307 in polenum 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 #937307 [src:polenum] polenum: Python2 removal in sid/bullseye
Added tag(s) pending.
--
937307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937307
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Mon, 06 Jan 2020 13:03:34 +
with message-id
and subject line Bug#944221: fixed in sdpa 7.3.12+dfsg-1
has caused the Debian Bug report #944221,
regarding sdpa: ftbfs in unstable [PATCH]
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 06 Jan 2020 13:01:17 +
with message-id
and subject line Bug#944937: fixed in py-postgresql 1.2.1+git20180803.ef7b9a9-2
has caused the Debian Bug report #944937,
regarding py-postgresql: needs an explicit build dependency on dh-python
to be marked as done.
This means
Your message dated Mon, 06 Jan 2020 13:01:25 +
with message-id
and subject line Bug#937428: fixed in pydispatcher 2.0.5-2
has caused the Debian Bug report #937428,
regarding pydispatcher: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
On Sat, 4 Jan 2020 16:18:44 + Dimitri John Ledkov
wrote:
> I would be ok to reintroduce boost-python2.7 in experimental only.
> > On Sat, 4 Jan 2020, 06:45 Giovanni Mascellani, wrote:
> >
> >> Hi,
> >>
> >> Il 03/01/20 22:07, Adrian Bunk ha scritto:
> >> > Dimitri already agreed in a
On Mon, Jan 06, 2020 at 12:19:21PM +0100, Christoph Biedl wrote:
> Additionally, I always upload new upstream versions of src:file to
> experimental first to avoid situations like this. If anybody wishes to
> receive a notification to start tests, drop me a line with your e-mail
> address,
Your message dated Mon, 06 Jan 2020 12:10:47 +
with message-id
and subject line Bug#948269: fixed in file 1:5.38-3
has caused the Debian Bug report #948269,
regarding file: misdetection of shared libraries as statically linked - breaks
dh_shlibdeps
to be marked as done.
This means that you
Hi Mo,
On Sun, Jan 05, 2020 at 08:19:07AM +, Mo Zhou wrote:
> GSL provides a set of CBLAS API/ABI, delivered with shared object
> "libgslcblas.so" and header "gsl_cblas.h". That subset becomes
> redundant once you include the headers of any standard/compatible
> (C)BLAS library. That's what
Observing similar issues after kmod upgrade from version 26-3 to
26+20191223-1.
initramfs is built, despite of errors reported and all systems affected
are bootable without problems for me.
Temporary file claimed as missing
(/var/tmp/mkinitramfs_iC46xD/lib/modules/5.4.8/modules.builtin.bin ) is
Processing control commands:
> tags 947326 + patch
Bug #947326 [src:antimony] FTBFS: unable to load addon python3: Can't locate
Ignoring request to alter tags of bug #947326 to the same tags previously set
> tags 947326 + pending
Bug #947326 [src:antimony] FTBFS: unable to load addon python3:
Control: tags 947326 + patch
Control: tags 947326 + pending
Control: tags 947479 + patch
Control: tags 947479 + pending
Dear maintainer,
I've prepared an NMU for antimony (versioned as 0.9.3-1.1) and
uploaded it to DELAYED/XX. Please feel free to tell me if I
should delay it longer.
Not sure
Processing control commands:
> tags 947326 + patch
Bug #947326 [src:antimony] FTBFS: unable to load addon python3: Can't locate
Added tag(s) patch.
> tags 947326 + pending
Bug #947326 [src:antimony] FTBFS: unable to load addon python3: Can't locate
Added tag(s) pending.
> tags 947479 + patch
Bug
Control: tags 948269 tags pending upstream
Sebastian Ramacher wrote...
(...)
> Note the difference in dynamically linked vs statically linked. This
> change breaks dh_shlibdeps causing ${shlibs:Depends} to not be properly
> populated.
That was a change done upstream:
|PR/93: iaeiaeiaeiae:
Processing control commands:
> tags 948269 tags pending upstream
Unknown tag/s: tags.
Recognized are: patch wontfix moreinfo unreproducible help security upstream
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed
fixed-in-experimental sid experimental potato woody
Your message dated Mon, 6 Jan 2020 11:38:10 +0100
with message-id
and subject line Re: FTBFS: make[1]: *** No rule to make target
'lowered_tree_view.h', needed by 'ui_datovka.h'. Stop.
has caused the Debian Bug report #947475,
regarding datovka: FTBFS: make[1]: *** No rule to make target
Your message dated Mon, 6 Jan 2020 11:39:34 +0100
with message-id
and subject line Re: FTBFS: debian/bppphyview/usr/share/man/man1/phyview.1: No
such file or directory
has caused the Debian Bug report #947329,
regarding bppphyview: FTBFS: debian/bppphyview/usr/share/man/man1/phyview.1: No
such
Package: file
Version: 1:5.38-2
Severity: grave
With file version 1:5.37-6:
$ file /usr/lib/x86_64-linux-gnu/libcrypt.so.1.1.0
/usr/lib/x86_64-linux-gnu/libcrypt.so.1.1.0: ELF 64-bit LSB shared object,
x86-64, version 1 (SYSV), dynamically linked,
Your message dated Mon, 06 Jan 2020 10:19:01 +
with message-id
and subject line Bug#947513: fixed in luakit 1:2.1-2
has caused the Debian Bug report #947513,
regarding luakit: build-depends on obsolete libunique-dev
to be marked as done.
This means that you claim that the problem has been
Package: slirp
Version: 1:1.0.17-8+b1
Severity: grave
Hey;
When starting slirp it crashes almost immediately; Backtrace from gdb:
```
(gdb) bt
#0 ip_slowtimo () at ip_input.c:457
#1 0x55568a82 in main_loop () at ./main.c:980
#2 0x97c6 in main (argc=1, argv=0x7fffdf38)
Processing control commands:
> severity -1 serious
Bug #948257 [kmod] depmod: ERROR: ../libkmod/libkmod.c:515
lookup_builtin_file() could not open builtin file
'/var/tmp/mkinitramfs_N1a1Mk/lib/modules/5.4.0-1-amd64/modules.builtin.bin'
Severity set to 'serious' from 'important'
--
948257:
Hi,
I don't understand why there's still this bug, and it's being set to
severity serious: when I build the package locally using sbuild, there's
no issue and the package builds fine, at least with version 2.6.1-1.
Gianfranco, could you help me understand?
Cheers,
Thomas Goirand (zigo)
Your message dated Mon, 6 Jan 2020 09:41:30 +0100
with message-id
and subject line Fixed in seafile/7.0.4-1
has caused the Debian Bug report #938459,
regarding seafile: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Quoting gregor herrmann (2020-01-06 05:05:25)
> As first seen on ci.d.n. [0] the package's test suite fails after the
> update
>
> - -libregexp-pattern-license-perl 3.0.31-4
> +libregexp-pattern-license-perl 3.1.99-1
Possibly related: Licensecheck was broken yesterday after upload of
Processing commands for cont...@bugs.debian.org:
> severity 937569 important
Bug #937569 [src:python2.7] python2.7: Python2 removal in sid/bullseye
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
937569:
89 matches
Mail list logo
