Dear Technical Committee members,
(CC'ed to submitter, and debootstrap maintainers for information and feedack)
Here's the current state of the draft resolution; which `master` is at
https://salsa.debian.org/debian/tech-ctte/blob/master/914897_merged_usr/ballot.md
I will submit it to vote on Frid
Control: reassign -1 libqt5core5a/5.11.3+dfsg-2
Control: affects -1 plasma-desktop
Control: severity -1 important
Please, don't abuse the bugs severity just to get more attention.
El 2019-02-17 a las 10:06 +0100, Charlemagne Lasse escribió:
Package: plasma-desktop
Version: 4:5.14.5-1
Severity:
Processing control commands:
> reassign -1 libqt5core5a/5.11.3+dfsg-2
Unknown command or malformed arguments to command.
> affects -1 plasma-desktop
Bug #922502 [plasma-desktop] plasma-desktop: regional settings allow do select
system incompatible locales
Added indication that 922502 affects pla
> Control: reassign -1 libqt5core5a/5.11.3+dfsg-2
> Control: affects -1 plasma-desktop
>
> Control: severity -1 important
>
> Please, don't abuse the bugs severity just to get more attention.
I didn't abuse the severity. The
https://www.debian.org/Bugs/Developer#severities has an entry "makes
unr
Control: tag -1 pending
Hello,
Bug #922253 in hamradio-maintguide 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:
https://salsa.debian.org/debian-hamradio-team/hamradio-maintguide/commi
Processing control commands:
> tag -1 pending
Bug #922253 [src:hamradio-maintguide] hamradio-maintguide: FTBFS (Could not
import extension sphinx.ext.pngmath)
Added tag(s) pending.
--
922253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922253
Debian Bug Tracking System
Contact ow...@bugs.
Your message dated Mon, 18 Feb 2019 09:19:30 +
with message-id
and subject line Bug#921733: fixed in cyrus-imapd 3.0.8-2
has caused the Debian Bug report #921733,
regarding prevent migration while I am out of town
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 18 Feb 2019 09:34:13 +
with message-id
and subject line Bug#922253: fixed in hamradio-maintguide 0.5
has caused the Debian Bug report #922253,
regarding hamradio-maintguide: FTBFS (Could not import extension
sphinx.ext.pngmath)
to be marked as done.
This means that yo
On Thursday, 14 February 2019 4:03:35 AM AEDT Shengjing Zhu wrote:
> BTW, now the test migration is 10 days, and this package will be removed
> from testing in 6 days. Maybe the release-team should be contacted to
> keep this in buster?
I can not spare time for dumb-init right now but I trust you
On Saturday, 16 February 2019 5:57:51 AM AEDT Shengjing Zhu wrote:
> I've uploaded this NMU to DELAYED/2-day. Hope it works.
Awesome. Thank you very much.
--
Regards,
Dmitry Smirnov.
---
To predict the behavior of ordinary people in advance, you only have to
assume that they will always try t
Processing commands for cont...@bugs.debian.org:
> forcemerge 922478 922547
Bug #922478 [src:linux] upgrade linux-image-4.9.0-8-armmp-lpae:armhf from
4.9.130-2 to 4.9.144-3 renders many systems unbootable
Bug #922532 [src:linux] upgrade linux-image-4.9.0-8-armmp-lpae:armhf from
4.9.130-2 to 4.9.
Your message dated Mon, 18 Feb 2019 10:23:03 +
with message-id
and subject line Bug#873016: fixed in node-lodash 4.17.11+dfsg-2
has caused the Debian Bug report #873016,
regarding node-lodash-packages: not preferred form for source: Should be built
from node-lodash
to be marked as done.
This
On Sun, 17 Feb 2019 21:26:41 +0100 (CET) "Timo Sigurdsson"
wrote:
> Hi,
>
> Cyril Brulebois schrieb am 17.02.2019 19:38:
>
> > Hi folks,
> >
> > Jürgen Löb (2019-02-16):
> >> Package: linux-image-4.9.0-8-armmp-lpae
> >> Version: 4.9.144-3
> >> Severity: serious
> >>
> >> Updated my Lamobo R1
Processing control commands:
> merge -1 910237
Bug #922564 [src:mathicgb] FTBFS on ppc64el
Unable to merge bugs because:
forwarded of #910237 is 'https://github.com/Macaulay2/mathicgb/issues/12' not ''
severity of #910237 is 'serious' not 'important'
Failed to merge 922564: Did not alter merged bu
Processing commands for cont...@bugs.debian.org:
> forwarded 922564 https://github.com/Macaulay2/mathicgb/issues/12
Bug #922564 [src:mathicgb] FTBFS on ppc64el
Set Bug forwarded-to-address to
'https://github.com/Macaulay2/mathicgb/issues/12'.
> severity 922564 serious
Bug #922564 [src:mathicgb] F
Control: tags -1 + ftbfs
Hi Julien
I'm neither a user of mercurial nor hg-git.
On 2019/02/08 16:52, Julien Cristau wrote:
Guess there's two parts here, splitting them. hg-git has been in need
of upstream love for a while AFAICT...
Do you have any ideas on how to suppress the deprecation war
Processing control commands:
> tags -1 + ftbfs
Bug #921732 [hg-git] hg-git: incompatible with mercurial 4.9
Added tag(s) ftbfs.
--
921732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Mon, 18 Feb 2019 12:19:06 +
with message-id
and subject line Bug#921979: fixed in lmfit-py 0.9.11+dfsg-2
has caused the Debian Bug report #921979,
regarding lmfit-py: FTBFS randomly
(test_covariance_matrix.test_bounded_parameters fails)
to be marked as done.
This means tha
Hi,
I'm looking at this bug because it's menacing my package goiardi.
The removal count expires today; in the meanwhile goiardi 0.11.9 has
been uploaded a few days ago, and does no longer require -x-exp-dev to
build.
The other two source packages requiring -x-exp-dev to build are
kubernetes and
On Sun, Feb 17, 2019 at 04:54:00PM -0800, Vagrant Cascadian wrote:
>On 2019-02-17, Vagrant Cascadian wrote:
>> On 2019-02-17, Timo Sigurdsson wrote:
>>> Cyril Brulebois schrieb am 17.02.2019 19:38:
Jürgen Löb (2019-02-16):
>> FWIW, I also built a local package from 4.9.155-1~ from salsa/stre
On Mon, Feb 18, 2019 at 11:28:10AM +, Neil Williams wrote:
>On Sun, 17 Feb 2019 21:26:41 +0100 (CET) "Timo Sigurdsson"
>>
>> So, I also tested 4.9.135-1 on a Bananapi board and can confirm it
>> works.
>>
>> I would suspect the issue is caused by Debian's kernel configuration
>> or changes. T
Hi all.
I'd like to add that 4.9.0-8-686 Version is broken too.
At least for my ALIX-Board ALIX.2D2 from PC Engines.
(CPU: 500 MHz AMD Geode LX800)
W.O.
Your message dated Mon, 18 Feb 2019 12:49:18 +
with message-id
and subject line Bug#888556: fixed in etsf-io 1.0.4-4
has caused the Debian Bug report #888556,
regarding libetsf-io-doc: fails to upgrade from 'testing' - trying to overwrite
/usr/share/doc/libetsf-io-dev/AUTHORS
to be marked as
Hi,
On Mon, 18 Feb 2019 11:28:10 +, Neil Williams wrote:
> Is it feasible to have a script in devscripts or similar which maps the
> version of the kernel *Candidate* to KernelCI URLs for the same
> version?
>
> Can we correlate Debian kernel versions to something like
> https://kernelci.org
Your message dated Mon, 18 Feb 2019 13:19:09 +
with message-id
and subject line Bug#922552: fixed in diffutils 1:3.7-2
has caused the Debian Bug report #922552,
regarding diffutils: FTBFS in ppc64el (failing tests)
to be marked as done.
This means that you claim that the problem has been deal
Processing commands for cont...@bugs.debian.org:
> severity 918578 serious
Bug #918578 [gosa] gosa: GOsa web interface missing password field
Severity set to 'serious' from 'important'
> # After upgrading a Debian Edu main server (Stretch 9.8 -> Buster) the
> # password entry field is missing just
Processing commands for cont...@bugs.debian.org:
> notfound 922478 4.9.130-2
Bug #922478 [src:linux] upgrade linux-image-4.9.0-8-armmp-lpae:armhf from
4.9.130-2 to 4.9.144-3 renders many systems unbootable
Bug #922532 [src:linux] upgrade linux-image-4.9.0-8-armmp-lpae:armhf from
4.9.130-2 to 4.9
Your message dated Mon, 18 Feb 2019 19:02:15 +0530
with message-id
and subject line ruby-capybara is in testing now
has caused the Debian Bug report #921320,
regarding ruby-rspec-rails build depends on ruby-capybara (>= 2.15~) that is
currently not in buster
to be marked as done.
This means that
Processing commands for cont...@bugs.debian.org:
> severity 917807 grave
Bug #917807 [src:libcaca] libcaca: CVE-2018-20544 CVE-2018-20545 CVE-2018-20546
CVE-2018-20547 CVE-2018-20548 CVE-2018-20549
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if y
Your message dated Mon, 18 Feb 2019 13:37:36 +
with message-id
and subject line Bug#919805: fixed in redmine 4.0.1-1
has caused the Debian Bug report #919805,
regarding redmine: FTBFS (Could not find gem mail)
to be marked as done.
This means that you claim that the problem has been dealt wit
On Thu, 14 Feb 2019 09:41:13 +0100 Paul Gevers wrote:
> While investigating ways to fix bug #896468 (new version for
> libjs-chartjs), I discovered that ruby-rails-assets-chartjs doesn't
> contain the source of Chart.js and for sure doesn't build Chart.js from
> the upstream source.
>
> Ironicall
Your message dated Mon, 18 Feb 2019 15:17:59 +0100
with message-id <1dea5cef-0a73-796d-e55c-c2fc95311...@gmx.de>
and subject line Milib fixes "~" dependency oversight
has caused the Debian Bug report #920838,
regarding libredberry-pipe-java: pom generates unfulfillable dependency
to be marked as do
Your message dated Mon, 18 Feb 2019 14:50:31 +
with message-id
and subject line Bug#895115: fixed in beep 1.4.3-1
has caused the Debian Bug report #895115,
regarding info leakage and unauthorized access to devices
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Mon, 18 Feb 2019 14:50:31 +
with message-id
and subject line Bug#902722: fixed in beep 1.4.3-1
has caused the Debian Bug report #902722,
regarding CVE-2018-1000532
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case
Hi!
El lun., 18 feb. 2019 05:48, Charlemagne Lasse
escribió:
> > Control: reassign -1 libqt5core5a/5.11.3+dfsg-2
> > Control: affects -1 plasma-desktop
> >
> > Control: severity -1 important
> >
> > Please, don't abuse the bugs severity just to get more attention.
>
> I didn't abuse the severit
Hello,
Just wondering why this test seem to have passed in 0.10.6-3 (sid) and
not any more ?
As this test is failing on most arch, shouldn't we disable it ?
Thanks
On Sat, 29 Jul 2017 12:43:02 +0300 Adrian Bunk wrote:
> Source: qtile
> Version: 0.10.7-2
> Severity: serious
>
> https://buildd.de
Package: grfcodec
Version: 6.0.6-2
Severity: serious
Justification: policy 4.6
Tags: upstream
grfcodec can make the build loop indefinitely. The attached bad.patch
demonstrates the behaviour. The problem seems to be
https://sources.debian.org/src/grfcodec/6.0.6-2/Makefile/#L216:
| $(_C)objs
Your message dated Mon, 18 Feb 2019 15:21:16 +
with message-id
and subject line Bug#918764: fixed in systemd 240-6
has caused the Debian Bug report #918764,
regarding udev: "udevadm control --reload-rules" kills all processes except init
to be marked as done.
This means that you claim that th
Processing commands for cont...@bugs.debian.org:
> fixed #917408 5.7.4-1
Bug #917408 [src:jupyter-notebook] jupyter-notebook: CVE-2018-19352
Marked as fixed in versions jupyter-notebook/5.7.4-1.
> fixed #917409 5.7.4-1
Bug #917409 [src:jupyter-notebook] jupyter-notebook: CVE-2018-19351
Marked as f
Control: tag -1 patch
Adrian Bunk (2019-02-17):
> On Sun, Feb 17, 2019 at 09:52:48AM -0800, Vagrant Cascadian wrote:
> > After upgrading to the latest 4.9.x kernel in sid, all of the armhf
> > boards running this kernel failed to boot.
> >
> > Adding to the list:
> >
> > imx6: Cubox-i4pro, Cubo
Processing control commands:
> tag -1 patch
Bug #922478 [src:linux] upgrade linux-image-4.9.0-8-armmp-lpae:armhf from
4.9.130-2 to 4.9.144-3 renders many systems unbootable
Bug #922532 [src:linux] upgrade linux-image-4.9.0-8-armmp-lpae:armhf from
4.9.130-2 to 4.9.144-3 renders many systems unboo
Processing commands for cont...@bugs.debian.org:
> forcemerge 910056 920458
Bug #910056 {Done: Mattia Rizzolo } [src:twisted] twisted:
Missing version constraint on python-attr dependencies
Unable to merge bugs because:
package of #920458 is 'python3-twisted' not 'src:twisted'
Failed to forcibly
On Mon, Feb 18, 2019 at 05:09:12PM +0100, Cyril Brulebois wrote:
>Control: tag -1 patch
>
>Adrian Bunk (2019-02-17):
>> On Sun, Feb 17, 2019 at 09:52:48AM -0800, Vagrant Cascadian wrote:
>> > After upgrading to the latest 4.9.x kernel in sid, all of the armhf
>> > boards running this kernel failed
Hi all,
Same issue here with 4.9.144-3 on my Olimex OLinuXino-LIME2 board
(Allwinner A20 cpu) :
u-boot is struck at "Starting kernel", nothing happens after that.
This board boots ok with 4.9.130-2 and also with 4.9.135-1 (found at
snapshot.debian.org).
I'm using the armmp kernel variant
On Mon, 18 Feb 2019 17:09:12 +0100
Cyril Brulebois wrote:
> Control: tag -1 patch
>
> Adrian Bunk (2019-02-17):
> > On Sun, Feb 17, 2019 at 09:52:48AM -0800, Vagrant Cascadian wrote:
> > > After upgrading to the latest 4.9.x kernel in sid, all of the
> > > armhf boards running this kernel fai
Your message dated Mon, 18 Feb 2019 16:35:05 +
with message-id
and subject line Bug#921754: fixed in gfsview 20121130+dfsg-6
has caused the Debian Bug report #921754,
regarding gfsview: FTBFS (error adding symbols)
to be marked as done.
This means that you claim that the problem has been deal
Hi.
On Mon, Feb 18, 2019 at 05:09:12PM +0100, Cyril Brulebois wrote:
> Checking this on real hardware would be great, trying to put everyone
> involved in the loop through cc.
Confirming that the patched kernel booted successfully on
Armada385/Caiman.
Reco
On Mon, Feb 18, 2019 at 05:09:12PM +0100, Cyril Brulebois wrote:
I've uploaded linux-image binaries (armmp and armmp-lpae) here, which
were cross-built through sbuild, thanks to Vagrant's suggestion on IRC:
https://people.debian.org/~kibi/linux-bug-922478/
[...]
Checking this on real hard
On Mon, 18 Feb 2019 17:45:25 +0100
jean.ta...@free.fr wrote:
> On Mon, Feb 18, 2019 at 05:09:12PM +0100, Cyril Brulebois wrote:
>
> > I've uploaded linux-image binaries (armmp and armmp-lpae) here,
> > which were cross-built through sbuild, thanks to Vagrant's
> > suggestion on IRC:
> > https://p
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package ruby-ronn
> # 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
Setti
Processing commands for cont...@bugs.debian.org:
> forwarded 918611 https://github.com/ichord/jquery-atwho-rails/issues/29
Bug #918611 [src:ruby-jquery-atwho-rails] ruby-jquery-atwho-rails FTBFS with
rails 5.2
Set Bug forwarded-to-address to
'https://github.com/ichord/jquery-atwho-rails/issues/2
Hi,
Not sure why grave so late in the release process that we lose
some packages (csync2 in my case)? grave after the release would
give us more time to move to librsync2.
--
Valentin
Hi Cyril,
Cyril Brulebois schrieb am 18.02.2019 17:09:
> Based on this suggestion and Julien's suggested patch on IRC a couple
> hours ago, I've tested the attached patch successfully (as in: from a
> busy loop in qemu-system-arm to the “expected” kernel panic, as
> discussed in another subthread
Your message dated Mon, 18 Feb 2019 18:06:14 +
with message-id
and subject line Bug#919798: fixed in maven-javadoc-plugin 3.0.1-3
has caused the Debian Bug report #919798,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be m
Your message dated Mon, 18 Feb 2019 18:06:14 +
with message-id
and subject line Bug#919798: fixed in maven-javadoc-plugin 3.0.1-3
has caused the Debian Bug report #919798,
regarding dirgra FTBFS with recent OpenJDK
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Mon, 18 Feb 2019 18:06:14 +
with message-id
and subject line Bug#919798: fixed in maven-javadoc-plugin 3.0.1-3
has caused the Debian Bug report #919798,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be m
Your message dated Mon, 18 Feb 2019 18:06:14 +
with message-id
and subject line Bug#919798: fixed in maven-javadoc-plugin 3.0.1-3
has caused the Debian Bug report #919798,
regarding localizer FTBFS with recent OpenJDK
to be marked as done.
This means that you claim that the problem has been d
Your message dated Mon, 18 Feb 2019 18:06:14 +
with message-id
and subject line Bug#919798: fixed in maven-javadoc-plugin 3.0.1-3
has caused the Debian Bug report #919798,
regarding javamail: FTBFS on Buster/Sid
to be marked as done.
This means that you claim that the problem has been dealt w
Your message dated Mon, 18 Feb 2019 18:06:14 +
with message-id
and subject line Bug#919798: fixed in maven-javadoc-plugin 3.0.1-3
has caused the Debian Bug report #919798,
regarding jnr-posix FTBFS with recent OpenJDK
to be marked as done.
This means that you claim that the problem has been d
Your message dated Mon, 18 Feb 2019 18:06:14 +
with message-id
and subject line Bug#919798: fixed in maven-javadoc-plugin 3.0.1-3
has caused the Debian Bug report #919798,
regarding libparanamer-java FTBFS with recent OpenJDK
to be marked as done.
This means that you claim that the problem ha
Your message dated Mon, 18 Feb 2019 18:06:14 +
with message-id
and subject line Bug#919798: fixed in maven-javadoc-plugin 3.0.1-3
has caused the Debian Bug report #919798,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be m
Your message dated Mon, 18 Feb 2019 18:06:14 +
with message-id
and subject line Bug#919798: fixed in maven-javadoc-plugin 3.0.1-3
has caused the Debian Bug report #919798,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be m
Your message dated Mon, 18 Feb 2019 18:06:14 +
with message-id
and subject line Bug#919798: fixed in maven-javadoc-plugin 3.0.1-3
has caused the Debian Bug report #919798,
regarding javadoc: The code being documented uses modules but the packages
defined in … are in the unnamed module
to be m
Your message dated Mon, 18 Feb 2019 18:06:14 +
with message-id
and subject line Bug#919798: fixed in maven-javadoc-plugin 3.0.1-3
has caused the Debian Bug report #919798,
regarding weupnp FTBFS with recent OpenJDK
to be marked as done.
This means that you claim that the problem has been deal
Processing control commands:
> tag -1 - sid experimental
Bug #921704 [src:tortoisehg] tortoisehg: uninstallable with mercurial 4.9
Removed tag(s) sid and experimental.
--
921704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921704
Debian Bug Tracking System
Contact ow...@bugs.debian.org wit
Control: tag -1 - sid experimental
On Sun, Feb 17, 2019 at 21:57:32 -0800, Ludovico Cavedon wrote:
> package src:tortoisehg
> tags 921704 + sid experimental
> thanks
>
> Thank you for the bug report. TortoiseHg 4.9 has not been released yet.
>
There's no need for the tags, and this will affect
On Mon, Feb 18, 2019 at 10:58 AM Julien Cristau wrote:
> > Thank you for the bug report. TortoiseHg 4.9 has not been released yet.
> >
> There's no need for the tags, and this will affect buster when mercurial
> migrates so they're wrong anyway.
>
I see.
Would it make sense to delay the migratio
Processing control commands:
> severity -1 serious
Bug #918632 [src:simplejson, src:json-schema-validator] simplejson breaks
json-schema-validator autopkgtest
Severity set to 'serious' from 'normal'
--
918632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918632
Debian Bug Tracking System
C
Processing control commands:
> severity -1 serious
Bug #919928 [src:htslib, src:python-pysam] htslib breaks python-pysam
autopkgtest
Severity set to 'serious' from 'normal'
--
919928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919928
Debian Bug Tracking System
Contact ow...@bugs.debian.o
On Mon, Feb 18, 2019 at 11:07:59 -0800, Ludovico Cavedon wrote:
> On Mon, Feb 18, 2019 at 10:58 AM Julien Cristau wrote:
>
> > > Thank you for the bug report. TortoiseHg 4.9 has not been released yet.
> > >
> > There's no need for the tags, and this will affect buster when mercurial
> > migrates
On Mon, Feb 18, 2019 at 11:39 AM Julien Cristau wrote:
> Well it's going to be delayed by virtue of making tortoisehg and hg-git
> uninstallable anyway, for now. Is there an ETA on a tortoise 4.9
> release?
>
>
Let me check with upstream.
Thanks,
Ludovico
Quoting Faustin Lammler (2019-01-17 22:17:07)
> Control: forwarded -1 https://redmine.kannel.org/issues/795
>
> Hi,
> This seems to be a bug (see
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919395#36):
>
> > error: 'MYSQL_SERVER_VERSION' undeclared
> >
> > this looks like a bug. MYSQL_SE
Your message dated Mon, 18 Feb 2019 20:44:08 +
with message-id
and subject line Bug#921798: fixed in node-mocha 4.1.0+ds3-4
has caused the Debian Bug report #921798,
regarding node-mocha: FTBFS (Module not found: Error: Recursion in resolving)
to be marked as done.
This means that you claim t
Processing commands for cont...@bugs.debian.org:
> unarchive 895778
Bug #895778 {Done: Markus Koschany } [jruby] jruby: Several
security vulnerabilities
Unarchived Bug 895778
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
895778: https://bugs.debian.org/cgi-bin/
Your message dated Mon, 18 Feb 2019 21:50:39 +
with message-id
and subject line Bug#896625: fixed in pyevolve 0.6+git20151103.589b6a9-1
has caused the Debian Bug report #896625,
regarding FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'
to be marked as done.
This means that
Processing commands for cont...@bugs.debian.org:
> affects 895778 9.1.13.0-1
Bug #895778 {Done: Markus Koschany } [jruby] jruby: Several
security vulnerabilities
Added indication that 895778 affects 9.1.13.0-1
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
89577
Processing commands for cont...@bugs.debian.org:
> affects 895778 9.1.13.0-1^
Bug #895778 {Done: Markus Koschany } [jruby] jruby: Several
security vulnerabilities
Added indication that 895778 affects 9.1.13.0-1^
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
895
On Mon, Jun 04, 2018 at 11:47:35PM +0200, Andreas Beckmann wrote:
> Source: nvidia-graphics-drivers-legacy-304xx
> Version: 304.137-5
> Severity: serious
> Tags: sid buster upstream wontfix
>
> The 304.xx legacy series is EoL upstream and won't be updated for the
> latest Xorg.
>
> Let's get it o
On Mon, Nov 12, 2018 at 02:36:23PM +, Luca Boccassi wrote:
> On Mon, 2018-11-12 at 13:47 +0100, Andreas Beckmann wrote:
> > On 2018-11-11 13:54, Luca Boccassi wrote:
> > > https://nvidia.custhelp.com/app/answers/detail/a_id/4738
> >
> > So we expect new releases soon. There is already 415.* ..
Processing commands for cont...@bugs.debian.org:
> forcemerge 910056 920458
Bug #910056 {Done: Mattia Rizzolo } [src:twisted] twisted:
Missing version constraint on python-attr dependencies
Unable to merge bugs because:
package of #920458 is 'python3-twisted' not 'src:twisted'
Failed to forcibly
On Mon, 18 Feb 2019 20:05:41 +0100 Paul Gevers
wrote:
> Control: severity -1 serious
>
> Hi,
>
> On Mon, 7 Jan 2019 21:49:01 +0100 Paul Gevers
> wrote:
> > With a recent upload of simplejson the autopkgtest of
> > json-schema-validator fails in testing when that autopkgtest is run
> > with the
On Sun, Feb 17, 2019 at 04:41:57PM +0100, Wolfgang Schweer wrote:
> On Mon, Jan 14, 2019 at 03:43:26PM +, Holger Levsen wrote:
> > On Mon, Jan 14, 2019 at 05:15:59PM +0200, Eliza Ralph wrote:
> > > So are you saying it's not possible to fix GOsa in this case?
> >
> > it's not gosa that is brok
On Mon, 2019-02-18 at 22:57 +0100, Moritz Mühlenhoff wrote:
> On Mon, Nov 12, 2018 at 02:36:23PM +, Luca Boccassi wrote:
> > On Mon, 2018-11-12 at 13:47 +0100, Andreas Beckmann wrote:
> > > On 2018-11-11 13:54, Luca Boccassi wrote:
> > > > https://nvidia.custhelp.com/app/answers/detail/a_id/473
Your message dated Mon, 18 Feb 2019 23:18:42 +
with message-id
and subject line Bug#921725: fixed in libu2f-host 1.1.2-2+deb9u1
has caused the Debian Bug report #921725,
regarding libu2f-host: CVE-2018-20340
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Mon, 18 Feb 2019 23:18:41 +
with message-id
and subject line Bug#906855: fixed in gnome-chemistry-utils 0.14.15-1+deb9u1
has caused the Debian Bug report #906855,
regarding gcu-plugin: NPAPI plugins are no longer supported by firefox-esr
to be marked as done.
This means tha
Your message dated Mon, 18 Feb 2019 23:18:30 +
with message-id
and subject line Bug#922059: fixed in flatpak 0.8.9-0+deb9u2
has caused the Debian Bug report #922059,
regarding flatpak: CVE-2019-8308: vulnerability similar to runc CVE-2019-5736
involving /proc/self/exe
to be marked as done.
T
Your message dated Mon, 18 Feb 2019 23:18:42 +
with message-id
and subject line Bug#921725: fixed in libu2f-host 1.1.2-2+deb9u1
has caused the Debian Bug report #921725,
regarding libu2f-host: CVE-2018-20340
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Mon, 18 Feb 2019 23:18:59 +
with message-id
and subject line Bug#922071: fixed in mosquitto 1.4.10-3+deb9u4
has caused the Debian Bug report #922071,
regarding mosquitto dumps core on startup on armv7l
to be marked as done.
This means that you claim that the problem has bee
Control: fixed 911873 python-pygraphviz/1.5-1
Hi,
I cannot reproduce this bug by building python-transitions in a fresh
buster pbuilder environment. I've updated upstream's CI setup to run on
Python 3.7, and all tests pass there as well.
Looking closer at the stack trace and the source code, it
Processing control commands:
> fixed 911873 python-pygraphviz/1.5-1
Bug #911873 {Done: Stein Magnus Jodal }
[src:python-transitions] python-transitions FTBFS: tests fail with Python 3.7:
RuntimeError: generator raised StopIteration
Marked as fixed in versions python-pygraphviz/1.5-1.
--
911873
Your message dated Tue, 19 Feb 2019 00:38:57 +0100
with message-id <20190218233857.GA29367@buildup>
and subject line Re: python-transitions FTBFS: tests fail with Python 3.7:
RuntimeError: generator raised StopIteration
has caused the Debian Bug report #911873,
regarding python-transitions FTBFS:
Hi,
Didier 'OdyX' Raboud (2019-02-18):
> Dear Technical Committee members,
> (CC'ed to submitter, and debootstrap maintainers for information and feedack)
>
> Here's the current state of the draft resolution; which `master` is at
> https://salsa.debian.org/debian/tech-ctte/blob/master/914897_mer
Hi Didier,
While I'm not necessarily disagreeing with the overall point(s) here,
some of the points in this list of arguments seem dubious at
best. Maybe you could expand?
>* having separate `/` and `/usr` filesystems has been useful in the past for
> booting without initramfs onto a minimal roo
On Feb 18, Didier 'OdyX' Raboud wrote:
> * another use-case is to be able to share an identical `/usr` over a network
> link; hence booting an initramfs, mounting a local `/`, then mounting `/usr`
> over the network. It seems that an initramfs with everything needed to mount
> a filesystem
On Sun, Feb 10, 2019 at 09:25:30PM +0100, Johan Grip wrote:
> Hi.
>
> Looked at it a bit more and found the following things.
>
> ApacheDS have moved it's configuration to a dynamic schema based setup, like
> OpenLDAP.
> As part of the startup it tries to migrate the config.ldif to a folder based
Your message dated Tue, 19 Feb 2019 02:40:41 +
with message-id
and subject line Bug#915987: fixed in partimage 0.6.9-7
has caused the Debian Bug report #915987,
regarding partimage FTBFS with glibc 2.28
to be marked as done.
This means that you claim that the problem has been dealt with.
If t
Your message dated Mon, 18 Feb 2019 22:09:36 -0500
with message-id
and subject line Re: Bug#921521: chromium-browser: CVE/Security fixes missing
in stable-sec
has caused the Debian Bug report #921521,
regarding chromium-browser: CVE/Security fixes missing in stable-sec
to be marked as done.
Thi
Processing commands for cont...@bugs.debian.org:
> severity 922500 minor
Bug #922500 [tex-common] tex-common: Fails to install with LC_TIME=en_DE.UTF-8
Severity set to 'minor' from 'serious'
> retitle 922500 make luatex work under broken locales
Bug #922500 [tex-common] tex-common: Fails to instal
Processing commands for cont...@bugs.debian.org:
> retitle 920476 mumble: CVE-2019-129: DoS due to changing # of allowed
> users in root channel
Bug #920476 {Done: Christopher Knadle } [mumble]
security issue: DoS due to changing # of allowed users in root channel
Changed Bug title to 'mumbl
Package: beep
Version: 1.4.3-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
After today's upgrade to version 1.4.x, beep no longer works and pops the above
error. After checking its man page, I found out that it tries to access these
devices, in that spe
1 - 100 of 106 matches
Mail list logo
