Source: pandas
Version: 1.1.5+dfsg-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent change in testing the autopkgtest of your package started
to fail. I copied some of the output at the bottom of
Source: sonic-pi
Version: 3.2.2~repack-6
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky
Dear maintainer(s),
The autopkgtest of your package turned up as blocking xorg-server. I
looked into the history of your
Package: firefox-esr
Version: 78.6.1esr-1~deb10u1
Severity: serious
Justification: 4
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I executed package updates and upgrades using apt
* What exactly
Hi,
I think it is time to fix this bug and upload package. Let me make
final check. Osamu
On Fri, 2021-01-08 at 23:28 -0500, Boyuan Yang wrote:
> Hi,
>
> 在 2021-01-08星期五的 09:49 +0800，xiao sheng wen(肖盛文)写道：
> > Hi,
> >
> > libopencc2-data had change name to libopencc-data in bullseye
> >
Package: chromium
Version: 87.0.4280.88-0.4
Severity: grave
X-Debbugs-Cc: deb...@rocketjump.eu
Hi,
starting chromium on bullseye will render a window (with various elements
shifted down by half a screen), which is impossible to interact with, and causes
gnome to offer a "force quit" prompt after
Hi,
在 2021-01-08星期五的 09:49 +0800，xiao sheng wen(肖盛文)写道：
> Hi,
>
> libopencc2-data had change name to libopencc-data in bullseye
> sid.
>
> As the opencc upstream had changed the version number, SONAME, etc.
>
> Update debian-reference build-depends on libopencc-data should fix
> this bug.
Your message dated Sat, 09 Jan 2021 04:18:57 +
with message-id
and subject line Bug#969275: fixed in python-uvicorn 0.13.3-1
has caused the Debian Bug report #969275,
regarding python-uvicorn: CVE-2020-7695
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sat, 09 Jan 2021 04:18:57 +
with message-id
and subject line Bug#969276: fixed in python-uvicorn 0.13.3-1
has caused the Debian Bug report #969276,
regarding python-uvicorn: CVE-2020-7694
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing control commands:
> reassign -1 libxnvctrl-dev
Bug #978192 [src:xfce4-sensors-plugin] xfce4-sensors-plugin: FTBFS:
NVCtrlLib.h:42:1: error: unknown type name ‘Bool’; did you mean ‘bool’?
Bug reassigned from package 'src:xfce4-sensors-plugin' to 'libxnvctrl-dev'.
No longer marked as
Followup-For: Bug #978192
Control: reassign -1 libxnvctrl-dev
Control: affects -1 + src:xfce4-sensors-plugin
NVCtrlLib.h uses macros from X11/Xlib.h but does not include that header.
So including NVCtrlLib.h only worked if X11/Xlib.h was accidentally
included earlier, which no longer is the case:
Package: seamly2d
Version: 0.6.0.2+20201207+ds-1
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Seamly2D is a fork of Valentina. Valentina is already in Debian.
Original author Roman Telezhynskyi a.k.a. dismine developed the code
until
Processing commands for cont...@bugs.debian.org:
> found 972729 0.0~git20200918.3dc0328-3
Bug #972729 [gloo] gloo: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath
There is no source info for the package 'gloo' at version
'0.0~git20200918.3dc0328-3' with architecture ''
Unable to make a
Another reminder about why it's important to handle this also in the
supported releases:
https://askubuntu.com/q/1306202
--
Gunnar Hjalmarsson
https://launchpad.net/~gunnarhj
Your message dated Sat, 09 Jan 2021 01:25:37 +
with message-id
and subject line Bug#976780: fixed in pycuda 2020.1~dfsg-1
has caused the Debian Bug report #976780,
regarding pycuda needs a manual upload to drop Python 3.8 support
to be marked as done.
This means that you claim that the
Your message dated Sat, 09 Jan 2021 01:04:19 +
with message-id
and subject line Bug#979601: fixed in git-lfs 2.13.1-2
has caused the Debian Bug report #979601,
regarding git-lfs: autopkgtest failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing commands for cont...@bugs.debian.org:
> severity 978336 normal
Bug #978336 {Done: Adrian Bunk } [src:picolisp] picolisp:
FTBFS: flood -- Undefined
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
978336:
On Fri, 8 Jan 2021 at 21:15, Lisandro Damián Nicanor Pérez Meyer
wrote:
>
> Hi! Explicitely CCing my bug, since it seems it missed my previous reply.
>
> On Fri, 8 Jan 2021 at 20:49, Guillem Jover wrote:
> >
> > On Fri, 2021-01-08 at 19:23:13 -0300, Lisandro Damián Nicanor Pérez Meyer
> >
Hi! Explicitely CCing my bug, since it seems it missed my previous reply.
On Fri, 8 Jan 2021 at 20:49, Guillem Jover wrote:
>
> On Fri, 2021-01-08 at 19:23:13 -0300, Lisandro Damián Nicanor Pérez Meyer
> wrote:
> > [snip]
> > > We did a full archive rebuild testing this change, and I provided
>
Your message dated Sat, 9 Jan 2021 00:13:15 +0200
with message-id <20210108221312.ga26...@tty.gr>
and subject line Re: Bug#961958: librdkafka++1: Zero-size library on several
architectures
has caused the Debian Bug report #961958,
regarding librdkafka++1: Zero-size library on several
Package: termtris
Version: 1.3-1
Followup-For: Bug #966877
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com
Control: tags -1 patch
Hi,
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/gcc-10.patch: Fix
Processing control commands:
> tags -1 patch
Bug #966877 [src:termtris] termtris: FTBFS: ld:
src/game.o:/<>/src/game.h:21: multiple definition of `quit';
src/ansi.o:/<>/src/game.h:21: first defined here
Added tag(s) patch.
--
966877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966877
Processing control commands:
> tags -1 patch
Bug #957902 [src:uronode] uronode: ftbfs with GCC-10
Added tag(s) patch.
--
957902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957902
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: uronode
Version: 2.10-1
Followup-For: Bug #957902
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com
Control: tags -1 patch
Hi,
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/gcc-10.patch: Fix
Your message dated Fri, 08 Jan 2021 21:18:26 +
with message-id
and subject line Bug#979569: fixed in frama-c 20201209+titanium-3
has caused the Debian Bug report #979569,
regarding frama-c ftbfs on armel, mipsel and mips64el
to be marked as done.
This means that you claim that the problem
Source: git-lfs
Version: 2.13.1-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org
git-lfs is currently unable to migrate to testing because it fails its
autopkgtest:
| rm obj-x86_64-linux-gnu/bin/cmd
| rm: cannot remove 'obj-x86_64-linux-gnu/bin/cmd': No such file or directory
| make[1]: ***
> In xscreensaver (or maybe lightdm).
> Why is xscreensaver started in the lightdm session anyway?
> Is xscreensaver really usable as a per user service or should it be per
> session?
> Why is the lightdm xscreensaver instance interfering with the xscreensaver
> instance of the logged in user?
>
Source: ucx
Version: 1.10.0~rc1-1
Severity: serious
X-Debbugs-Cc: Alastair McKinstry
The maintainer address is invalid, see below.
Ansgar
Start of forwarded message
From: Mail Delivery System
Subject: Mail delivery failed: returning message to sender
On Fri, Jan 08, 2021 at 11:30:21PM +0800, Shengjing Zhu wrote:
On Fri, Jan 8, 2021 at 11:17 PM Alberto Bertogli
wrote:
On Thu, Jan 07, 2021 at 11:12:24PM +0800, Shengjing Zhu wrote:
>On Thu, Jan 7, 2021 at 10:59 PM Alberto Bertogli
> wrote:
>> But those issues are not made worse by allowing
Your message dated Fri, 08 Jan 2021 20:22:32 +
with message-id
and subject line Bug#978382: fixed in phpmyadmin 4:5.0.4+dfsg1-1
has caused the Debian Bug report #978382,
regarding phpmyadmin: FTBFS: Test directory "./test/engines" not found
to be marked as done.
This means that you claim
Your message dated Fri, 08 Jan 2021 20:20:44 +
with message-id
and subject line Bug#977246: fixed in lutris 0.5.8.2-1
has caused the Debian Bug report #977246,
regarding lutris should depend on python3-dbus
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing commands for cont...@bugs.debian.org:
> limit source phpmyadmin
Limiting to bugs with field 'source' containing at least one of 'phpmyadmin'
Limit currently set to 'source':'phpmyadmin'
> tags 977983 + pending
Bug #977983 [phpmyadmin] Should not build-depend on composer
Added tag(s)
Processing control commands:
> tags -1 patch
Bug #966861 [src:vilistextum] vilistextum: FTBFS: ld: html.o:./src/text.h:16:
multiple definition of `ch'; charset.o:./src/text.h:16: first defined here
Added tag(s) patch.
--
966861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966861
Debian
Package: vilistextum
Version: 2.6.9-1.2
Followup-For: Bug #966861
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu hirsute ubuntu-patch
X-Debbugs-Cc: lo...@ubuntu.com
Control: tags -1 patch
Hi,
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/gcc-10.patch:
Processing commands for cont...@bugs.debian.org:
> severity 978146 important
Bug #978146 [geary] geary: Geary segfaults on startup after upgrade to 3.38.1-1
Severity set to 'important' from 'grave'
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
978146:
Processing control commands:
> severity -1 important
Bug #974779 [julia] julia: Please upgrade to llvm-toolchain-11
Severity set to 'important' from 'serious'
--
974779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
control: severity -1 important
I agree on reopening, but I don't think this is a serious issue anymore, since
we plan to ship stable with
llvm-9 and llvm-11
G.
On Fri, 8 Jan 2021 13:21:40 +0100 Sylvestre Ledru wrote:
> control: reopen -1
>
> It isn't fixed for real as Julia needs to be
Processing commands for cont...@bugs.debian.org:
> reopen 976930
Bug #976930 {Done: Carsten Schoenert } [src:arduino]
arduino: FTBFS on ppc64el (arch:all-only src pkg): Target "${platform}-build"
does not exist in the project "Arduino".
'reopen' may be inappropriate when a bug has been closed
Your message dated Fri, 08 Jan 2021 18:33:24 +
with message-id
and subject line Bug#952313: fixed in arduino-builder 1.3.25-2~exp1
has caused the Debian Bug report #952313,
regarding arduino-builder: FTBFS: failed to initialize build cache at
/sbuild-nonexistent/.cache/go-build: mkdir
Processing commands for cont...@bugs.debian.org:
> reassign 979520 src:chromium
Bug #979520 [chromium] chromium: Security upgrade to version 87.0.4280.141
Bug reassigned from package 'chromium' to 'src:chromium'.
No longer marked as found in versions chromium/87.0.4280.88-0.4.
Ignoring request to
Am 08.01.21 um 14:12 schrieb Eduard Bloch:
Hallo,
I don't fully agree. If you don't see a problem here, WHERE do you see
it?
In xscreensaver (or maybe lightdm).
Why is xscreensaver started in the lightdm session anyway?
Is xscreensaver really usable as a per user service or should it be per
In data venerdì 8 gennaio 2021 12:38:20 CET, Gianfranco Costamagna ha scritto:
> llvm-toolchain-11 is now fixed, and clazy should be fixed too.
No, llvm-toolchain-11 is not fixed yet.
> Unfortunately clazy seems to be missing a "break" relationship against old
> llvm, and britney uses
> the
On 2021-01-08, Lisandro Damián Nicanor Pérez Meyer wrote:
> On Fri, 13 Nov 2020 at 17:40, Vagrant Cascadian
> wrote:
>>
>> On 2020-11-13, Sune Vuorela wrote:
>> > On 2020-10-27, Vagrant Cascadian wrote:
>> >> Though, of course, identifying the exact reproducibility problem would
>> >> be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2021-01-08 at 14:10 +0200, Juhani Numminen wrote:
> Thank you Yves-Alexis for implementing this in orage/4.12.1-8.
>
> I noticed that the removal request still stands (
> https://bugs.debian.org/977628 ).
> Do you still intend to remove
Hello,
I'm working on the update, but I encountered an unexpected issue. The
update was easy. Patches did not require updating. The problem, is that
Chromium IU is frozen. Chromium itself isn't and the globe on
https://en.wikipedia.org/wiki/GIF spins, but Chromium doesn't react to
any UI input.
On Mon, Dec 21, 2020 at 11:30:14PM +0200, Adrian Bunk wrote:
> > I see that the build eventually succeeded:
> >
> >
> > https://buildd.debian.org/status/logs.php?pkg=geary=3.38.1-1=mipsel
> >
> > The webkit2gtk build is flaky itself in mipsel, we discussed this
> > already in the past
On Fri, Jan 08, 2021 at 05:36:58PM +0100, Paul Gevers wrote:
> The srt source package is RC buggy and has just been orphaned. We'll
> probably remove it soon from bullseye. nageru will go too then, unless
> it drop the (apparent optional) Build-Depends.
That's sad to hear. I'll drop the B-D in an
Severity: important
Changing the severity to important as it turns out that a workaround
exists (ie: remove the user's geary config).
Also, since Geary does not support POP accounts, I don't believe any
data loss would happen (one just need to resync their imap emails).
Given those info,
Source: golang-github-spf13-cobra
Version: 1.1.1-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With time moving the year to 2021, the autopkgtest of your package
started to fail. I copied some of the output
Processing control commands:
> block -1 by 971754
Bug #979582 [src:nageru] nageru: please drop the Build-Depends on
libsrt-gnutls-dev which is RC-buggy
979582 was not blocked by any bugs.
979582 was not blocking any bugs.
Added blocking bug(s) of 979582: 971754
--
979582:
Source: nageru
Version: 2.0.1-1
Severity: serious
Justification: B-D RC buggy
Control: block -1 by 971754
Hi Steinar,
The srt source package is RC buggy and has just been orphaned. We'll
probably remove it soon from bullseye. nageru will go too then, unless
it drop the (apparent optional)
Your message dated Fri, 08 Jan 2021 16:33:34 +
with message-id
and subject line Bug#976930: fixed in arduino 2:1.8.13+dfsg1-1~exp1
has caused the Debian Bug report #976930,
regarding arduino: FTBFS on ppc64el (arch:all-only src pkg): Target
"${platform}-build" does not exist in the project
Your message dated Fri, 08 Jan 2021 16:33:34 +
with message-id
and subject line Bug#891901: fixed in arduino 2:1.8.13+dfsg1-1~exp1
has caused the Debian Bug report #891901,
regarding arduino: Doesn't open.
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Fri, 08 Jan 2021 16:33:34 +
with message-id
and subject line Bug#877201: fixed in arduino 2:1.8.13+dfsg1-1~exp1
has caused the Debian Bug report #877201,
regarding arduino: broken symlink: /usr/share/arduino/lib/libastylej.so ->
../../../lib/jni/libastylej.so
to be marked
Your message dated Fri, 08 Jan 2021 16:33:34 +
with message-id
and subject line Bug#876495: fixed in arduino 2:1.8.13+dfsg1-1~exp1
has caused the Debian Bug report #876495,
regarding arduino: FTBFS error: is not abstract and does
not override abstract method
HI Sebastian,
On Thu, 07 Jan 2021 12:56:42 +0200 Sebastian =?ISO-8859-1?Q?Dr=F6ge?=
wrote:
> That seems like something for the maintainer to figure out IMHO but
> they didn't even respond to #971754 yet.
They orphaned the package today after I inquired on the progress.
> There's going to be
Package: src:openjdk-15
Version: 15.0.1+9-3
Severity: serious
OpenJDK 15 should stay out of testing. We stil want to keep it unstable, as it
is the latest released version.
Processing commands for cont...@bugs.debian.org:
> forcemerge 979533 979520
Bug #979533 [src:chromium] chromium: New 87.0.4280.141 (CVE-2020-15995
CVE-2020-16043 CVE-2021-21106 CVE-2021-21107 CVE-2021-21108 CVE-2021-21109
CVE-2021-21110 CVE-2021-2 CVE-2021-21112 CVE-2021-21113
Your message dated Fri, 08 Jan 2021 16:05:34 +
with message-id
and subject line Bug#957991: fixed in xneur 0.20.0-3
has caused the Debian Bug report #957991,
regarding xneur: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Fri, 08 Jan 2021 16:05:34 +
with message-id
and subject line Bug#956680: fixed in xneur 0.20.0-3
has caused the Debian Bug report #956680,
regarding xneur: Please migrate to enchant-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Hi,
the package has been dropped from testing a while ago due to this bug
but it's not clear to me that there's a real bug here.
On Wed, 23 Sep 2020, Matthias Klose wrote:
> Package: pipx
> Version: 0.12.3.1-3
> Severity: serious
> Tags: sid bullseye
>
> This package depends or build-depends on
On Fri, Jan 8, 2021 at 11:17 PM Alberto Bertogli
wrote:
>
> On Thu, Jan 07, 2021 at 11:12:24PM +0800, Shengjing Zhu wrote:
> >On Thu, Jan 7, 2021 at 10:59 PM Alberto Bertogli
> > wrote:
> >> But those issues are not made worse by allowing golang-google-protobuf
> >> to go in, right?
> >>
> >
>
On Thu, Jan 07, 2021 at 11:12:24PM +0800, Shengjing Zhu wrote:
On Thu, Jan 7, 2021 at 10:59 PM Alberto Bertogli
wrote:
But those issues are not made worse by allowing golang-google-protobuf
to go in, right?
Let golang-google-protobuf go in is one thing, it's not difficult.
However without
Your message dated Fri, 08 Jan 2021 14:51:00 +
with message-id
and subject line Bug#978066: fixed in pmix 4.0.0-2
has caused the Debian Bug report #978066,
regarding pmix: breaks openmpi autopkgtest
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Fri, 08 Jan 2021 14:49:47 +
with message-id
and subject line Bug#971615: fixed in golang-github-russellhaering-goxmldsig
1.1.0-1
has caused the Debian Bug report #971615,
regarding golang-github-russellhaering-goxmldsig: CVE-2020-15216
to be marked as done.
This means
My reply bounced with
: host gretel.discordia.ch[185.95.218.132] said: 530
5.7.0 Must issue a STARTTLS command first (in reply to MAIL FROM command)
Andreas
Thanks, Jan. I killed chromium, upgraded to 87* again, and re-launched
with the recommended command last night. The user is back on this
morning and I'm monitoring from another machine.
Steve
Jan Luca Naumann wrote on 1/7/21 2:30 AM:
Dear Steve,
with the upgrade to 87.* we included the
On 1/8/21 3:15 PM, Peter Keel wrote:
> [82609.756755] nvidia-modeset/: page allocation failure: order:4,
> mode:0x40cc0(GFP_KERNEL|__GFP_COMP), nodemask=
You could try the 460.xx beta driver from experimental which seems to
have a fix for that:
- Improved the memory allocation strategy in
Your message dated Fri, 08 Jan 2021 14:26:51 +
with message-id
and subject line Bug#971127: fixed in ofxstatement-plugins 20210108
has caused the Debian Bug report #971127,
regarding ofxstatement-plugins: FTBFS: AssertionError: Failed doctest test
Processing control commands:
> tag -1 pending
Bug #971615 [src:golang-github-russellhaering-goxmldsig]
golang-github-russellhaering-goxmldsig: CVE-2020-15216
Added tag(s) pending.
--
971615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971615
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #971615 in golang-github-russellhaering-goxmldsig 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:
Ack, merge request created.
I had already built ldb with the patch for both unstable and the
environment I ran into issues due to the symbols check and also rebuilt
samba in both afterwards. Both built fine and at least basic functionality
tests also worked fine.
Am Fr., 8. Jan. 2021 um 13:33 Uhr
close 972301 3.5.0+dfsg1-5
thanks
Source: dpkg
Version: 1.20.6
Severity: serious
Justification: Breaks well defined functionality
X-Debbugs-Cc: pkg-kde-t...@alioth-lists.debian.net,
reproducible-bui...@lists.alioth.debian.org
Hi! As discussed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876901
mangling __FILE__, even if
Processing commands for cont...@bugs.debian.org:
> close 972301 3.5.0+dfsg1-5
Bug #972301 [ignition-common] ignition-common: FTBFS with
DEB_BUILD_OPTIONS=reproducible=+fixfilepath
There is no source info for the package 'ignition-common' at version
'3.5.0+dfsg1-5' with architecture ''
Unable to
Package:src:frama-c
Version: 20201209+titanium-2
Severity: serious
Tags: sid bullseye
[...]
ocamlfind: Not supported in your configuration: ocamlopt
make[1]: *** [share/Makefile.generic:88: src/libraries/stdlib/extlib.cmx] Error
2
make[1]: *** Waiting for unfinished jobs
make[1]: Leaving
Your message dated Fri, 08 Jan 2021 13:19:04 +
with message-id
and subject line Bug#972308: fixed in kookbook 0.2.1-2
has caused the Debian Bug report #972308,
regarding kookbook: FTBFS with DEB_BUILD_OPTIONS=reproducible=+fixfilepath
to be marked as done.
This means that you claim that the
Hallo,
I don't fully agree. If you don't see a problem here, WHERE do you see
it?
Under my naive assumptions, it looks like SIGTERM is not sent when
lightdm stops the service. So apparently a systemd issue.
I would like to investigate more but a there seems to be no "debug" or
"trace" mode for
Source: libnfo
Version: 1.0.1-1
Severity: serious
Tags: bullseye sid
X-Debbugs-Cc: Holger Levsen
The maintainer address is invalid, see below.
Ansgar
Start of forwarded message
From: Mail Delivery System
Subject: Mail delivery failed: returning
Your message dated Fri, 08 Jan 2021 12:48:40 +
with message-id
and subject line Bug#978936: fixed in darktable 3.4.0-2
has caused the Debian Bug report #978936,
regarding darktable: FTBFS on arm64
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing control commands:
> reassign -1 xscreensaver
Bug #979562 [systemd] lightdm session termination does not stop xscreensaver
Bug reassigned from package 'systemd' to 'xscreensaver'.
No longer marked as found in versions systemd/247.2-4.
Ignoring request to alter fixed versions of bug
Control: reassign -1 xscreensaver
I don't see a systemd problem here, so re-assigning to xscreensaver.
Am 08.01.21 um 13:04 schrieb Eduard Bloch:
Package: systemd
Version: 247.2-4
Severity: serious
Hi,
I am reporting this with high severity because it might affect system
security.
For
Le lun. 21 déc. 2020 à 16:06, Sven Mueller a écrit :
>
> Well, turns out that apparently nobody else bothers with a .symbols file for
> Python extensions. I looked at the packages for samba, numpy, mypy and
> python-stdlib-extensions. And if the Python maintainers themselves don't do
> it, you
For the record in bug #954270,
to delay autoremoval of iva and kmc from testing scheduled on 2021-01-09,
I'm writing this little status update regarding their testing migration.
My understanding is that kmc and iva shall migrate to testing once the
FTP Team processes this removal request:
Processing control commands:
> reopen -1
Bug #974779 {Done: Gianfranco Costamagna } [julia]
julia: Please upgrade to llvm-toolchain-11
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No
control: reopen -1
It isn't fixed for real as Julia needs to be updated!
S
Le 08/01/2021 à 13:06, Debian Bug Tracking System a écrit :
This is an automatic notification regarding your Bug report
which was filed against the julia package:
#974779: julia: Please upgrade to llvm-toolchain-11
Package: gitlab
Version: 13.5.6-1
Severity: grave
Uploaded gitlab 13.5.6 to experimental for more testing, but some core
features are broken, likely due to new version of rugged/libgit2
already in debian which upstream does not support yet.
When visiting any project, for example,
tags 977628 + moreinfo
thanks
On Tue, 5 Jan 2021 16:13:29 +0100 Slavko wrote:
> Hi,
>
> quick look into ./configure --help shows the --disable-libxfce4panel
> option, while i do not understand it in depth, but can be quick
> solution.
>
> If i properly understand, it will not be usable with
Hi Gianfranco,
Thanks for looking into this, very much appreciated!
Do we really need a new upload of Julia, or can't we kick of a new trial build
at ppc64el?
Also, if an upload is necessary and someone else in the Julia team beats me, no
problem with that ;-)
Again thanks a lot for your
Your message dated Fri, 08 Jan 2021 12:03:40 +
with message-id
and subject line Bug#974779: fixed in llvm-toolchain-9 1:9.0.1-16
has caused the Debian Bug report #974779,
regarding julia: Please upgrade to llvm-toolchain-11
to be marked as done.
This means that you claim that the problem has
Watch out version dependency, too. It will not work with v2.0 (2.0.0+dfsg-1+b1)
g
Hello Norbert,
On Fri, 8 Jan 2021 19:59:10 +0900 Norbert Preining
wrote:
> Dear Sebastian,
>
> thanks for your email!
>
> > Sylvestre, could you apply the two patches to llvm-toolchain-9 so that
> > we can check if that fixes the julia build on ppc64el?
>
> If you want me to do anything
control: reopen -1
Hello Pino,
llvm-toolchain-11 is now fixed, and clazy should be fixed too.
Unfortunately clazy seems to be missing a "break" relationship against old
llvm, and britney uses
the broken testing version to test it.
I don't know if we can hint to let it migrate anyway, or we
Processing control commands:
> reopen -1
Bug #977814 {Done: Sylvestre Ledru }
[src:llvm-toolchain-11] llvm-toolchain-11/1:11.0.1~+rc1-1 breaks behaviour with
1:11.0.0-5
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need
Your message dated Fri, 08 Jan 2021 11:33:33 +
with message-id
and subject line Bug#971309: fixed in ansible 2.9.16+dfsg-1.1
has caused the Debian Bug report #971309,
regarding ansible: Switch to python3-pycryptodome
to be marked as done.
This means that you claim that the problem has been
Dear Sebastian,
thanks for your email!
> Sylvestre, could you apply the two patches to llvm-toolchain-9 so that
> we can check if that fixes the julia build on ppc64el?
If you want me to do anything regarding testing, please let me know, but
I don't have a ppc64el at home ;-)
> FWIW, I have
Processing control commands:
> fixed -1 0.11.0+dfsg-1
Bug #973028 [src:python-fabio] python-fabio's autopkg tests are failing with
python3.9
Marked as fixed in versions python-fabio/0.11.0+dfsg-1.
> close -1
Bug #973028 [src:python-fabio] python-fabio's autopkg tests are failing with
python3.9
control: fixed -1 0.11.0+dfsg-1
control: close -1
thanks
On Tue, 27 Oct 2020 13:34:47 +0100 Matthias Klose wrote:
> Package: src:python-fabio
> Version: 0.10.2+dfsg-2
> Severity: serious
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: python3.9
>
> see
>
Hi Norbert
On 2021-01-08 12:17:54, Norbert Preining wrote:
> Hi Sebastian,
>
> coming back to the llvm-9 vs -10 vs -11 issue.
>
> So, julia fails to build on ppc64el with llvm-9 because llvm-9 has bugs
> there, and we cannot use llvm-11 since this is not supported in the
> current version of
Additionally, I’ve found that the official releases of Chrome from
Google suffer from the same problem for me, but that the beta is fine.
So it looks like it might be fixed upstream in Chrome release 88.
Phil
On Thu, 7 Jan 2021 11:30:25 +0100 Jan Luca Naumann
wrote:
Dear Steve,
with the
Right, it should certainly not be included in its current state in next
release.
But there is more into it. If you for instance try to install Opera from
stable (or oldstable or testing or unstable...) the .deb recommends
pepperflashplugin-nonfree, and you may end up to a situation like this:
1 - 100 of 110 matches
Mail list logo
