Your message dated Tue, 11 Jun 2019 06:49:02 +
with message-id
and subject line Bug#929916: fixed in libreswan 3.29-1
has caused the Debian Bug report #929916,
regarding libreswan: CVE-2019-12312
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Tue, 11 Jun 2019 02:07:04 -0400
with message-id
and subject line Re: Bug#928097: chromium: crc32 build errors on arm64
has caused the Debian Bug report #928097,
regarding chromium: crc32 build errors on arm64
to be marked as done.
This means that you claim that the problem has
package: src:chromium
severity: serious
version: 75.0.3770.80-1
The latest upload fails to build on armhf due to missing intrinsics [0].
Best wishes,
Mike
[0]https://buildd.debian.org/status/fetch.php?pkg=chromium&arch=armhf&ver=75.0.3770.80-1&stamp=1560141959&raw=0
Hi Salvatore,
On Tue, Jun 11, 2019 at 6:18 AM Salvatore Bonaccorso wrote:
> On Mon, Jun 10, 2019 at 05:06:07PM +, Debian Bug Tracking System wrote:
> > sqlite3 (3.27.2-3) unstable; urgency=high
> > .
> >* Backport security related patches:
> [...]
> > - prevent aliases of window fu
Hi Laszlo,
On Mon, Jun 10, 2019 at 05:06:07PM +, Debian Bug Tracking System wrote:
> sqlite3 (3.27.2-3) unstable; urgency=high
> .
>* Backport security related patches:
[...]
> - prevent aliases of window functions expressions from being used as
>arguments to aggregate or ot
Hi Brian!
El lun., 10 jun. 2019 16:54, Brian Potkin escribió:
> Severity: critical
> thanks
>
>
>
> On Thu 25 Oct 2018 at 12:50:25 +0100, Brian Potkin wrote:
>
> > Package: okular
> > Version: 4:17.12.2-2
> > Severity: critical
> > Tags: upstream security
> >
> >
> >
> > "critical" because a do
at bottom :-
On 10/06/2019, Ansgar wrote:
> Hi,
>
>> I'm rising the severity since this causes errors in dose-debcheck, which
>> might affect QA or other infrastructure:
>
> I removed the problematic package from experimental earlier; that should
> make it a bit less urgent to upload a new versio
Processing commands for cont...@bugs.debian.org:
> severity 911844 critical
Bug #911844 [okular] okular: Prints to the wrong printer
Severity set to 'critical' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
911844: https://bugs.debian.org/cgi-bin/bu
Followup-For: Bug #871321
Hi,
I'm rising the severity to serious because tenshi violates version
ordering constraints since this bug was fixed in wheezy-security:
tenshi | 0.13-2| wheezy | source, all
tenshi | 0.13-2| stretch | source, all
tenshi | 0.13-2
Processing commands for cont...@bugs.debian.org:
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 871321 piuparts
There were no usertags set.
Usertags are now: piuparts.
> fixed 871321 0.13-2+deb7u1
Bug #871321 [src:tenshi] tenshi: CVE-
Processing commands for cont...@bugs.debian.org:
> severity 930337 important
Bug #930337 [src:linux] linux-image-4.19.0-5-amd64: mount fails when deprecated
'nobarrier' option is used in fstab
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.
Please contact me if you
Your message dated Mon, 10 Jun 2019 20:37:46 +
with message-id
and subject line Bug#930300: fixed in haskell-argon2 1.3.0.1-5
has caused the Debian Bug report #930300,
regarding libghc-argon2-dev: switch dependency to libargon2-dev
to be marked as done.
This means that you claim that the prob
Package: src:linux
Version: 4.19.37-3
Severity: critical
Justification: breaks the whole system
Hi!
Just upgraded from stretch to buster to test the whole upgrade thing.
In stretch I was using "nobarrier" option to mount my XFS filesystems. As
described in https://patchwork.kernel.org/patch/104
Hello,
I'm here looking for opinions from debian-accessibility from people with
low vision.
Samuel Thibault, le lun. 10 juin 2019 22:02:05 +0200, a ecrit:
> > whenever i have to use the linux console, i have significant
> > neurological issues, due to the blinking cursor.
>
> Oh, I did not know
gofloss gofloss, le mar. 06 juin 2017 13:52:05 -0700, a ecrit:
> apparently debian wants to make its fonts unreadable because [...]
Nope. I understand that you got a big pile of frustration like hell,
but unfortunately what followed this sentence can't get anything
positive done. Debian clearly
Hi khelpcenter maintainers,
On Sat, 01 Jun 2019 21:30:41 +0200 pnd23 wrote:
> KDE packages install their documentation files in /usr/share/doc/HTML on
> buster
> (in debian 8 this was: /usr/share/doc/kde/HTML). The "dhelp" package erases
> this folder when it rebuilds its index. The KHelpcenter
Processing control commands:
> block 864320 by 816111 595696
Bug #864320 [base] multiple critical problems booting
864320 was blocked by: 595696 816111
864320 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #864320 to the same blocks
previously set
--
864320: https://b
Control: block 864320 by 816111 595696
Hello,
gofloss gofloss, le mar. 06 juin 2017 13:52:05 -0700, a ecrit:
> below i describe multiple bugs in booting in jessie, which
> might be relevant to stretch.
[...]
> rebooted, and discovered that the font was unreadably small,
> unlike wheezy.
>
> bu
Processing control commands:
> block 864320 by 816111 595696
Bug #864320 [base] multiple critical problems booting
864320 was not blocked by any bugs.
864320 was not blocking any bugs.
Added blocking bug(s) of 864320: 816111 and 595696
--
595696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug
Processing control commands:
> block 864320 by 816111 595696
Bug #864320 [base] multiple critical problems booting
864320 was blocked by: 595696 816111
864320 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #864320 to the same blocks
previously set
--
816111: https://b
hi Thomas,
On Fri, Jun 07, 2019 at 09:31:41AM +0200, Thomas Goirand wrote:
> Hi Salvatore and the rest of the security team,
>
> I have prepared the Stretch update for the new Stretch update:
> miniupnpd/1.8.20140523-4.1+deb9u2
>
> The debdiff is attached to this mail. The resulting package is a
Processing commands for cont...@bugs.debian.org:
> found 930321 2.0.15-1
Bug #930321 [src:php-horde-form] php-horde-form: CVE-2019-9858
Marked as found in versions php-horde-form/2.0.15-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
930321: https://bugs.debian
Processing commands for cont...@bugs.debian.org:
> tags 930332 ftbfs
Bug #930332 [coyim] FTBFS on arm64: FAIL: peer_test.go:79:
PeerSuite.Test_NameForPresentation_returnsTheNameIfItExistsButJidOtherwise
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistan
Hi Andreas,
On 10-06-2019 03:42, Andreas Henriksson wrote:
> On Sat, Jun 08, 2019 at 09:00:52PM +0200, Paul Gevers wrote:
>> While rebuilding all packages in buster for CVE-2018-17846 /
>> CVE-2018-17847 / CVE-2018-17848 in golang-golang-x-net-dev,
>> mender-client fails to build from source on al
Package: coyim
Version: 0.3.8+ds-6
Severity: grave
When binNMU coyim in sid, it FTBFS on arm64,
https://buildd.debian.org/status/fetch.php?pkg=coyim&arch=arm64&ver=0.3.8%2Bds-6%2Bb10&stamp=1552303594&raw=0
Log is
FAIL: peer_test.go:79:
PeerSuite.Test_NameForPresentation_returnsTheNameIfItExists
Package: debian-installer-9-netboot-amd64
Version: 20170615+deb9u6
Followup-For: Bug #917491
Dear Maintainer,
Some weeks ago, my Debian stretch netboot installer told me that
I needed to update, so I proceeded to download the new files:
http://ftp.debian.org/debian/dists/stretch/main/installer-a
Hi,
I discovered the need for the new udev rules via trying to use the
yubikey-personalization-gui. Someone had reported 842194 and as far as
I can tell its caused by the same permission denied problem this bug is
covering.
I suppose one could argue the gui should have reported the permission
den
Your message dated Mon, 10 Jun 2019 17:04:24 +
with message-id
and subject line Bug#928770: fixed in sqlite3 3.27.2-3
has caused the Debian Bug report #928770,
regarding sqlite3: CVE-2019-5018: Window Function Remote Code Execution
Vulnerability
to be marked as done.
This means that you clai
Processing commands for cont...@bugs.debian.org:
> block 842194 with 924787
Bug #842194 [yubikey-personalization-gui] [yubikey-personalization-gui]
'Unknown error occurred' reported - insufficient permissions
842194 was not blocked by any bugs.
842194 was not blocking any bugs.
Added blocking bug
Processing commands for cont...@bugs.debian.org:
> severity 928139 important
Bug #928139 [src:pgpool2] pgpool2: FTBFS twice in a row: ln: failed to create
symbolic link './watchdog_setup': File exists
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me
Hi there,
On Mon, 15 Apr 2019 at 23:24:19 +0200, Cyril Brulebois wrote:
>>> One could argue that cryptodisk support has never been supported by
>>> d-i anyway,
>>
>> Yup, and I suppose that's why I overlooked this in my mail to
>> debian-boot :-P Jonathan Carter had a similar report last week
>>
Processing commands for cont...@bugs.debian.org:
> affects 867020 auctex
Bug #867020 {Done: sa...@debian.org (Davide G. M. Salvetti)} [auctex] auctex:
fails to remove: auctex/remove: Removing parsed (La)TeX macros for
emacs25...rm: cannot remove '/var/lib/auctex/emacs25': Directory not empty
Add
Your message dated Mon, 10 Jun 2019 14:48:30 +
with message-id
and subject line Bug#929451: fixed in nageru 1.8.4-2
has caused the Debian Bug report #929451,
regarding spurious crashes with “vertex shader lacks main()” on i965
to be marked as done.
This means that you claim that the problem h
Hi,
> I'm rising the severity since this causes errors in dose-debcheck, which
> might affect QA or other infrastructure:
I removed the problematic package from experimental earlier; that should
make it a bit less urgent to upload a new version of firefox (it will
only miss firefox-l10n-bn).
Ans
Source: php-horde-form
Version: 2.0.18-3
Severity: grave
Tags: security upstream
Justification: user security hole
Hi,
The following vulnerability was published for php-horde-form.
CVE-2019-9858[0]:
| Remote code execution was discovered in Horde Groupware Webmail 5.2.22
| and 5.2.17. Horde/Form
On 10 June 2019 06:59:43 CEST, "Jürgen Göricke"
wrote:
>why don't you create binary packages of chromium and publish them in
>the unstable branch?
>Did I miss something important?
The packages are still being built, see
https://buildd.debian.org/status/package.php?p=chromium
Regards,
Steph
Hi,
Thank you for feedback.
On Sun, 9 Jun 2019 19:03:19 +0200 Salvatore Bonaccorso
wrote:
> Hi,
>
snip
> This should not close the bug yet as it only adresses CVE-2019-11502.
> #928052 both tracks CVE-2019-11502 CVE-2019-11503. So onless I miss
> smoething the changes to fix CVE-2019-11503 ar
Processing control commands:
> severity -1 serious
Bug #930256 [firefox-l10n-bn] Ignoring Provides line with non-equal
DepCompareOp for package firefox-l10n-bn-bd
Bug #930260 [firefox-l10n-bn] Ignoring Provides line with non-equal
DepCompareOp for package firefox-l10n-bn-bd
Bug #930299 [firefox-
Processing commands for cont...@bugs.debian.org:
> affects 930256 aptitude
Bug #930256 [firefox-l10n-bn] Ignoring Provides line with non-equal
DepCompareOp for package firefox-l10n-bn-bd
Bug #930260 [firefox-l10n-bn] Ignoring Provides line with non-equal
DepCompareOp for package firefox-l10n-bn-
Your message dated Mon, 10 Jun 2019 19:40:10 +0800
with message-id
and subject line Re: Bug#908055: docker.io: CVE-2017-14992
has caused the Debian Bug report #908055,
regarding docker.io: CVE-2017-14992
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
Control: forcemerge 865975 -1
I looked at the bug list of docker.io, found it's already reported at #865975
docker did this intentionally, and also metioned this behaviour in its
chanelog(in src engine/CHANGELOG.md, not in /usr/share/doc)
* Change the default `FORWARD` policy to `DROP`
[#28257](
Processing control commands:
> forcemerge 865975 -1
Bug #865975 [docker.io] docker.io breaks (bridged) network for VMs
Bug #865975 [docker.io] docker.io breaks (bridged) network for VMs
Marked as found in versions docker.io/18.03.1+dfsg1-5 and
docker.io/18.09.1+dfsg1-7.
Added tag(s) confirmed.
Bu
Processing commands for cont...@bugs.debian.org:
> reassign 929451 nageru
Bug #929451 [libgl1-mesa-dri] linking shaders twice fails, fixed by rebuilding
the package
Bug reassigned from package 'libgl1-mesa-dri' to 'nageru'.
No longer marked as found in versions mesa/18.3.4-2.
Ignoring request to
Processing commands for cont...@bugs.debian.org:
> clone 903635 -1
Bug #903635 [docker.io] docker.io: Modifies iptables despite --iptables=false
Bug 903635 cloned as bug 930302
> retitle -1 installing and starting docker changes iptables FORWARD policy,
> breaking unrelated things
Bug #930302 [do
clone 903635 -1
retitle -1 installing and starting docker changes iptables FORWARD policy,
breaking unrelated things
severity 903635 important
found 903635 18.09.1+dfsg1-7
found -1 18.09.1+dfsg1-7
thanks
On Mon, Jun 10, 2019 at 01:27:45AM +0800, Shengjing Zhu wrote:
Could you provide more info
On Sat, Jun 08, 2019 at 10:13:03PM -0400, Afif Elghraoui wrote:
I don't understand... I thought the whole point of making a bug
release-critical is to keep the bug out of the release (either by having
it fixed or removing the package).
No, that's not the point; it's the consequence. There are c
Hi Reinhard,
I don't blame you. I think that for Debian to upgrade a package, changing a
global setting, break some of its dependencies, and then kick out the
resulting broken packages a month later (nearly a year before the expected
release date) seems pretty harsh. In this case it took me 4.5 mo
Package: libghc-argon2-dev
Version: 1.3.0.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libghc-argon2-prof
Hi,
during a test with piuparts I noticed your package causes problems
during the upgrade from stretch to buster.
>From the attached log (s
Processing control commands:
> affects -1 + libghc-argon2-prof
Bug #930300 [libghc-argon2-dev] libghc-argon2-dev: switch dependency to
libargon2-dev
Added indication that 930300 affects libghc-argon2-prof
--
930300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930300
Debian Bug Tracking Sy
49 matches
Mail list logo
