package: libgit2
version: 0.27.0+dfsg.1-0.7
severity: serious
On harris.debian.org (armhf porterbox) I got this error.
/home/praveen/libgit2-0.27.0+dfsg.1/tests/checkout/tree.c: In function
'test_che
ckout_tree__target_directory_from_bare':
Your message dated Wed, 18 Jul 2018 08:27:20 +0530
with message-id
and subject line libgit2 0.27 is in unstable
has caused the Debian Bug report #892962,
regarding libgit2: CVE-2018-8099
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Your message dated Wed, 18 Jul 2018 08:26:09 +0530
with message-id <13d050b5-a300-22c1-daa8-77082a6d7...@onenetbeyond.org>
and subject line libgit2 0.27 is in unstable
has caused the Debian Bug report #892961,
regarding libgit2: CVE-2018-8098
to be marked as done.
This means that you claim that
Processing control commands:
> tag -1 pending
Bug #903166 [src:asciidoc] asciidoc: FTBFS in buster/sid (dh_installdocs:
Cannot find "README")
Ignoring request to alter tags of bug #903166 to the same tags previously set
--
903166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903166
Debian
Control: tag -1 pending
Hello,
Bug #903166 in asciidoc 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 commands for cont...@bugs.debian.org:
> reassign 903789 wine-development
Bug #903789 [wine64-development] wine64-development: missing version 3.12-2?
Bug reassigned from package 'wine64-development' to 'wine-development'.
No longer marked as found in versions wine-development/3.12-1.
Processing commands for cont...@bugs.debian.org:
> forcemerge 903966 903789
Bug #903966 [wine-development] wine-development: FTBFS on most architectures
Unable to merge bugs because:
package of #903789 is 'wine64-development' not 'wine-development'
Failed to forcibly merge 903966: Did not alter
Source: audacious
Severity: grave
Justification: renders package unusable
Dear Maintainer,
-- System Information:
Debian Release: 9.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.9.0-3-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8,
Processing control commands:
> tag -1 pending
Bug #903166 [src:asciidoc] asciidoc: FTBFS in buster/sid (dh_installdocs:
Cannot find "README")
Added tag(s) pending.
--
903166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903166
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #903166 in asciidoc 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:
Your message dated Wed, 18 Jul 2018 08:15:23 +0800
with message-id
and subject line Re: espresso: ftbfs with GCC-8
has caused the Debian Bug report #897744,
regarding espresso: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Wed, 18 Jul 2018 00:19:07 +
with message-id
and subject line Bug#903351: fixed in latexml 0.8.2-2
has caused the Debian Bug report #903351,
regarding latexml: FTBFS in buster/sid (dh_installdocs: Cannot find "README")
to be marked as done.
This means that you claim that
Your message dated Wed, 18 Jul 2018 08:09:42 +0800
with message-id <1f4b38f9c1b26c97c9f614264f1035cd06e7e358.ca...@debian.org>
and subject line Re: slepc: ftbfs with GCC-8
has caused the Debian Bug report #897862,
regarding slepc: ftbfs with GCC-8
to be marked as done.
This means that you claim
> I run a few build commands, but I never got a file called README. What
> command did you use to generate that file?
Seems you are right and I was just stupid, sorry. Fixed, added
README.pod to the docs install file, and uploaded the packages.
Thanks for fixing.
Best
Norbert
--
PREINING
Hi,
Matthias Klose (2018-05-04):
> Package: src:cdebconf
> Version: 0.243
> Severity: normal
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-8
>
> Please keep this issue open in the bug tracker for the package it
> was filed for. If a fix in another package is
Your message dated Wed, 18 Jul 2018 07:43:37 +0900
with message-id <20180717224337.meirwyv2vxusc...@glandium.org>
and subject line Re: Bug#897821: nss: ftbfs with GCC-8
has caused the Debian Bug report #897821,
regarding nss: ftbfs with GCC-8
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
> severity 898453 grave
Bug #898453 [src:vncterm] vncterm: CVE-2018-7226: integer overflow in
vcSetXCutTextProc in VNConsole.c
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
On Tue, 17 Jul 2018 21:31:31 +0200, Stefan Fritsch wrote:
> Thanks, Gregor. Unfortunately, that is not helpful, yet. Please try again
> with
> ldd instead of readelf -d.
Sure, here we go:
# pid=6855; for i in $(awk '{ print $6 }' < /proc/$pid/maps|sort -u|grep /) ;
do ldd $i|grep libcap &&
Processing commands for cont...@bugs.debian.org:
> affects 903767 release.debian.org
Bug #903767 [src:linux] Stretch kernel 4.9.110-1 boot-loops with Xen Hypervisor
4.8
Bug #903800 [src:linux] linux-image-4.9.0-7-amd64: general protection fault /
kernel panic at boot
Bug #903821 [src:linux]
Processing commands for cont...@bugs.debian.org:
> reassign 902295 nvidia-driver
Bug #902295 [src:linux] linux-image-4.16.0-2-amd64: invalid opcode / general
protection fault with nvidia graphics module
Bug reassigned from package 'src:linux' to 'nvidia-driver'.
No longer marked as found in
Processing control commands:
> tag -1 confirmed patch pending
Bug #903838 [src:linux] Unable to mount ext4 filesystem with meta_bg flag
Added tag(s) pending and patch.
--
903838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903838
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: tag -1 confirmed patch pending
On Sun, 2018-07-15 at 18:03 +0200, deb...@heinopeters.de wrote:
> Package: linux-image-4.9.0-7-amd64
> Version: 4.9.110-1
>
> Mounting ext4 filesystem with meta_bg set fails with "structure needs
> cleaning".
> Mounting the same filesystem with the kernel
Source: cipux-rbac
Version: 3.4.0~svn2868-1
Severity: serious
Justification: fails to build from source
cipux-rbac/experimental cannot be built any longer since libcipux-perl,
libmodule-build-cipux-perl have been removed from unstable.
Should cipux-rbac be removed as well?
Andreas
Your message dated Tue, 17 Jul 2018 19:49:14 +
with message-id
and subject line Bug#897705: fixed in apr 1.6.3-3
has caused the Debian Bug report #897705,
regarding apr: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Processing commands for cont...@bugs.debian.org:
> affects 903838 + release.debian.org
Bug #903838 [src:linux] Unable to mount ext4 filesystem with meta_bg flag
Added indication that 903838 affects release.debian.org
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
> # regression from stable, but disputably maybe downgrade to imortant
> severity 903838 serious
Bug #903838 [src:linux] Unable to mount ext4 filesystem with meta_bg flag
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
On Tuesday, 17 July 2018 21:12:48 CEST gregor herrmann wrote:
> On Tue, 17 Jul 2018 20:54:02 +0200, Stefan Fritsch wrote:
> > Can one of you please check how libcap-ng is pulled into the process.
> > Something like this should do the trick (replace XXX with the pid of one
> > of
> > your apache
Processing control commands:
> tags -1 patch
Bug #897885 [src:wbar] wbar: ftbfs with GCC-8
Added tag(s) patch.
--
897885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 patch
On Fri, 04 May 2018 12:24:04 + Matthias Klose wrote:
> Package: src:wbar
> Version: 2.3.4-7
> Severity: normal
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-8
> In file included from /usr/include/gtk-2.0/gtk/gtk.h:89,
>
Le mardi 17 juillet 2018 à 15:06:14-0400, Sandro Tosi a écrit :
> no need, i can upgrade the package myself when needed, but thanks for the
> offer.
>
> since astroid/pylint only support python 3.4+, it is not as simple as
> package the new version and upload it; i'm not even (yet) sure buster
>
On Tue, 17 Jul 2018 20:54:02 +0200, Stefan Fritsch wrote:
> Can one of you please check how libcap-ng is pulled into the process.
> Something like this should do the trick (replace XXX with the pid of one of
> your apache processes, you need to be root to do this) :
>
> pid=XXX; for i in $(awk
Your message dated Tue, 17 Jul 2018 19:08:00 +
with message-id <2ae09b00-216e-48e5-2555-b76bf7cf3...@debian.org>
and subject line Re: [Pkg-rust-maintainers] Bug#897854: rustc: ftbfs with GCC-8
has caused the Debian Bug report #897854,
regarding rustc: ftbfs with GCC-8
to be marked as done.
Your message dated Tue, 17 Jul 2018 19:06:32 +
with message-id
and subject line Bug#897834: fixed in pcre3 2:8.39-10
has caused the Debian Bug report #897834,
regarding pcre3: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
no need, i can upgrade the package myself when needed, but thanks for the offer.
since astroid/pylint only support python 3.4+, it is not as simple as
package the new version and upload it; i'm not even (yet) sure buster
should have 2.0 but maybe it should to 1.9
On Tue, Jul 17, 2018 at 2:41 PM
On Friday, 29 June 2018 10:35:32 CEST mer.at wrote:
> when i do an "apachectl graceful" or "apachectl restart", i get
> segfaults.
I don't think this is a bug in apache, at least not directly.
> if i then do a /etc/init.d/apache2 restart, it works normally
> /etc/init.d/apache2 restart and
On Monday, July 16 2018, I wrote:
> On Sunday, July 01 2018, Fabian Wolff wrote:
>
>> Hi Jonathan,
>>
>> On Fri, 29 Jun 2018 22:21:54 +0100, Jonathan Wiltshire wrote:
>>> Would you like to co-maintain? If so, please add yourself to uploaders and
>>> prepare a maintainer upload (rather than NMU).
Control: tag -1 patch
On Fri, Jan 19, 2018 at 06:23:25AM +0200, Adrian Bunk wrote:
> Package: libsmokeqt4-dev
> Version: 4:4.14.3-1.2
> Severity: serious
> Control: affects -1 src:qt4-perl
>
> qt4-perl FTBFS:
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/qt4-perl.html
>
Processing control commands:
> tag -1 patch
Bug #887687 [libsmokeqt4-dev] libsmokeqt4-dev: broken symlinks and causes
qt4-perl FTBFS
Added tag(s) patch.
--
887687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: ruby-doorkeeper
Version: 4.2.0-1
Severity: grave
Tags: security upstream
Forwarded: https://github.com/doorkeeper-gem/doorkeeper/issues/891
Hi,
The following vulnerability was published for ruby-doorkeeper.
CVE-2018-1000211[0]:
| Doorkeeper version 4.2.0 and later contains a Incorrect
Your message dated Tue, 17 Jul 2018 18:04:04 +
with message-id
and subject line Bug#903016: fixed in libvirt-python 4.5.0-1
has caused the Debian Bug report #903016,
regarding python3-libvirt: import fails with current python interpreter in sid
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> severity 897734 serious
Bug #897734 [src:darkradiant] darkradiant: ftbfs with GCC-8
Severity set to 'serious' from 'normal'
> severity 897696 serious
Bug #897696 [src:abinit] abinit: ftbfs with GCC-8
Severity set to 'serious' from 'normal'
>
Your message dated Tue, 17 Jul 2018 17:04:06 +
with message-id
and subject line Bug#903793: fixed in gmap 2018-07-04-1
has caused the Debian Bug report #903793,
regarding libgmap1-dev: broken symlink: /usr/lib/x86_64-linux-gnu/libgmap.so ->
libgmap.so.1.0.0
to be marked as done.
This means
I can confirm that a build of the 4.9 series against 4.9.112 boots under Xen PV
with the following patches removed:
--- linux-4.9.110/debian/patches/series 2018-07-15 18:05:38.614069505 +
+++ linux-4.9.112/debian/patches/series 2018-07-16 03:22:09.551240940 +
@@ -12,7 +12,6 @@
Your message dated Tue, 17 Jul 2018 16:22:40 +
with message-id
and subject line Bug#903185: fixed in openstack-doc-tools 1.6.0-3
has caused the Debian Bug report #903185,
regarding openstack-doc-tools: FTBFS in buster/sid (dh_installman: Cannot find
"doc/build/man/openstack-doc-test.1")
to
Your message dated Tue, 17 Jul 2018 18:19:21 +0200
with message-id <20180717161921.lqq7vfpnz2qei...@var.youpi.perso.aquilenet.fr>
and subject line Re: Bug#903366: starpu: FTBFS in buster/sid (dpkg-shlibdeps:
error: cannot find library libsocl-1.2.so.0)
has caused the Debian Bug report #903366,
* Drew Parsons [2018-07-17 00:44]:
On Tue, 2018-07-17 at 00:30 +0800, Drew Parsons wrote:
On Mon, 2018-07-16 at 13:54 +0200, Rafael Laboissière wrote:
I tried to build the package using the tip of the Mercurial
repository
Weird though, https://wiki.octave.org/Odepkg points at
On Tue, Jul 17, 2018 at 04:11:15PM +0200, Samuel Thibault wrote:
> I have just tried with
>
> pdebuild -- --basetgz /var/cache/pbuilder/base-buster.tgz --debbuildopts -B
>
> without seeing any issue. Is your autobuilder chroot really clean?
Yes, my autobuilder chroot was really clean. However,
On Wed, 18 Jul 2018 00:09:54 +1000 TMC wrote:
> does commit 1adc34adc3447c34926994b87db5d929f5ab45b5 on top of
> Debian’s 4.9.110-1 kernel solvexen dom0 boot issue?
Unfortunately I have no control over the host, so I cannot test dom0. I could
only test inside a single domU.
Am 17.07.2018 um 16:25 teilte Norbert Preining mit:
Hi,
Unfortunately, I don't think this is not the proper fix.
README should be generated as far as I see, but the call done by the OP
(dpkg-buildpackage -A) somehow triggered a build process without
generating README.
So the proper fix is to
Hi Hilmar,
> Has been fixed on salsa.
Unfortunately, I don't think this is not the proper fix.
README should be generated as far as I see, but the call done by the OP
(dpkg-buildpackage -A) somehow triggered a build process without
generating README.
So the proper fix is to see why this
does commit 1adc34adc3447c34926994b87db5d929f5ab45b5 on top of
Debian’s 4.9.110-1 kernel solvexen dom0 boot issue?
--
--
GPG key fingerprint: 07DF B95B DB58 57B6 9656 682E 830A D092 288E F017
GPG public key available on pgp(dot)net key server
Processing control commands:
> tags -1 + unreproducible moreinfo
Bug #903366 [src:starpu] starpu: FTBFS in buster/sid (dpkg-shlibdeps: error:
cannot find library libsocl-1.2.so.0)
Added tag(s) moreinfo and unreproducible.
--
903366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903366
Control: tags -1 + unreproducible moreinfo
Hello,
Santiago Vila, le lun. 09 juil. 2018 00:07:03 +, a ecrit:
> dpkg-shlibdeps: error: cannot find library libsocl-1.2.so.0 needed by
> debian/starpu-examples/usr/lib/x86_64-linux-gnu/starpu/examples/socl/testmap
> (ELF format: 'elf64-x86-64'
On Tue, 17 Jul 2018 11:11:37 +0200 =?utf-8?Q?Michael_La=C3=9F?=
wrote:
> I can confirm that applying 1adc34adc3447c34926994b87db5d929f5ab45b5 on top of
> Debian’s 4.9.110-1 kernel solves the issue here on a Xen PV guest.
>
Processing control commands:
> tags -1 + patch
Bug #903581 [valgrind] valgrind: can't understand libc6 symbols: ELF section
outside all mapped regions
Added tag(s) patch.
--
903581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903581
Debian Bug Tracking System
Contact
Control: tags -1 + patch
patch taken from the trunk:
http://launchpadlibrarian.net/378923838/valgrind_1%3A3.13.0-2ubuntu4_1%3A3.13.0-2ubuntu5.diff.gz
Package: wine-development
Version: 3.12-2
Severity: serious
This package failed to build on the build daemons
on amd64 and arm*.
On amd64:
row_server_p.c: In function '__finally_IWineRowServer_AddRefRows_Stub':
row_server_p.c:7751:35: error: passing argument 1 of
Your message dated Tue, 17 Jul 2018 13:03:59 +
with message-id
and subject line Bug#903184: fixed in ohcount 3.1.1-2
has caused the Debian Bug report #903184,
regarding ohcount: FTBFS in buster/sid (dh_installdocs: Cannot find "README")
to be marked as done.
This means that you claim that
I’ll pile on top of this: domUs crash with the kernel as well, with a GPF.
Looks like any Xen + 4.9.0-7 = Crash, regardless of it being a domU or dom0.
John
> On 15 Jul 2018, at 21:55, Sebastien KOECHLIN wrote:
>
> Package: src:linux
> Followup-For: Bug #903821
>
> When booting with the new
On 07/17/2018 12:39 AM, Benoît Tonnerre wrote:
> Hi,
>
> I tested this workaround : I confirm that it works on Xen host, but not
> on Xen guest.
> If you try to start a vm with latest kernel i.e. theses parameters in
> cfg file :
>
> #
> # Kernel + memory size
> #
> kernel =
I can confirm that applying 1adc34adc3447c34926994b87db5d929f5ab45b5 on top of
Debian’s 4.9.110-1 kernel solves the issue here on a Xen PV guest.
Your message dated Tue, 17 Jul 2018 08:40:40 +
with message-id
and subject line Bug#871163: fixed in reposurgeon 3.44-3
has caused the Debian Bug report #871163,
regarding reposurgeon: FTBFS: dh_auto_test: make -j16 check returned exit code 2
to be marked as done.
This means that you claim
Am 09.07.2018 um 00:08 teilte Santiago Vila mit:
Hi,
make[1]: Leaving directory '/<>'
# install documentation file
mkdir -p debian/latexml/usr/share/texmf/doc/latexml
cp manual.pdf debian/latexml/usr/share/texmf/doc/latexml/
find debian/latexml -type f -name .packlist | xargs rm -f
dh_testdir
On Tue, Jul 17, 2018 at 09:23:30AM +0200, Alex Mestiashvili wrote:
>
> I plan to drop libgmap1[0], as there is no use cases so far. (also no
> rdepends).
> Was about to do it long time ago but failed due to ENOTIME...
>
>
> I'll try to look later today on the package and may be upload the new
>
Processing control commands:
> severity -1 serious
Bug #888255 [src:netty-3.9] RM? Upstream dropped support, security important,
newer version packaged
Severity set to 'serious' from 'normal'
--
888255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888255
Debian Bug Tracking System
Contact
Package: mbrola-cn1
Version: 0.0.20-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Hello,
mbrola-cn1 just does not work at all with the provided examples:
€ mbrola /usr/share/mbrola/cn1/cn1 "/usr/share/doc/mbrola-cn1/examples/Moon
Represents My Heart.pho" "Moon
Hi Andreas,
On 07/17/2018 08:19 AM, Andreas Tille wrote:
> Hi Alexandre,
>
> On Sat, Jul 14, 2018 at 11:41:01PM +0200, Andreas Beckmann wrote:
>> Depends: gmap (= 2017-11-15-1) | libgmap1 (= 2017-11-15-1)
>>
>> which does not sound like a good idea if gmap does not provide the required
>> shared
Processing control commands:
> block 828451 with -1
Bug #828451 [src:netty-tcnative] netty-tcnative: FTBFS with openssl 1.1.0
828451 was not blocked by any bugs.
828451 was blocking: 871056
Added blocking bug(s) of 828451: 903956
--
828451:
Your message dated Tue, 17 Jul 2018 06:49:00 +
with message-id
and subject line Bug#903867: fixed in cod-tools 2.2+dfsg-3
has caused the Debian Bug report #903867,
regarding cod-tools: FTBFS when built with dpkg-buildpackage -A
to be marked as done.
This means that you claim that the problem
Control: tags 903867 + |pending Dear |Santiago,
many thanks for the report and hints about how to fix it. I will soon upload
the fixed package.
Best wishes,
Andrius
||
--
Andrius Merkys
Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325
LT-10257 Vilnius, Lithuania
Processing control commands:
> tags 903867 + |pending Dear |Santiago,
Unknown tag/s: |pending, Dear, |Santiago.
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
Hi Alexandre,
On Sat, Jul 14, 2018 at 11:41:01PM +0200, Andreas Beckmann wrote:
> Depends: gmap (= 2017-11-15-1) | libgmap1 (= 2017-11-15-1)
>
> which does not sound like a good idea if gmap does not provide the required
> shared library.
I've fixed this in Git and also updated to the latest
72 matches
Mail list logo
