Your message dated Sat, 28 Sep 2019 05:21:52 +
with message-id
and subject line Bug#941288: Removed package(s) from unstable
has caused the Debian Bug report #935343,
regarding eficas: Qt4 removal from Bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 28 Sep 2019 05:21:22 +
with message-id
and subject line Bug#941285: Removed package(s) from unstable
has caused the Debian Bug report #875150,
regarding [qtiplot] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 28 Sep 2019 05:20:47 +
with message-id
and subject line Bug#941286: Removed package(s) from unstable
has caused the Debian Bug report #875158,
regarding [qtexengine] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 28 Sep 2019 05:20:15 +
with message-id
and subject line Bug#940890: Removed package(s) from unstable
has caused the Debian Bug report #918396,
regarding golang-github-glendc-gopher-json FTBFS with Go 1.11
to be marked as done.
This means that you claim that the
Processing control commands:
> severity -1 serious
Bug #930890 [src:ghdl] Update GHDL packaging for newer releases
Severity set to 'serious' from 'wishlist'
> found -1 0.35+git20181129+dfsg-3
Bug #930890 [src:ghdl] Update GHDL packaging for newer releases
Marked as found in versions
Your message dated Sat, 28 Sep 2019 01:49:32 +
with message-id
and subject line Bug#941204: fixed in sdrangelove 0.0.1.20150707-3
has caused the Debian Bug report #941204,
regarding sdrangelove FTBFS in unstable with new gnuradio: gmpxx.h: No such
file or directory
to be marked as done.
Control: severity -1 normal
Control: tags -1 + unreproducible
On 2019-07-24 01:49, Alex Volkov wrote:
Package: libkscreenlocker5
Version: 5.14.5-1
Severity: grave
Doesn't lock automatically by timeout, which presents a security issue.
Seems
to work in a newly created test user setup, and
Your message dated Fri, 27 Sep 2019 23:36:48 +
with message-id
and subject line Bug#941273: fixed in runit 2.1.2-35
has caused the Debian Bug report #941273,
regarding runit: FTBFS (looks like endless loop)
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing control commands:
> severity -1 normal
Bug #932872 [libkscreenlocker5] [libkscreenlocker5] Doesn't lock automatically
by timeout
Severity set to 'normal' from 'grave'
> tags -1 + unreproducible
Bug #932872 [libkscreenlocker5] [libkscreenlocker5] Doesn't lock automatically
by timeout
Processing control commands:
> tag -1 pending
Bug #941273 [src:runit] runit: FTBFS (looks like endless loop)
Added tag(s) pending.
--
941273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #941273 in runit 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: owncloud-client
Version: 2.5.1.10973+dfsg-1
Followup-For: Bug #933290
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan ubuntu-patch
This is fixed by simply replacing texlive-generic-extra with
texlive-plain-extra in the build-dependencies. Please find a patch
attached.
On Tue, Sep 17, 2019 at 11:25:56PM +0200, Moritz Mühlenhoff wrote:
> On Wed, Aug 21, 2019 at 11:00:10PM +0300, Dmitry Shachnev wrote:
> > Source: eficas
> > Version: 6.4.0-1-2
> > Severity: important
> > User: debian-qt-...@lists.debian.org
> > Usertags: qt4-removal
> >
> > Hi!
> >
> > As you
Your message dated Fri, 27 Sep 2019 21:36:16 +
with message-id
and subject line Bug#935764: fixed in freeipmi 1.6.4-2
has caused the Debian Bug report #935764,
regarding freeipmi: --link-doc between architecture all and not all packages
breaks binNMUs
to be marked as done.
This means that
Hi,
thanks for investigating, a fix for it is already in git, just failed to
build due to other issues.
Bernd
On 9/27/19 3:23 PM, Fabio Fantoni wrote:
> |change freeipmi-common (= ${source:Version}) to ||freeipmi-common (=
> ${binary:Version}) can solve the issue or can be other "unexpected"
>
On Wed, Sep 25, 2019 at 07:57:47AM +0200, Andreas Tille wrote:
> Hi,
>
> On Tue, Sep 24, 2019 at 10:48:24PM +0200, Moritz Mühlenhoff wrote:
> > On Tue, Sep 17, 2019 at 12:05:17PM -0300, Lisandro Damián Nicanor Pérez
> > Meyer wrote:
> > > Hi! It seems there is no activity on this bug, should we
Processing commands for cont...@bugs.debian.org:
> retitle 940679 cython3: generated code does out of bounds reads in with-dict
> (subclass of) cdef class
Bug #940679 [cython3] pandas: random test crashes
Changed Bug title to 'cython3: generated code does out of bounds reads in
with-dict
Processing control commands:
> reassign -1 cython3
Bug #940679 [src:pandas] pandas: random test crashes
Bug reassigned from package 'src:pandas' to 'cython3'.
No longer marked as found in versions pandas/0.23.3+dfsg-6.
Ignoring request to alter fixed versions of bug #940679 to the same values
Control: reassign -1 cython3
Control: affects -1 python3-pandas python3-skimage
Control: tags -1 fixed-upstream
Control: retitle -1: cython3: generated code does out of bounds reads in
with-dict (subclass of) cdef class
No, it is a proper Timedelta-sized space (144 bytes, not a _Timedelta's
Hi,
On Thu, Sep 26, 2019 at 04:32:58PM -0400, Boyuan Yang wrote:
> X-Debbugs-CC: debian-secur...@lists.debian.org
Adding now explicity the team alias.
> 在 2019-09-23一的 17:52 +0200，Gunnar Hjalmarsson写道：
> > It may be worth mentioning that Ubuntu's security team has disabled
> >
Your message dated Fri, 27 Sep 2019 15:20:22 +
with message-id
and subject line Bug#939492: fixed in nbsphinx 0.4.2+ds-3
has caused the Debian Bug report #939492,
regarding nbsphinx: testsuite failures with new pandoc
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 27 Sep 2019 16:20:09 +0100
with message-id <20190927152009.ga19...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#941076: libgcr-base-3-1: pinentry-gnome3 causes
gnome-shell crash if used with GLib >= 2.59
has caused the Debian Bug report #941076,
regarding
On Fri, Sep 27, 2019 at 15:49, Simon McVittie wrote:
Control: tags -1 = bullseye sid
Control: retitle -1 libgcr-base-3-1: pinentry-gnome3 causes
gnome-shell crash if used with GLib >= 2.59
Control: reassign -1 libgcr-base-3-1 3.28.0-1
Control: affects -1 + gnome-shell pinentry-gnome3
Julien,
On Fri, Sep 27, 2019 at 03:39:43PM +0200, Julien Cristau wrote:
> So one thing I think we should ensure is we don't end up uninstalling
> systemd without an explicit user choice.
>
> The "init" package has the "Important: yes" control field which as I
> understand it tells apt to behave
Processing control commands:
> tags -1 = bullseye sid
Bug #941076 [gnome-session,pinentry-gnome3] [GNOME 3.34] debsign crashes gnome
on wayland session
Added tag(s) sid and bullseye; removed tag(s) moreinfo and experimental.
> retitle -1 libgcr-base-3-1: pinentry-gnome3 causes gnome-shell crash
Control: tags -1 = bullseye sid
Control: retitle -1 libgcr-base-3-1: pinentry-gnome3 causes gnome-shell crash
if used with GLib >= 2.59
Control: reassign -1 libgcr-base-3-1 3.28.0-1
Control: affects -1 + gnome-shell pinentry-gnome3
Control: fixed -1 3.28.0-4
On Wed, 25 Sep 2019 at 16:59:01
On Fri, Sep 27, 2019 at 03:39:43PM +0200, Julien Cristau wrote:
> So one thing I think we should ensure is we don't end up uninstalling
> systemd without an explicit user choice.
>
> The "init" package has the "Important: yes" control field which as I
> understand it tells apt to behave like
On Wed, 25 Sep, 2019 at 13:33, Simon McVittie wrote:
On Wed, 25 Sep 2019 at 17:23:30 +0530, Pirate Praveen wrote:
On Wed, 25 Sep, 2019 at 16:59, Pirate Praveen
wrote:
> Let me try downgrading libgcr-base-3-1 and reproduce the crash.
Do I need to install some -dbgsym packages?
On Fri, Sep 27, 2019 at 09:19:10AM -0400, Sam Hartman wrote:
> I think it is fair to ask Julien as the bug submitter to engage here
> either by coming up with new options that none of us have explored or by
> coming up with specific problems. Alternatively it would be reasonable
> for him to ask
Sam,
On Fri, Sep 27, 2019 at 09:19:10AM -0400, Sam Hartman wrote:
> > "Mark" == Mark Hindley writes:
>
> Mark> Sam, Since I cannot get a working and robust dpkg-divert
> Mark> solution, I feel the need to revisit the validity of these
> Mark> concerns.
>
> I'd like to push back
Hello Sam,
> What i'm hearing is that after spending a couple of weeks exploring ways
> to meet these concerns, you'd now like to push back on whether they are
> a good idea in the first place.
> That seems dismissive both of Julien's concerns and the engineering
this is a completely wrong
> "Mark" == Mark Hindley writes:
Mark> Sam, Since I cannot get a working and robust dpkg-divert
Mark> solution, I feel the need to revisit the validity of these
Mark> concerns.
I'd like to push back on the phrasing here.
What i'm hearing is that after spending a couple of weeks
Package: src:runit
Version: 2.1.2-34
Severity: serious
I noticed that the last runit build is already taking over 13h on
buildds. The hppa build log[1] looks like the build failed due to an
endless loop.
I asked the other builds to be killed.
Ansgar
[1]
Hi, I trying to solve it and do a MR in salsa but I not found a better
way that revert this for now:
https://salsa.debian.org/debian/freeipmi/commit/af06af712350aabb28df359b4e9f0a1a0bfe978d
Someone know a better way please?
Anyway the upload of 1.6.4-1.1 seems don't have the serious issue of
*+b1
Package: ukwm
Version: 1.1.11-1+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
ukwm can't start,crash.The dmesg has the following error info:
[ 306.124994] ukwm[1159]: segfault at 38 ip b5b57084 sp bf9b2d0c error 4 in
libukwm-cogl-1.so[b5b19000+68000]
[
Could you please clarify: did you experience any data loss, or were you simply
unable to import your pool at one point?
As a second note, you should have done something like
zpool import -d /dev/disks/by-id -a
so that your import is done by labels that are stable across boots (names like
Processing commands for cont...@bugs.debian.org:
> reassign 941264 php-cache-lite 1.8.2-1
Bug #941264 [src:phpunit, src:php-cache-lite] phpunit breaks php-cache-lite
autopkgtest: tries to write to /usr/bin/.phpunit.result.cache
Bug reassigned from package 'src:phpunit, src:php-cache-lite' to
Control: reassign 941264 php-cache-lite/1.8.2-1
Hi,
Normally I check the bts for bugs, but it slipped. There is bug #940275
already.
Paul
signature.asc
Description: OpenPGP digital signature
Source: phpunit, php-cache-lite
Control: found -1 phpunit/8.3.5-1
Control: found -1 php-cache-lite/1.8.2-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainers,
With a recent upload of
Processing control commands:
> found -1 phpunit/8.3.5-1
Bug #941264 [src:phpunit, src:php-cache-lite] phpunit breaks php-cache-lite
autopkgtest: tries to write to /usr/bin/.phpunit.result.cache
Marked as found in versions phpunit/8.3.5-1.
> found -1 php-cache-lite/1.8.2-1
Bug #941264
control: severity -1 important
I'm downgrading because I pushed a package without the -doc build
G.
On Wed, 5 Dec 2018 17:10:19 +0200 Ilias Tsitsimpis wrote:
> Source: haskell-esqueleto
> Version: 2.5.3.git20180402-3
> Severity: serious
> Justification: fails to build from source (but built
Processing control commands:
> severity -1 important
Bug #915646 [src:haskell-esqueleto] FTBFS: haddock: internal error: internal:
extractDecl
Severity set to 'important' from 'serious'
--
915646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915646
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> found 940963 2:4.10.8+dfsg-1
Bug #940963 [samba-common-bin] samba doesn't start anymore
Marked as found in versions samba/2:4.10.8+dfsg-1.
> affects 940963 src:cups src:tdb
Bug #940963 [samba-common-bin] samba doesn't start anymore
Added
Your message dated Fri, 27 Sep 2019 08:35:27 +
with message-id
and subject line Bug#925779: fixed in mlpack 3.2.0-1
has caused the Debian Bug report #925779,
regarding mlpack: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing commands for cont...@bugs.debian.org:
> tags 941249 + pending
Bug #941249 [virt-manager] virt-manager: Can not open detail of connection and
detail or console of a VM
Ignoring request to alter tags of bug #941249 to the same tags previously set
> thanks
Stopping processing here.
Hi,
On Fri, Sep 27, 2019 at 07:59:16AM +0200, Sebastien Helleu wrote:
> Package: virt-manager
> Version: 1:2.2.1-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> After upgrade from virt-manager 2.0.0 to 2.2.1, I can not open any more
> detail of connection,
Control: tag -1 pending
Hello,
Bug #941249 in virt-manager 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 #941249 [virt-manager] virt-manager: Can not open detail of connection and
detail or console of a VM
Added tag(s) pending.
--
941249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941249
Debian Bug Tracking System
Contact
On Fri, 27 Sep 2019 07:59:16 +0200 Sebastien Helleu
wrote:
[ven., 27 sept. 2019 07:56:12 virt-manager 2944] DEBUG (cli:200) Uncaught
exception:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/xmleditor.py", line 11, in
gi.require_version("GtkSource",
Control: severity -1 normal
Processing control commands:
> severity -1 normal
Bug #940723 [java-package] java-package requires libgtk-3-0 and
libcairo-gobject2 to build java8 221
Severity set to 'normal' from 'serious'
--
940723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940723
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> tag 941018 - fixed-upstream
Bug #941018 [ibus] ibus: Regression from CVE-2019-14822 fix: does not work with
qt5 applications
Removed tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
941018:
Package: virt-manager
Version: 1:2.2.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After upgrade from virt-manager 2.0.0 to 2.2.1, I can not open any more detail
of connection, or detail/console of a VM, no window is open when I click or if
I select Open in the
53 matches
Mail list logo
