Package: zfs-dkms
Version: 0.8.1-4~bpo10+1
Severity: critical
Tags: upstream
Justification: causes serious data loss
Dear Maintainer,
recently I have noticed some instability on one of my machines.
The mprime (https://www.mersenne.org/download/) Torture Tests would occasionaly
show errors like
Processing commands for cont...@bugs.debian.org:
> tags 885189 - experimental
Bug #885189 {Done: Andreas Metzler } [src:autogen]
autogen: please migrate to guile-2.2
Removed tag(s) experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
885189:
Processing commands for cont...@bugs.debian.org:
> found 924757 anjuta/2:3.28.0-5
Bug #924757 [src:anjuta] anjuta: clean after build deletes
libanjuta/interfaces/Makefile.am.gir which is not regenerated
Marked as found in versions anjuta/2:3.28.0-5.
>
End of message, stopping processing here.
Brian May writes:
> If it is not needed anymore, and nobody has the time to maintain it,
> might be best to remove it.
Removal request sent, see Bug#940923.
--
Brian May
Package: python3-rope
Version: 0.10.5-3
Severity: grave
Dear Maintainer,
As can be seen here[1], the license of this package has been changed
from GPL to LGPL without
the consent of the main author.
[1] https://github.com/python-rope/rope/pull/266
I don't know, if it is still relevant to
The ppc64 failure was this bug, specifically the
pandas/tests/indexes/interval/test_astype.py::TestDatetimelikeSubtype::test_astype_category[index3]
version. It was retried successfully. (The hppa failure is something
else.)
The "Build environment" section of the build log (i.e. the
Processing control commands:
> forcemerge 939754 940907
Bug #939754 {Done: Jeremy Bicha } [gimp] gimp: Crashes when
I try to open an image or create a new one
Bug #939768 {Done: Jeremy Bicha } [gimp] gimp: After the
last upgrade, GIMP crashes when creating a new image or opening an existing
> Preparing to unpack .../15-libubootenv-tool_0.1-1_amd64.deb ...
> Unpacking libubootenv-tool (0.1-1) ...
> dpkg: error processing archive
> /tmp/apt-dpkg-install-S5V5yb/15-libubootenv-tool_0.1-1_amd64.deb (--unpack
> ):
> trying to overwrite '/usr/bin/fw_printenv', which is also in package
>
Processing commands for cont...@bugs.debian.org:
> # merging this bug with 921178
> severity 940914 important
Bug #940914 [uno-libs3] uno-libs3: Segfault on launch in
cppu::_copyConstructAnyFromData
Severity set to 'important' from 'grave'
> reassign 940914 libreoffice
Bug #940914 [uno-libs3]
# merging this bug with 921178
severity 940914 important
reassign 940914 libreoffice
found 940914 1:6.1.5-3+deb10u4
forcemerge 940914 921178
thanks
On Sat, Sep 21, 2019 at 09:12:36PM +0200, Michel Le Bihan wrote:
> Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
>
On Sat, Sep 21, 2019 at 09:12:36PM +0200, Michel Le Bihan wrote:
> -- System Information:
> Debian Release: 10.1
> APT prefers stable-debug
> APT policy: (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500,
> 'stable')
Just to see whether it had an affect I upgraded to
Package: python3-cxx-dev
Version: 7.0.3-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks
Hi,
during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using
tag 940914 + moreinfo
tag 940914 + unreproducible
thanks
Hi,
On Sat, Sep 21, 2019 at 09:12:36PM +0200, Michel Le Bihan wrote:
> Package: uno-libs3
> Version: 6.1.5-3+deb10u4
> Severity: grave
Why?
> Justification: renders package unusable
If this was true, yes.
Unfortunately
a) this version
Processing commands for cont...@bugs.debian.org:
> tag 940914 + moreinfo
Bug #940914 [uno-libs3] uno-libs3: Segfault on launch in
cppu::_copyConstructAnyFromData
Added tag(s) moreinfo.
> tag 940914 + unreproducible
Bug #940914 [uno-libs3] uno-libs3: Segfault on launch in
Your message dated Sat, 21 Sep 2019 20:32:08 +
with message-id
and subject line Bug#939990: fixed in bird 1.6.6-1+deb10u1
has caused the Debian Bug report #939990,
regarding bird: CVE-2019-16159
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Package: pylint
Version: 2.2.2-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks
Hi,
during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces
Processing commands for cont...@bugs.debian.org:
> tags 885189 + sid bullseye experimental
Bug #885189 {Done: Andreas Metzler } [src:autogen]
autogen: please migrate to guile-2.2
Added tag(s) sid, experimental, and bullseye.
> tags 885190 + sid bullseye
Bug #885190 [src:denemo] denemo: please
Your message dated Sat, 21 Sep 2019 19:35:06 +
with message-id
and subject line Bug#885237: fixed in remake 4.1+dbg1.3~dfsg.1-3
has caused the Debian Bug report #885237,
regarding remake: please migrate to guile-2.2
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> clone 934600 -1
Bug #934600 {Done: Alexandre Mestiashvili } [cufflinks]
cufflinks,gffread: both ship /usr/bin/gffread
Bug 934600 cloned as bug 940915
> reassign -1 gffread 0.11.4-1
Bug #940915 {Done: Alexandre Mestiashvili } [cufflinks]
Control: reassign -1 xtables-addons-dkms
Control: forcemerge 872077 -1
This is not a bug in the kernel, it's a bug in xtables-addons. This
has been fixed but unfortunately it wasn't included in the buster
release. You'll need to get the fixed version from unstable.
Ben.
--
Ben Hutchings
If
Processing control commands:
> reassign -1 xtables-addons-dkms
Bug #940802 [xtables-addons-source] linux-image-4.19.0-5-amd64: Build of
xt_ACCOUNT.ko failed for: 4.19.0-5-amd64 (x86_64)
Bug #939801 [xtables-addons-source] xtables-addons-source:
xtables-addons-2.12.0 fails to compile (kernel
Package: uno-libs3
Version: 6.1.5-3+deb10u4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
LibreOffice is crashing on launch with a segfault.
Fatal exception: Signal 11
Stack:
/usr/lib/libreoffice/program/libuno_sal.so.3(+0x3d523)[0x7f491d642523]
Processing commands for cont...@bugs.debian.org:
> close 939391 6.5.1~dfsg-1
Bug #939391 {Done: roucaries.bast...@gmail.com} [src:node-elliptic]
node-elliptic: test failure with new node-bn.js
Ignoring request to alter fixed versions of bug #939391 to the same values
previously set
Bug #939391
close 939391 6.5.1~dfsg-1
thanks
Processing commands for cont...@bugs.debian.org:
> close 939391 6.5.1~dfsg-1
Bug #939391 [src:node-elliptic] node-elliptic: test failure with new node-bn.js
Marked as fixed in versions node-elliptic/6.5.1~dfsg-1.
Bug #939391 [src:node-elliptic] node-elliptic: test failure with new node-bn.js
Processing commands for cont...@bugs.debian.org:
> unarchive 872077
Bug #872077 {Done: Mateusz Łukasik } [xtables-addons-dkms]
[xtables-addons-dkms] Error building against Linux 4.12
Unarchived Bug 872077
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
872077:
close 939391 6.5.1~dfsg-1
thanks
On Sat, Sep 21, 2019 at 06:51:16PM +0200, Cristian Ionescu-Idbohrn wrote:
> > Would you, please, start a new bug for this unless you really think
> > it is the same issue (apt being broken by continuing to uninstall
> > libsystemd0 after systemd prerm fails) and I will be happy to help.
>
> I
Your message dated Sat, 21 Sep 2019 17:35:27 +
with message-id
and subject line Bug#940888: Removed package(s) from unstable
has caused the Debian Bug report #918416,
regarding golang-github-microcosm-cc-bluemonday FTBFS with Go 1.11
to be marked as done.
This means that you claim that the
Your message dated Sat, 21 Sep 2019 17:36:00 +
with message-id
and subject line Bug#940889: Removed package(s) from unstable
has caused the Debian Bug report #917494,
regarding golang-github-jaytaylor-html2text: FTBFS (failing tests)
to be marked as done.
This means that you claim that the
Package: xserver-xorg-video-tdfx
Version: 1:1.5.0-1
Severity: serious
In version 1:1.5.0-1 xserver-xorg-video-tdfx no longer depends on
xorg-video-abi-24 and xserver-xorg-core. The reason is that commit
058dc36806b3 ("Bump debhelper to 12.") inadvertently dropped not only
autoreconf, but also
All,
I was the author of c2esp. It's hard for me to test it now because I no
longer have kodak printers.
I'm wondering if other backends also use the gstoraster filter (I'd
expect there would be others?) and do they also cause this error? Or did
I do something unusual in c2espC that's
Hi Shayan,
On Sat, Sep 21, 2019 at 05:23:49PM +0100, Shayan Doust wrote:
> This is new territory - I have spent some time looking at this and so far I
> could only reproduce all of what was already mentioned above.
It might become time consuming.
> I will later go more in-depth and try using
On Sat, 21 Sep 2019, Mark Hindley wrote:
> On Sat, Sep 21, 2019 at 04:35:39PM +0200, Cristian Ionescu-Idbohrn wrote:
> > I'm interested in this, but my systems (unstable and testing) are
> > in a slightly different state. Let's take unstable, for example:
>
> Thanks for this. However, I really
Processing control commands:
> tags -1 help
Bug #940902 [cycle] doesn't read the data
Added tag(s) help.
--
940902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 help
Dear Ana,
On Sat, Sep 21, 2019 at 05:41:27PM +0200, Ana Guerrero Lopez wrote:
> This new version of cycle, ported to python3, doesn't read the data file
> ( under .cycle) and prompts to create a new user.
>
> Not creating a new user and downgrading to the version in buster
Hello Andreas,
This is new territory - I have spent some time looking at this and so
far I could only reproduce all of what was already mentioned above.
I will later go more in-depth and try using mem profiling / debugging
and some trial and error to try figure out why this gets a
Processing commands for cont...@bugs.debian.org:
> severity 940897 serious
Bug #940897 [sdaps] sdaps: please switch from texlive-generic-recommended to
texlive-plain-generic
Severity set to 'serious' from 'normal'
> forcemerge 940897 940119
Bug #940897 [sdaps] sdaps: please switch from
Processing control commands:
> tag -1 pending
Bug #933581 [python-networkx] BD on texlive-generic-extra which isn't build
anymore and isn't in bullseye
Added tag(s) pending.
--
933581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933581
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #933581 in python-networkx 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:
Source: rexical
Version: 1.0.5-2
Severity: grave
Tags: security upstream
Justification: user security hole
Hi,
The following vulnerability was published for rexical.
CVE-2019-5477[0]:
| A command injection vulnerability in Nokogiri v1.10.3 and earlier
| allows commands to be executed in a
Cristian,
On Sat, Sep 21, 2019 at 04:35:39PM +0200, Cristian Ionescu-Idbohrn wrote:
> I'm interested in this, but my systems (unstable and testing) are in a
> slightly different state. Let's take unstable, for example:
Thanks for this. However, I really don't see it as relating to Simon's
Processing commands for cont...@bugs.debian.org:
> tags 938874 + patch
Bug #938874 [src:yum-metadata-parser] yum-metadata-parser: Python2 removal in
sid/bullseye
Added tag(s) patch.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
938874:
Your message dated Sat, 21 Sep 2019 16:05:33 +
with message-id
and subject line Bug#940185: fixed in pywps 4.2.1-4
has caused the Debian Bug report #940185,
regarding src:pywps: Debian/copyright needs update
to be marked as done.
This means that you claim that the problem has been dealt
Hi,
I'm not familiar with yum-metadata-parser at all, but
I'm not willing to remove createrepo (it depends yum-metadata-parser)
So, I've tried to fix this issue by adding python3 version.
I've added debdiff patch (may be not so good in shape), but I hope
it will help.
--
Regards,
diff -Nru
Package: cycle
Version: 0.3.1-16
Severity: grave
Hi,
This new version of cycle, ported to python3, doesn't read the data file
( under .cycle) and prompts to create a new user.
Not creating a new user and downgrading to the version in buster (-14), allows
to continue using the application with
Le samedi, 21 septembre 2019, 16.24:30 h CEST Brian Potkin a écrit :
> > There's clearly a regression in ghostscript 9.28 that started segfaulting
> > in the c2esp filter chain. But I can't manage to reproduce it outside of
> > the "cups + c2esp + cups-filters (gstoraster) + ghostscript"
Processing commands for cont...@bugs.debian.org:
> tags 938874 + py2keep
Unknown tag/s: py2keep.
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 experimental
Processing commands for cont...@bugs.debian.org:
> reassign 940885 nvidia-driver-libs-nonglvnd 430.40-2
Bug #940885 [nvidia-driver] bumblebee can not active the secondary GPU to run
opengl program after upgrade nvidia-driver to 430
Bug reassigned from package 'nvidia-driver' to
On Sat 21 Sep 2019 at 10:22:22 +0200, Didier 'OdyX' Raboud wrote:
[...]
> Using snapshot.debian.org:
>
> * ghostscript 9.27~dfsg-3.1 works
> * ghostscript 9.28~~rc1~dfsg-1 and all the later versions segfault
>
> So…
>
> There's clearly a regression in ghostscript 9.28 that started segfaulting
On Sat, 21 Sep 2019, Mark Hindley wrote:
>
> Removing the pending tag as I don't think there is anything for
> elogind to do to fix this.
Hi,
I'm interested in this, but my systems (unstable and testing) are in a
slightly different state. Let's take unstable, for example:
,
| #
Your message dated Sat, 21 Sep 2019 13:04:09 +
with message-id
and subject line Bug#885189: fixed in autogen 1:5.18.16-1
has caused the Debian Bug report #885189,
regarding autogen: please migrate to guile-2.2
to be marked as done.
This means that you claim that the problem has been dealt
Control: tags -1 - pending
On Fri, Sep 20, 2019 at 04:30:00PM +0200, Thorsten Glaser wrote:
> On Thu, 19 Sep 2019, Mark Hindley wrote:
>
> > On irc he also said there was little point in adding the Breaks: as apt
> > doesn't
> > rexec itself.
>
> Yes, even a Pre-Depends would not achieve
Processing control commands:
> tags -1 - pending
Bug #934491 [libelogind0] libelogind0: failing to switch from systemd to
sysvinit-core/elogind results in libsystemd.so.0 disappearing
Removed tag(s) pending.
--
934491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934491
Debian Bug
Julian,
On Wed, Sep 11, 2019 at 02:28:55PM +0100, Mark Hindley wrote:
> > I don't think it's reasonable to ship this package with C/R/P
> > libsystemd0.
>
> I understand that you don't like it. However, for libelogind0 to export the
> same
> symbols as libsystemd0 so that it could C/R/P
Your message dated Sat, 21 Sep 2019 09:35:41 +
with message-id
and subject line Bug#939439: fixed in websockify 0.8.0+dfsg1-16
has caused the Debian Bug report #939439,
regarding python3-websockify: trying to overwrite
'/usr/share/man/man1/websockify.1.gz', which is also in package
Your message dated Sat, 21 Sep 2019 09:35:27 +
with message-id
and subject line Bug#915895: fixed in redis-py-cluster 2.0.0-1
has caused the Debian Bug report #915895,
regarding python-limits FTBFS: ERROR: Failure: ImportError (cannot import name
b)
to be marked as done.
This means that you
Laurent,
On Fri, Sep 20, 2019 at 09:06:57AM +0200, Laurent Bigonville wrote:
> Hello,
>
> When I looked I elogind a while back I was able to build a package without
> having a public libelogind0, I basically had that in my debian/rules file:
>
> # We only build the libelogind0 and
Control: tag -1 pending
Hello,
Bug #939439 in websockify 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 #939439 in websockify 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 #939439 in websockify 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 #939439 [python3-websockify,websockify] python3-websockify: trying to
overwrite '/usr/share/man/man1/websockify.1.gz', which is also in package
websockify 0.8.0+dfsg1-14
Added tag(s) pending.
--
939439:
Processing control commands:
> tag -1 pending
Bug #939439 [python3-websockify,websockify] python3-websockify: trying to
overwrite '/usr/share/man/man1/websockify.1.gz', which is also in package
websockify 0.8.0+dfsg1-14
Ignoring request to alter tags of bug #939439 to the same tags previously
Processing control commands:
> tag -1 pending
Bug #939439 [python3-websockify,websockify] python3-websockify: trying to
overwrite '/usr/share/man/man1/websockify.1.gz', which is also in package
websockify 0.8.0+dfsg1-14
Ignoring request to alter tags of bug #939439 to the same tags previously
On 9/7/19 6:05 AM, Sandro Tosi wrote:
> control: severity -1 serious
>
> On Mon, 30 Oct 2017 10:46:21 +0800 Drew Parsons wrote:
>> python-turbogears2 is currently only provided as a python2 module.
>>
>> Could you please also package the python3 version?
>> i.e. provide python3-turbogears2
>
>
Processing control commands:
> notfound -1 c2esp/27-4
Bug #940127 [src:ghostscript, src:c2esp] ghostscript makes c2esp autopkgtest
timeout
No longer marked as found in versions c2esp/27-4.
> affects -1 c2esp
Bug #940127 [src:ghostscript, src:c2esp] ghostscript makes c2esp autopkgtest
timeout
Control: notfound -1 c2esp/27-4
Control: affects -1 c2esp
Control: found -1 ghostscript/9.28~~rc1~dfsg-1
Control: retitle -1 gs segfaults in c2esp filter chain
Hi Paul,
thanks for the detailed report.
Le jeudi, 12 septembre 2019, 19.27:46 h CEST Paul Gevers a écrit :
> Dear maintainers,
>
>
Hello Rebecca,
>Running just the affected test files (in installed -6) produced no
>failures in ~350 attempts. The build of -7 succeeded on amd64; it
>failed on ppc64, but as the log isn't available yet, I don't know if
>it's this bug.
I don't think so, when log is not available it might
Hi Eric,
any idea when you might find some time to comment on this build issue.
Its really urgent now and since we are basically two years in an
unchanged situation that the package does not build I have no idea
what to tell the release team.
Kind regards
Andreas.
On Fri, Sep 06, 2019
Hi,
On Fri, Sep 20, 2019 at 11:55:03PM +0200, Moritz Mühlenhoff wrote:
> On Fri, Sep 20, 2019 at 06:41:05PM -0300, Lisandro Damián Nicanor Pérez Meyer
> wrote:
> > I've created a WIP merge request at
> >
> > https://salsa.debian.org/med-team/sofa-framework/merge_requests/1
> >
> > I could
Source: openconnect
Version: 8.02-1
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 7.08-1
Hi,
The following vulnerability was published for openconnect.
CVE-2019-16239[0]:
| process_http_response in OpenConnect before 8.05 has a Buffer Overflow
|
Processing control commands:
> found -1 7.08-1
Bug #940871 [src:openconnect] openconnect: CVE-2019-16239: Fix buffer overflow
with chunked HTTP handling
Marked as found in versions openconnect/7.08-1.
--
940871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940871
Debian Bug Tracking
72 matches
Mail list logo