Source: mit-scheme
Version: 10.1.11-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=mit-scheme=sid
...
debian/rules override_dh_install-arch
make[1]: Entering directory '/<>'
dh_install
dh_install: warning: Cannot find (any matches for)
Processing control commands:
> block -1 by 959828
Bug #957160 [src:e17] e17: ftbfs with GCC-10
957160 was not blocked by any bugs.
957160 was not blocking any bugs.
Added blocking bug(s) of 957160: 959828
--
957160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957160
Debian Bug Tracking
Control: reassign -1 libdebconf-kde-dev 1.0.3-3
Control: retitle -1 libdebconf-kde-dev misses dependencies
Control: tags -1 - patch
Control: affects -1 src:apper
On Wed, Jun 10, 2020 at 12:07:37AM +0100, peter green wrote:
> Package: apper
> Version: 1.0.0-2
> Severity: serious
> Tags: bullseye,
Processing control commands:
> reassign -1 libdebconf-kde-dev 1.0.3-3
Bug #962567 [apper] apper FTBFS can't find KF5TextWidgetsConfig.cmake
Bug reassigned from package 'apper' to 'libdebconf-kde-dev'.
No longer marked as found in versions apper/1.0.0-2.
Ignoring request to alter fixed versions of
Your message dated Wed, 10 Jun 2020 05:10:40 +
with message-id
and subject line Bug#962520: Removed package(s) from unstable
has caused the Debian Bug report #933131,
regarding customdeb: depends on libparse-debianchangelog-perl that has no
upstream maintainer
to be marked as done.
This
Your message dated Wed, 10 Jun 2020 05:11:44 +
with message-id
and subject line Bug#962543: Removed package(s) from unstable
has caused the Debian Bug report #937682,
regarding python-cyclone: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Your message dated Wed, 10 Jun 2020 05:09:54 +
with message-id
and subject line Bug#962489: Removed package(s) from unstable
has caused the Debian Bug report #937483,
regarding pymtbl: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 10 Jun 2020 05:09:31 +
with message-id
and subject line Bug#962487: Removed package(s) from unstable
has caused the Debian Bug report #938192,
regarding python-sqlite: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 10 Jun 2020 05:11:02 +
with message-id
and subject line Bug#962521: Removed package(s) from unstable
has caused the Debian Bug report #933128,
regarding libparse-debianchangelog-perl: Unsuitable for Bullseye unless someone
becomes upstream
to be marked as done.
This
Your message dated Wed, 10 Jun 2020 05:10:17 +
with message-id
and subject line Bug#962490: Removed package(s) from unstable
has caused the Debian Bug report #877856,
regarding mysql-utilities: Parsing MySQL version is broken
to be marked as done.
This means that you claim that the problem
Processing control commands:
> tags 925672 + pending
Bug #925672 [src:efivar] efivar: ftbfs with GCC-9
Added tag(s) pending.
--
925672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags 925672 + pending
Dear maintainer,
I've prepared an NMU for efivar (versioned as 37-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer or cancel the NMU.
Regards,
David Polverari.
diff -Nru efivar-37/debian/changelog
Ah, gotchu. Here it is attached.
On Tue, 2020-06-09 at 22:29 -0500, Richard Laager wrote:
> On 6/9/20 7:02 PM, Wxcafé wrote:
> > I don't use zfs-import-cache since it's a single pool that contains
> > the
> > root so it's in the kernel cmdline and imported at that point.
>
> I wasn't asking
On 6/9/20 7:02 PM, Wxcafé wrote:
> I don't use zfs-import-cache since it's a single pool that contains the
> root so it's in the kernel cmdline and imported at that point.
I wasn't asking about the pool cache, but the filesystem cache file used
by zfs-mount-generator. That would show all the
Your message dated Wed, 10 Jun 2020 03:03:40 +
with message-id
and subject line Bug#962570: fixed in gazebo 11.0.0+dfsg1-4
has caused the Debian Bug report #962570,
regarding libgazebo-dev: Leftover dependency on removed package ttf-dejavu-core
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> notfound 962086 0.8.14+dfsg2-3
Bug #962086 {Done: Gianfranco Costamagna }
[src:freecad] freecad: FTBFS with boost 1.71
The source 'freecad' and version '0.8.14+dfsg2-3' do not appear to match any
binary packages
No longer marked as found in
Processing control commands:
> severity -1 grave
Bug #962201 [src:natbraille] natbraille: depends on dummy transitional package
ttf-dejavu-core
Severity set to 'grave' from 'normal'
--
962201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962201
Debian Bug Tracking System
Contact
Package: libgazebo-dev
Severity: serious
Version: 11.0.0+dfsg1-3
Tags: sid bullseye
Dear Debian gazebo maintainers,
Thanks for fixing https://bugs.debian.org/961561 in the last upload.
However, the previous upload only cleaned up the build-dependencies,
not the binary package dependencies.
Processing commands for cont...@bugs.debian.org:
> notfound 962086 0.8.14+dfsg2-3
Bug #962086 {Done: Gianfranco Costamagna }
[src:freecad] freecad: FTBFS with boost 1.71
The source 'freecad' and version '0.8.14+dfsg2-3' do not appear to match any
binary packages
No longer marked as found in
Your message dated Wed, 10 Jun 2020 00:33:41 +
with message-id
and subject line Bug#958414: fixed in equivs 2.3.1
has caused the Debian Bug report #958414,
regarding Latest equivs version 2.3.0 breaks mk-build-deps
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 10 Jun 2020 00:12:18 +
with message-id
and subject line Bug#831104: fixed in xevil 2.02r2-10.1
has caused the Debian Bug report #831104,
regarding xevil: FTBFS with GCC 6: stl_algobase.h:243:56: error: macro "min"
passed 3 arguments, but takes just 2
to be marked as
Only one pool containing both the actual datasets and the ones with
canmount=noauto (backups) that have the same mountpoint (there's a
separate boot pool but it doesn't matter in this circumstance)
I don't use zfs-import-cache since it's a single pool that contains the
root so it's in the kernel
Your message dated Tue, 09 Jun 2020 23:09:09 +
with message-id
and subject line Bug#962335: fixed in pandas 1.0.4+dfsg-1
has caused the Debian Bug report #962335,
regarding FTBFS: new upstream version available with bug fixes
to be marked as done.
This means that you claim that the problem
Package: apper
Version: 1.0.0-2
Severity: serious
Tags: bullseye, sid, patch
http://buildd.raspbian.org/status/fetch.php?pkg=apper=armhf=1.0.0-2%2Bb4=1591727741
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apper.html
CMake Error at
Processing control commands:
> tags 960758 + patch
Bug #960758 [src:libcamera] libcamera FTBFS: missing boost build dependencies
Added tag(s) patch.
> tags 960758 + pending
Bug #960758 [src:libcamera] libcamera FTBFS: missing boost build dependencies
Added tag(s) pending.
--
960758:
Control: tags 960758 + patch
Control: tags 960758 + pending
Dear maintainer,
I've prepared an NMU for libcamera (versioned as 0~git20200513+924778e-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.
Regards,
Luis Paulo Linares
diff -Nru
On 6/7/20 3:12 PM, wxcafe wrote:
> The systemd zfs-mount-generator script
> (/lib/systemd/system-generators/zfs-mount-generator) can break system
> boot if there are multiple datasets with the same mountpoint, because it
> ignores the zfs property canmount=noauto.
It certainly does not "ignore"
Hi Paul,
I am just busy, so the ping here should be enough. I’ll take a look at it
tomorrow.
Ondrej
--
Ondřej Surý
> On 9 Jun 2020, at 22:08, Paul Gevers wrote:
>
> Dear maintainers,
>
>> On 25/05/2020 21.20, Paul Gevers wrote:
>> On 12-03-2020 16:05, Paul Gevers wrote:
>> The tests are
Your message dated Tue, 09 Jun 2020 21:59:09 +
with message-id
and subject line Bug#960243: fixed in zimlib 4.0.4-5.1
has caused the Debian Bug report #960243,
regarding zimlib FTBFS with ICU 67.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 09 Jun 2020 21:57:31 +
with message-id
and subject line Bug#962555: fixed in scilab 6.1.0+dfsg1-4
has caused the Debian Bug report #962555,
regarding scilab: FTBFS with libicu (>= 66)
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 09 Jun 2020 21:51:49 +
with message-id
and subject line Bug#949837: fixed in innoextract 1.8-1.2
has caused the Debian Bug report #949837,
regarding FTBFS with Boost 1.71
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Tue, 09 Jun 2020 21:49:39 +
with message-id
and subject line Bug#960381: fixed in cupt 2.10.4+nmu1
has caused the Debian Bug report #960381,
regarding cupt: FTBFS with boost 1.71
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Tue, 09 Jun 2020 21:23:48 +
with message-id
and subject line Bug#961863: fixed in zatacka 0.1.8-5.3
has caused the Debian Bug report #961863,
regarding zatacka: Depends/Build-Depends on cruft package ttf-dejavu-core
to be marked as done.
This means that you claim that the
Your message dated Tue, 9 Jun 2020 23:08:58 +0200
with message-id
and subject line Re: Bug#962556: pycuda needs a binary upload for the Boost
1.71 transition
has caused the Debian Bug report #962556,
regarding pycuda needs a binary upload for the Boost 1.71 transition
to be marked as done.
This
Your message dated Tue, 09 Jun 2020 20:29:45 +
with message-id
and subject line Bug#962554: fixed in libgff 1.0-4
has caused the Debian Bug report #962554,
regarding libgff: autopkgtest failure: g++: command not found
to be marked as done.
This means that you claim that the problem has been
Your message dated Tue, 09 Jun 2020 16:17:09 -0400
with message-id <3243332.62c0MyHNQ3@t450>
and subject line Re: Bug#954505: kitinerary: FTBFS: phonenumber.pb.h:17:2:
error: #error This file was generated by an older version of protoc which is
has caused the Debian Bug report #954505,
regarding
Processing commands for cont...@bugs.debian.org:
> # FTBFS bugs are serious
> severity 962555 serious
Bug #962555 [src:scilab] scilab: FTBFS with libicu (>= 66)
Severity set to 'serious' from 'grave'
> tags 962555 + ftbfs
Bug #962555 [src:scilab] scilab: FTBFS with libicu (>= 66)
Added tag(s)
Processing control commands:
> severity -1 normal
Bug #962300 [src:dmraid] dmraid: dmraid fails do install in a debootstrapped
chroot
Severity set to 'normal' from 'grave'
--
962300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962300
Debian Bug Tracking System
Contact
Dear maintainers,
On 25/05/2020 21.20, Paul Gevers wrote:
> On 12-03-2020 16:05, Paul Gevers wrote:
> The tests are passing in unstable, which typically hints at a mismatch
> of versions. I scheduled a test run with php-defaults from unstable and
> the tests now pass. If I understand correctly,
On Tue, 09 Jun 2020 at 15:21:37 -0400, Olek Wojnar wrote:
> On Tue, Jun 9, 2020 at 6:12 AM Adrian Bunk <[1]b...@debian.org> wrote:
> > I wonder if the real fix shouldn't be for cegui-mk2 to stop exporting a
> pile
> > of Boost symbols...
>
>
> I would love that. Any advice on a
Source: pycuda
Version: 2018.1.1-4
Severity: serious
Tags: ftbfs
Control: block 961995 with -1
pycuda needs a binary upload for the Boost 1.71 transition,
it cannot be autobuilt due to the build dependency on a
pacakge in non-free.
Processing control commands:
> block 961995 with -1
Bug #961995 [release.debian.org] transition: boost-defaults
961995 was blocked by: 960378 962390 960381 962288 948127 962070 953871 958156
960414 949837 953873 960413 960424 960418 955581 960383 962252 962173 959463
960385 960331 959573 948122
Control: severity -1 normal
On 09/06/2020 10.43, Lukasz Stelmach wrote:
> I assume, however,that in case of chroot environmets running udevadm
> isn't crucial for a successful installation. I was thinking, maybe run
> udevadm only if /sys is mounted like this?
systemd/udev already uses this
Processing commands for cont...@bugs.debian.org:
> tags 961841 + fixed-upstream
Bug #961841 [src:fontforge] fontforge FTBFS on 64bit big endian: test failures
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
961841:
On Tue, Jun 09, 2020 at 07:08:01PM +0200, Jérémy Lal wrote:
> Le mar. 9 juin 2020 à 18:37, gregor herrmann a écrit :
> > # unshare -n
> > # ip li set lo up
> > # ip li add dummy0 type dummy
> > # ip li set dummy0 up
> Thanks, it doesn't yield the exact same conditions, though ?
On Tue, Jun 09, 2020 at 03:21:37PM -0400, Olek Wojnar wrote:
>
> Thanks for the bug report and both of your comments. The number of times
> I've had to re-upload this package due to symbol issues is really getting
> excessive, it seems.
>...
> Any advice on this? I really want to do what's "right"
Source: scilab
Severity: grave
Version: 6.1.0+dfsg1-3
Tags: sid bullseye
X-Debbugs-CC: jpu...@debian.org
Dear Debian scilab maintainers,
During a local rebuild of your package, it seems that package scilab
currently FTBFS against new version of libicu library:
==
In file
Source: libgff
Version: 1.0-3
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainer(s),
You recently added an autopkgtest to your package libgff, great.
However, it fails. Currently this failure is blocking the
Source: gffread
Version: 0.11.8-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, gff2ap...@packages.debian.org
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:gff2aplot
Dear maintainer(s),
With a recent upload of gff2aplot the
Processing control commands:
> affects -1 src:gff2aplot
Bug #962553 [src:gffread] gffread: autopkgtest needs update for new version of
gff2aplot: warning on stderr
Added indication that 962553 affects src:gff2aplot
--
962553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962553
Debian Bug
Processing control commands:
> found -1 libgclib/0.11.9-1
Bug #962550 [src:libgclib, src:gffread] libgclib breaks gffread autopkgtest:
Segmentation fault
Marked as found in versions libgclib/0.11.9-1.
> found -1 gffread/0.11.8-1
Bug #962550 [src:libgclib, src:gffread] libgclib breaks gffread
Source: libgclib, gffread
Control: found -1 libgclib/0.11.9-1
Control: found -1 gffread/0.11.8-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of libgclib the
Thanks for the bug report and both of your comments. The number of times
I've had to re-upload this package due to symbol issues is really getting
excessive, it seems.
On Tue, Jun 9, 2020 at 6:12 AM Adrian Bunk wrote:
> On Tue, Jun 09, 2020 at 11:24:27AM +0200, Stephen Kitt wrote:
> > Le
Package: libssl3
Version: 3.0.0~~alpha1-1
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 files.
Preparing to unpack
Hi Dod,
On 09/06/2020 19.29, Dominique Dumont wrote:
> Test method of libuv has recently changed. I've changed debian/rules to use
> cmake instead of autotools and the package builds fine.
>
> Unfortunately, I don't see a way to build the test executable without
> building
> and linking a
Processing commands for cont...@bugs.debian.org:
> # this is all done now
> close 951667
Bug #951667 [src:check] src:check: fails to migrate to testing for too long
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
951667:
On Fri, Aug 30, 2019 at 07:49:29AM +, Matthias Klose wrote:
> Package: src:qpid-python
> Version: 1.37.0+dfsg-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
>
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2
Étienne Mollier writes:
> Thank you for the workaround!
No problem; happy to have been of help (and that it in fact worked).
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Control: close 962523
Duplicate of #962320.
On samedi 30 mai 2020 20:15:57 CEST you wrote:
> With a recent upload of libuv1 the autopkgtest of libuv1 fails in
> testing when that autopkgtest is run with the binary packages of libuv1
> from unstable.
Test method of libuv has recently changed. I've changed debian/rules to use
cmake instead
Hi Aaron,
Aaron M. Ucko, on 2020-06-09 10:32:20 -0400:
> Andreas Tille writes:
>
> > On Tue, Jun 09, 2020 at 02:25:58PM +0200, Étienne Mollier wrote:
> >> My current impression is that makeblastdb is unable to work
> >> properly on most 32 bits machines, because the amount of memory
> >>
Le mar. 9 juin 2020 à 18:37, gregor herrmann a écrit :
> On Tue, 09 Jun 2020 15:35:37 +0200, Jérémy Lal wrote:
>
> > Is there a simple way to setup the network locally so i can reproduce it
> ?
> > Naive attempts (like disabling IPv4 on the wan network) failed.
>
> Niko and Dom came up with this
On Tue, Jun 09, 2020 at 06:28:05PM +0200, olivier sallou wrote:
> options:
>
> * simply remove 32bit package from Debian (though should work on
> *small* datasets).
That would affect a lot of rdepends and thus a lot of work filling
ROM bugs.
> more and more systems are going to 64bit only,
close 962517 1.3.10-1
thanks
This was fixed with the new upstream version as uploaded per
https://tracker.debian.org/news/1151783/accepted-fwupd-1310-1-source-into-unstable/
.
Processing commands for cont...@bugs.debian.org:
> close 962517 1.3.10-1
Bug #962517 [src:fwupd] CVE-2020-10759
Marked as fixed in versions fwupd/1.3.10-1.
Bug #962517 [src:fwupd] CVE-2020-10759
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
On Mon, 08 Jun 2020 10:18:09 +0300, Niko Tyni wrote:
> This seems to be a wider issue. Copying the debian-perl list for
> discussion.
Thanks for the analysis!
> I'm left wondering if the IO::Socket::IP default behaviour is desirable,
> or whether we should try to change it (maybe to special
On Tue, 09 Jun 2020 15:35:37 +0200, Jérémy Lal wrote:
> Is there a simple way to setup the network locally so i can reproduce it ?
> Naive attempts (like disabling IPv4 on the wan network) failed.
Niko and Dom came up with this recipe:
# unshare -n
# ip li set lo up
# ip li add
OpenMW 0.46 has been released and I've uploaded it here, it just
someone kind and just to review and upload. :)
https://salsa.debian.org/games-team/openmw
Once uploaded and built, this bug should be closed.
Cheers,
Bret
Le mar. 9 juin 2020 à 16:47, Aaron M. Ucko a écrit :
> Andreas Tille writes:
>
> > On Tue, Jun 09, 2020 at 02:25:58PM +0200, Étienne Mollier wrote:
> >> My current impression is that makeblastdb is unable to work
> >> properly on most 32 bits machines, because the amount of memory
> >> needing
Hi Josch,
Johannes Schauer wrote:
> > But then again, in the meanwhile we know that this isn't a packaging
> > issue but an LXC issue (https://bugs.debian.org/961584) and hence should be
> > able to ignore it.
>
> The salsa CI team implemented a workaround for that 10 days ago:
>
>
Hi Sébastien,
> > Security team, would you like an update for stretch and/or buster to
> > address these issues? It's fixed in sid, experimental as well as
> > jessie LTS. Bullseye is just pending migration time AFAICT.
[…]
> yes, that'd be fine. Is there any chance you could also piggyback the
>
Processing commands for cont...@bugs.debian.org:
> block 961995 with 962533
Bug #961995 [release.debian.org] transition: boost-defaults
961995 was blocked by: 953871 954648 948407 954351 962229 962253 954711 955579
960427 960426 962287 962286 953873 960416 962251 960331 959479 962070 962390
Source: mlpack
Version: 3.3.1-1
Severity: serious
Tags: ftbfs
It seems Boost 1.67 -> 1.71 increased something:
https://buildd.debian.org/status/fetch.php?pkg=mlpack=mips64el=3.3.1-1%2Bb1=1591444281=0
...
/usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat
Hi Axel,
Quoting Axel Beckert (2020-06-09 16:26:59)
> > But it's now two weeks since this was fixed in git and no upload has
> > happened even though this bug is RC severity.
>
> This was mostly because autopkgtests were, well, are still failing on
> Salsa and it was initially unclear, why.
>
>
Processing control commands:
> reassign -1 src:boost1.71
Bug #962320 [libfacter3.11.0] facter crashes with "free(): invalid pointer"
Bug reassigned from package 'libfacter3.11.0' to 'src:boost1.71'.
No longer marked as found in versions facter/3.11.0-4.1.
Ignoring request to alter fixed versions
Control: reassign -1 src:boost1.71
Control: reassign 962527 src:boost1.71
Control: reassign 962523 src:boost1.71
Control: forcemerge -1 962527 962523
Control: affects -1 libfacter3.11.0 puppet facter
Control: retitle -1 libboost-*1.71.0 packages need Breaks: libboost-*1.67.0
On Sat, Jun 06, 2020
Processing control commands:
> tags 952499 + patch
Bug #952499 [src:python-csa] python-csa: needs a source-only upload
Added tag(s) patch.
> tags 952499 + pending
Bug #952499 [src:python-csa] python-csa: needs a source-only upload
Added tag(s) pending.
--
952499:
Processing commands for cont...@bugs.debian.org:
> retitle 959573 facter FTBFS with yaml-cpp 0.6.3
Bug #959573 [src:facter] facter: FTBFS: dh_auto_test: error: cd
obj-x86_64-linux-gnu && make -j4 test ARGS\+=-j4 returned exit code 2
Bug #960412 [src:facter] facter: FTBFS with boost 1.71
Changed
Your message dated Tue, 09 Jun 2020 14:48:43 +
with message-id
and subject line Bug#962522: fixed in krb5 1.17-10
has caused the Debian Bug report #962522,
regarding krb5-kdc: LDAP configuration broke
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:
> found 962517 0.7.4-2
Bug #962517 [src:fwupd] CVE-2020-10759
Marked as found in versions fwupd/0.7.4-2.
> found 962517 1.2.5-2
Bug #962517 [src:fwupd] CVE-2020-10759
Marked as found in versions fwupd/1.2.5-2.
> found 962517 1.3.9-4
Bug #962517
Your message dated Tue, 09 Jun 2020 14:48:43 +
with message-id
and subject line Bug#962522: fixed in krb5 1.17-10
has caused the Debian Bug report #962522,
regarding libkadm5srv-mit11: krb5 admin programs are unable to find master key
stash
to be marked as done.
This means that you claim
Hi,
I need to admit that the package does not even build for me. I
had to add a patch to fix the includes and my attempt to rebuild
the package ends in:
...
/usr/bin/ld: ./source/svm/svm.cpp:794: undefined reference to
`MothurOut::mothurOutEndLine()'
/usr/bin/ld: ./source/svm/svm.cpp:849:
Hi Andreas,
Yes definitely, this is long overdue. I have a report due for submission
tonight, so I'll get to this tomorrow for sure.
Regards,
Pranav
On Tue, 9 Jun, 2020, 7:41 PM Andreas Tille, wrote:
> Hi Pranav,
>
> since you dealt with tests in this package could you please have
> a look?
>
Andreas Tille writes:
> On Tue, Jun 09, 2020 at 02:25:58PM +0200, Étienne Mollier wrote:
>> My current impression is that makeblastdb is unable to work
>> properly on most 32 bits machines, because the amount of memory
>> needing to be addressed by the process looks like it might
>> exceed too
Hi Josch,
Johannes Schauer wrote:
> On Tue, 26 May 2020 17:52:16 + Axel Beckert wrote:
> > Bug #958414 in equivs 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:
> >
> >
Hi Michael,
could you please have a look at this bug or try to redirect it to our
GSoC students?
Kind regards
Andreas.
On Thu, May 21, 2020 at 05:23:38PM +0200, Matthias Klose wrote:
> This also makes sopt ftbfs. Please patch ./include/spdlog/tweakme.h to set
> the
> expected default.
Hi Pranav,
since you dealt with tests in this package could you please have
a look?
Kind regards
Andreas.
On Sat, May 16, 2020 at 02:50:12PM +0300, Adrian Bunk wrote:
> Source: tree-puzzle
> Version: 5.3~rc16+dfsg-1
> Severity: serious
> Tags: ftbfs
>
> Based on the "Important remark"
Processing commands for cont...@bugs.debian.org:
> reassign 962522 krb5-kdc
Bug #962522 [libkadm5srv-mit11] libkadm5srv-mit11: krb5 admin programs are
unable to find master key stash
Bug reassigned from package 'libkadm5srv-mit11' to 'krb5-kdc'.
No longer marked as found in versions krb5/1.17-9.
Hi,
On Tue, 26 May 2020 17:52:16 + Axel Beckert wrote:
> Bug #958414 in equivs 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:
>
>
Package: facter
Version: 3.11.0-4.1
Severity: grave
Running facter crashes right away on startup with an invalid pointer
being passed to free().
~# facter
free(): invalid pointer
Aborted
Stacktrace:
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1
Hi Étienne,
I'm just including the Uploaders of ncbi-blast+ into this conversation
to make sure the information reaches the experts. We should probably
reassign the bug but I'll leave this to those who know better.
Thanks a lot for your analysis
Andreas.
On Tue, Jun 09, 2020 at
On Mon, 8 Jun 2020 10:18:09 +0300 Niko Tyni wrote:
> On Sat, Jun 06, 2020 at 10:22:58AM +0300, Adrian Bunk wrote:
> > Source: libmojolicious-perl
> > Version: 8.52+dfsg-1
> > Severity: serious
> > Tags: ftbfs
> >
> >
https://buildd.debian.org/status/logs.php?pkg=libmojolicious-perl=8.52+dfsg-1
>
On 06/06 10:15, Chris Lamb wrote:
> > python-django: CVE-2020-13254 CVE-2020-13596
>
> Security team, would you like an update for stretch and/or buster to
> address these issues? It's fixed in sid, experimental as well as
> jessie LTS. Bullseye is just pending migration time AFAICT.
Hi Chris,
Hi all,
Andreas Tille, on 2020-06-08 16:01:33 +0200:
> any voluntee to follow this hint of upstream?
Having a look a this issue, here is what I can tell so far.
> > Perhaps makeblastdb itself failed (and our wrapper didn't notice)? Those
> > are the first files looked for after calling
Yes, that. I look regularly at
https://qa.debian.org/dose/debcheck/src_testing_main/ as we (the release
team) require packages to be buildable in testing (we have some
tolerance as the migration of build dependencies isn't guaranteed when
checking if a package may migrate). Please help the rust
Package: puppet
Version: 5.5.19-1
Severity: critical
Dear Maintainer,
* What led up to the situation?
Any puppet command throws segmentation fault
* What exactly did you do (or not do) that was effective (or
ineffective)?
First run of puppet help
$ puppet help
Processing control commands:
> fixed -1 3.6.6-1
Bug #962512 [src:nethack] nethack: Security issues in Buster's nethack 3.6.1
Ignoring request to alter fixed versions of bug #962512 to the same values
previously set
> severity -1 important
Bug #962512 [src:nethack] nethack: Security issues in
Control: fixed -1 3.6.6-1
Control: severity -1 important
Am 09.06.20 um 03:25 schrieb Jason L. Quinn:
[...]
> Seems like the vunerabilities are important enough to warrant an upgrade in
> Buster.
I'm not against an update of nethack in Buster. However currently such
an update would break
Your message dated Tue, 09 Jun 2020 11:00:09 +
with message-id
and subject line Bug#944020: fixed in python-libusb1 1.8-1
has caused the Debian Bug report #944020,
regarding python3-libusb1: should be named python3-usb1, since it installs a
`usb1` top-level module
to be marked as done.
This
On Tue, Jun 09, 2020 at 11:24:27AM +0200, Stephen Kitt wrote:
> Le 09/06/2020 09:59, Adrian Bunk a écrit :
> > https://buildd.debian.org/status/package.php?p=cegui-mk2
> >
> > ...
> > dpkg-gensymbols: warning: some new symbols appeared in the symbols
> > file: see diff output below
> >
1 - 100 of 121 matches
Mail list logo
