Processing commands for cont...@bugs.debian.org:
> severity 926784 grave
Bug #926784 [firehol] firehol: Please document usage of iptables-legacy
Severity set to 'grave' from 'wishlist'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
926784:
On Fri, Feb 08, 2019 at 11:37:20PM +0100, Moritz Muehlenhoff wrote:
> Package: jabref
> Severity: grave
> Tags: security
>
> This was assigned CVE-2018-1000652:
> https://github.com/JabRef/jabref/issues/4229
> https://github.com/JabRef/jabref/commit/89f855d76713b4cd25ac0830c719cd61c511851e
Hello
Processing commands for cont...@bugs.debian.org:
> block 926350 with 926907
Bug #926350 [python3-django-casclient] CAS middleware incompatible with Django
>= 1.10
926350 was not blocked by any bugs.
926350 was not blocking any bugs.
Added blocking bug(s) of 926350: 926907
> thanks
Stopping
On 11.04.19 20:24, Paul Gevers wrote:
> Hi doko,
>
> On 07-04-2019 12:08, Samuel Thibault wrote:
>>> I disagree. I'll do the next upload with Samuel's proposed patches, not
>>> enabling that by default, together with the planned security update. Then
>>> people can start testing if the wrapper
Processing control commands:
> tag -1 pending
Bug #834089 [socklog-run] runit: breaks users of runit: ln: failed to create
symbolic link '/etc/service/bcron-sched': No such file or directory
Ignoring request to alter tags of bug #834089 to the same tags previously set
--
834089:
Processing control commands:
> tag -1 pending
Bug #857208 [src:socklog] socklog: building with -A doesn't put the changelog
in usr/share/doc/socklog-run/changelog.Debian.gz
Ignoring request to alter tags of bug #857208 to the same tags previously set
--
857208:
Control: tag -1 pending
Hello,
Bug #834089 in socklog 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:
Control: tag -1 pending
Hello,
Bug #857208 in socklog 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 Thu, 11 Apr 2019 22:44:51 +0100
with message-id <20190411214450.ga2...@laptop-t.office.oeko.net>
and subject line Re: Bug#926859: X Server Does Not Start
has caused the Debian Bug report #926859,
regarding X Server Does Not Start
to be marked as done.
This means that you claim
Processing control commands:
> tags -1 patch
Bug #919377 [src:mysql++] mysql++: FTBFS with mariadb-10.3:
dbdriver.cpp:260:10: error: 'CLIENT_LONG_PASSWORD' was not declared in this
scope
Added tag(s) patch.
--
919377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919377
Debian Bug
Control: tags -1 patch
Hi!
On Tue, 2019-04-02 at 09:53:47 +0300, Otto Kekäläinen wrote:
> Could you please check if it is still valid and happening in Debian
> unstable there has been several updates MariaDB client libraries /
> connector C libraries recently?
A rebuild quickly shows this is
* Ben Wong , 2017-12-22, 17:03:
Wait, that bug again? I fixed that a long time ago.
Indeed, you did. However, the critical part of the fix was regenerating
the configure script (and to lesser extent config.h.in) from source.
This was done at build time by adding:
Control: tag -1 pending
Hello,
Bug #923003 in qt4-x11 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 #923003 [src:qt4-x11] CVE-2018-19873 CVE-2018-19871 CVE-2018-19870
Added tag(s) pending.
--
923003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package fontconfig
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Source: lighttpd
Version: 1.4.53-3
Severity: grave
Tags: security upstream
Forwarded: https://redmine.lighttpd.net/issues/2945
Hi,
The following vulnerability was published for lighttpd.
CVE-2019-11072[0]:
| lighttpd before 1.4.54 has a signed integer overflow, which might
| allow remote
Hi. I have not been looking forward to having no java accessibility in
buster and it is really good to see the work Samuel has done on this
bug. I'd really hate to see buster release without some mechanism for
blind users like myself to use Java applications. Also, in the long
run, if buster
Hi doko,
On 07-04-2019 12:08, Samuel Thibault wrote:
>> I disagree. I'll do the next upload with Samuel's proposed patches, not
>> enabling that by default, together with the planned security update. Then
>> people can start testing if the wrapper works.
>
> Well, I'm afraid that what will
Santiago Vila wrote:
> Well, but I can't build packages in your machine, I have to do it in
> my machine, and it fails 50% of the time for me. Try building on a
> START1-XS instance from Scaleway (still available on Amsterdam), or
> ask me for an account in such a machine.
Thank you again for
Your message dated Thu, 11 Apr 2019 17:49:09 +
with message-id
and subject line Bug#926628: fixed in tdbcmysql 1.1.0-2
has caused the Debian Bug report #926628,
regarding tdbcmysql: hard-coded (build-)dependency on libmariadbclient18
to be marked as done.
This means that you claim that the
On Wed, Apr 10, 2019 at 11:12:17AM +0200, Matthias Klose wrote:
> On 10.04.19 10:29, Adrian Bunk wrote:
> > On Wed, Apr 10, 2019 at 10:11:29AM +0200, Matthias Klose wrote:
> >> Package: src:llvm-toolchain-7
> >> Version: 1:7.0.1-8
> >> Severity: serious
> >> Tags: sid buster
> >>
> >> underlinked
Processing commands for cont...@bugs.debian.org:
> severity 926872 grave
Bug #926872 [evolution] evolution: Spaces in mail view disappeared with recent
updates
Severity set to 'grave' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
926872:
On 2019-04-11 1:03 p.m., Toni wrote:
> Package: xserver-xorg
> Version: 1:7.7+19
> Severity: grave
>
>
>
> Hi,
>
> I am not sure whether this is the correct package to report the bug
> against, since several drivers are involved, and X stopped working for
> every setup simultanously.
>
> On
I have this bug pinned via /etc/apt/preferences.d/apt-listbugs ever
since, so I cannot upgrade this package. The bug description reads as if
I better do not dare to update, no? Any harm in simply continuing to
stay with the old un-upgraded version?
Thanks a million, I much much appreciate Debian,
I have this bug pinned via /etc/apt/preferences.d/apt-listbugs ever
since. So I cannot upgrade this package.
The bug description reads as if I better do not dare to update, no? Any
news? was this a single occurrence only?
Thanks a million, I much much appreciate Debian, and everyone who helps!
A new version addressing the bug has been prepared and Sergei will take
care to upload it. As per Sergei's suggestion I will file a bug against
release.debian.org as soon as the package gets into sid.
-- Massimo
On 4/10/19 1:54 PM, Sergei Golovan wrote:
Hi Ivo,
On Wed, Apr 10, 2019 at 2:35
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 923485 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 926251 0.18.1+dfsg1-1
Bug #926251 [freecad-common]
On Sun, 7 Apr 2019, Chris Lamb wrote:
> Santiago Vila wrote:
>
> > I tried to build this package in buster but it failed:
>
> Hm, I've just built this package 20 times in sid and the tests pass
> every time.
Well, but I can't build packages in your machine, I have to do it in
my machine, and
Your message dated Thu, 11 Apr 2019 11:33:37 +
with message-id
and subject line Bug#924650: fixed in epsilon 0.7.1-1.1
has caused the Debian Bug report #924650,
regarding epsilon ftbfs and fails autopkg tests on the buster kernel
to be marked as done.
This means that you claim that the
Package: xserver-xorg
Version: 1:7.7+19
Severity: grave
Hi,
I am not sure whether this is the correct package to report the bug
against, since several drivers are involved, and X stopped working for
every setup simultanously.
On my laptop with an Optimus graphics, X does no longer start after
Package: mesa-vdpau-drivers
Version: 18.3.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m23.0s ERROR: FAIL: Broken
Your message dated Thu, 11 Apr 2019 10:04:13 +
with message-id
and subject line Bug#924329: fixed in xastir 2.1.0-4
has caused the Debian Bug report #924329,
regarding xastir: FTBFS (magick/image-private.h: No such file or directory)
to be marked as done.
This means that you claim that the
Hi,
I pushed a patch for #924838 to Git but unfortunately there is an issue with
the build time test suite that tries to access remoto hosts:
...
debian/rules override_dh_auto_test
make[1]: Entering directory '/build/scoop-0.7.1.1'
PYBUILD_SYSTEM=custom \
PYBUILD_TEST_ARGS="cd {dir}/test;
Control: tag -1 pending
Hello,
Bug #924329 in xastir 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 #924329 [src:xastir] xastir: FTBFS (magick/image-private.h: No such file or
directory)
Added tag(s) pending.
--
924329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Package: openjdk-13-doc
Severity: grave
Justification: renders package unusable
--8<---cut here---start->8---
Unpacking openjdk-13-doc (13~12-1) ...
dpkg: error processing archive
/var/cache/apt/archives/openjdk-13-doc_13~12-1_all.deb (--unpack):
trying to
Your message dated Thu, 11 Apr 2019 08:36:39 +
with message-id
and subject line Bug#926389: fixed in wget 1.20.1-1.1
has caused the Debian Bug report #926389,
regarding wget: CVE-2019-5953
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
37 matches
Mail list logo
