Package: kasts
Version: 25.04.0-2
Severity: serious
kasts does not start in an out of the box install:
$ kasts
Database version 11
QQmlApplicationEngine failed to load component
qrc:/qt/qml/org/kde/kasts/qml/Main.qml:82:5: Type SettingsView unavailable
qrc:/qt/qml/org/kde/kasts/qml/Sett
Hi Simon,
On Fri, Feb 21, 2025 at 11:27:00PM +, Santiago Vila wrote:
> During a rebuild of all packages in unstable, your package failed to build:
>
>
>
> verify_test.go:563: Verify failed with error: pkcs7: failed to verify
> certificate chain: x509: certificate signed by unknown author
Control: forwarded -1 https://github.com/dell/libsmbios/pull/149
On Wed, Jan 08, 2025 at 08:36:18PM +0100, Lucas Nussbaum wrote:
> > Running ALL PYTHON tests.
> > Traceback (most recent call last):
> > File "/build/reproducible-path/libsmbios-2.4.3/src/pyunit/testAll.py",
> > line 39, in
> >
On Wed, Mar 05, 2025 at 02:51:42AM +0200, Adrian Bunk wrote:
> On Thu, Feb 20, 2025 at 11:23:20AM +0200, Faidon Liambotis wrote:
> >...
> > The API issue has been fixed upstream in a backwards-compatible way:
> > https://github.com/NixOS/nix/commit/edbfe863ce4ae4b89e554f29807e
Package: micropython
Version: 1.24.0+ds-1
Severity: serious
Tags: ftbfs
User: debian...@lists.debian.org
Usertags: i386
micropython has been FTBFSing[1] on i386 since October 2024, starting[2]
with the release of 1.24.0+ds-1, due to the following build error:
> ../py/binary.c: In function ‘mp_dec
Package: bdebstrap
Version: 0.7.0-2
Severity: serious
AIUI bdebstrap's autopkgtests are attempting to deploy a bullseye
system, using deb.debian.org as its source.
riscv64 was not an official port for bullseye and there is no such suite
in the archive for this architecture. This results in this t
Package: kde-config-sddm
Version: 4:6.2.4-1
Severity: serious
Using this KCM module, and attempting to configure SDDM from System
Settings, such as for example changing the background to an existing
theme, results in a password prompt, followed by KCM writing to the
configuration file:
/usr/share/
Source: arc-kde
Version: 20220908-2
Severity: serious
Thank you for maintaining arc-kde!
The Qt/KDE team intend to release trixie with Plasma 6 and have started
the process of uploading Plasma 6 to unstable[1].
1: https://lists.debian.org/debian-devel/2024/11/msg00327.html
arc-kde does not have
Hi Thorsten,
On Tue, Sep 17, 2024 at 09:55:14PM +, Thorsten Alteholz wrote:
> On Tue, 17 Sep 2024, Petter Reinholdtsen wrote:
> > I believe the following patch solve the build problems for hplib in
> > unstable.
>
> Thanks a lot for the patch!
What are you intentions with regards to this pat
Package: plasma-desktop
Version: 4:6.2.0-1
Severity: grave
I asked around on #debian-kde before filing this bug, but I don't think
there was a clear answer there. I'm not sure if you're welcoming bugs
against experimental, but I figured that part of uploading to
experimental is to iron out bugs be
Control: forwarded -1 https://github.com/tox-dev/pyproject-api/issues/153
On Fri, Sep 20, 2024 at 01:23:42PM +0200, Stefano Rivera wrote:
> Source: pyproject-api
> Version: 1.7.1-1
> Severity: serious
> Tags: ftbfs
> Justification: FTBFS
>
> During a test rebuild, pyproject-api failed to rebuild.
Control: tags -1 upstream fixed-upstream
Control: forwarded -1 https://github.com/gdnsd/gdnsd/issues/246
On Sun, Sep 15, 2024 at 07:31:10PM +0200, Santiago Vila wrote:
> Package: src:gdnsd
> Version: 3.8.2-2
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> During a rebuild of all packa
Control: tag -1 pending
Hello,
Bug #1075392 in pluma 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-mate-team/pluma/-/commit/64d1f0249e6bb740ec9d14b7574
Control: tag -1 pending
Hello,
Bug #1075258 in mate-applets 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-mate-team/mate-applets/-/commit/15d9f18e503f0
Control: tag -1 pending
Hello,
Bug #1074753 in mate-power-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:
https://salsa.debian.org/debian-mate-team/mate-power-manager/-/commit/d
On Tue, Aug 20, 2024 at 01:28:45PM +0200, Stefano Brivio wrote:
> > Was this before or after the time64 (and implicit LFS) transition?
>
> It turns out it was before that, and things actually started failing
> now, so I just posted a patch for armhf:
>
>
> https://archives.passt.top/passt-dev/
On Sun, Aug 18, 2024 at 10:00:57PM +0200, Stefano Brivio wrote:
> Thanks Uroš for reporting and Faidon for the analysis!
Thanks for the quick response!
> > In this case, there is a comment that states:
> > * #syscalls clock_gettime arm:clock_gettime64
> > ...but on i386, and likely other 32-bit
On Sun, Aug 11, 2024 at 12:31:21PM -0400, Reinhard Tartler wrote:
> But you are right, ultimately this decision is up to the maintainer to make.
Maintainer here :)
First of all, thanks to the both of you for caring enough about this
package to file bugs, NMU and argue about its bugs! It's helpful
Control: tags -1 + fixed-upstream
On Wed, Jul 03, 2024 at 12:36:03PM +, Matthias Klose wrote:
> command.c:472:59: error: passing argument 1 of ‘gtk_widget_get_accessible’
> from incompatible pointer type [-Wincompatible-pointer-types]
> 472 | atk_widget = gtk_widget_get_accessible (comm
Control: forwarded -1 https://github.com/stlink-org/stlink/issues/1365
Control: tags -1 + fixed-upstream
On Wed, Jul 03, 2024 at 12:45:01PM +, Matthias Klose wrote:
> /<>/src/stlink-lib/chipid.c:68:22: error: ‘calloc’ sizes
> specified with ‘sizeof’ in the earlier argument and not in the late
Control: forwarded -1
https://github.com/mate-desktop/mate-power-manager/issues/390
Control: tags -1 + patch
Dear maintainer,
On Tue, Jul 02, 2024 at 03:30:55PM +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
Attached is a (trivia
Source: bcachefs-tools
Version: 1:1.9.1-1
Severity: serious
bcachefs-tools 1:1.7.0-1 & 1:1.9.1-1 FTBFS on i386, while 1:1.9.1-1 also
FTBFS on armel and armhf.
As a result, bcachefs-tools has not reentered testing since it was
removed back in April. The 1:1.9.1-1 upload happened in the meantime
ab
Source: bcachefs-tools
Version: 24+really1.3.4-2
Severity: serious
I don't think bcachefs-tools in its current state is fit for release.
* The package is severely behind: Debian is currently at 1.3.4. Upstream
is at 1.6.4.
* Chronologically speaking, 1.3.4 was released in November 2023, so in
On Thu, Jan 11, 2024 at 01:02:47PM +, Simon McVittie wrote:
> It looks as though these are already known and already fixed in the
> packaging git repo.
Correct. I introduced these breakages with a couple of recent MRs, and
hopefully fixed them with #130. I asked Sylvestre to hold off until we
Control: tag -1 pending
Hello,
Bug #1058090 in oscrypto 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/python-team/packages/oscrypto/-/commit/d0be684e1101c03b6
Control: tags -1 + fixed-upstream
Dear maintainer,
On Tue, Dec 12, 2023 at 08:58:48AM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
>
> > File "/<>/tests/__init__.py", line 4, in
> > import imp
> > ModuleNotFoundError:
Dear Jonas,
On Mon, Aug 07, 2023 at 03:51:51PM +0300, Faidon Liambotis wrote:
> Dear maintainer, security team,
>
> (See #1032092 for a similar bug with an almost equivalent response)
I've seen that you've uploaded a couple new upstream releases of
Asterisk in the time sin
Hi,
This is now RC, which means sphinxcontrib-mermaid has been marked for
autoremoval, including its reverse dependencies (one of which I
maintain).
On Sun, Jul 30, 2023 at 08:30:07PM +0200, Lucas Nussbaum wrote:
> sphinxcontrib-mermaid fails to build with Sphinx 7.1 and docutils 0.20, both
> of
Control: affects 1052002 - wasmedge
Control: affects 1052002 + src:wasmedge
On Thu, Nov 09, 2023 at 09:52:04AM +0100, Paul Gevers wrote:
> > Hi Paul,
> > Thank you for your report. This is caused #1052002, which I had marked
> > as affects: wasmedge previously.
>
> Sorry for not checking that, bu
Hi Paul,
On Sun, Nov 05, 2023 at 01:45:34PM +0100, Paul Gevers wrote:
> Source: wasmedge
> Version: 0.13.4+dfsg-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: regression
>
> Dear maintainer(s),
>
> Your package has an autopkgtest, great. However, it fails. Can you please
>
Control: reopen -1
Control: found -1 1:16.0.6-17
This is still not fixed :( Mike's findings still stand:
On Sat, Sep 16, 2023 at 05:53:55AM +0900, Mike Hommey wrote:
> This is a regression from the upgrade to clang 16.
>
> with clang 14:
> #include "..." search starts here:
> #include <...> sear
Control: reassign -1 rustc 1.68.2+dfsg1-1
Control: retitle -1 Builds invalid wasm32 binaries (1.67->1.68 regression)
On Tue, Sep 12, 2023 at 10:56:57PM +0100, Peter Green wrote:
> The autopkgtests for wasmedge fail with rustc 1.68, I have observed this with
> both testing and unstable's versions o
Source: furo
Version: 2023.08.19+dfsg-1
Severity: grave
furo 2023.08.19+dfsg-1 requires Sphinx v6.0:
$ grep -r 'require_sphinx(' /usr/lib/python3/dist-packages/furo
/usr/lib/python3/dist-packages/furo/__init__.py:app.require_sphinx("6.0")
However:
$ rmadison -s unstable python3-sphinx
Dear maintainer, security team,
(See #1036697 for a similar bug with an almost equivalent response)
The changelog for the asterisk 1:20.4.0~dfsg+~cs6.13.40431414-1 upload
dated 2023-08-04, currently in unstable, mentions:
>+ fixate component pjproject at upstream release 2.13.1
The sources s
Dear maintainer, security team,
(See #1032092 for a similar bug with an almost equivalent response)
The changelog for the asterisk 1:20.4.0~dfsg+~cs6.13.40431414-1 upload
dated 2023-08-04, currently in unstable, mentions:
>+ fixate component pjproject at upstream release 2.13.1
The sources s
Control: forwarded -1 https://github.com/WasmEdge/WasmEdge/issues/2695
Control: tags -1 + patch
On Wed, Jul 26, 2023 at 09:50:12PM +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > /usr/bin/c++ -g
Control: forwarded -1 https://github.com/gdnsd/gdnsd/issues/236
On Wed, Jul 26, 2023 at 10:20:11PM +0200, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
Thanks Lucas. I had noticed that already and have been trying to figure
out a fix for
On Tue, Feb 21, 2023 at 02:23:34PM +0200, Adrian Bunk wrote:
> Looking at #1028371, should generated dependencies on python3-protobuf be
> python3-protobuf (>= 3.21), python3-protobuf (<< 3.22)
> to ensure that the binary package is used with the same version
> as the protobuf-compiler used durin
On Thu, Feb 23, 2023 at 12:16:41PM +0200, Faidon Liambotis wrote:
> I also have changes underway for 4.5, but currently looking into what it
> would take dependency-wise to accomplish this, as there are 1-2 new
> Python module dependencies that are not present in Debian yet. I'll
&g
On Wed, Mar 08, 2023 at 09:41:21AM +, Simon McVittie wrote:
> > there is a metapackage, libc++-dev-wasm32, which Depends on the
> > default implementation, which is libc++-14-dev-wasm32 right now. That
> > metapackage has at least one notable reverse B-D, firefox, using it to
> > build certain
On Fri, Mar 03, 2023 at 05:46:15PM +, Simon McVittie wrote:
> I've cut down what I think is the root cause of this compile failure to
> a more minimal bug report: see #1032317.
That's super helpful, thanks :) Spoiler alert: I have a suspicion on the
root cause, I'll follow up there.
> I don't
On Tue, Feb 21, 2023 at 02:16:40PM +0200, Faidon Liambotis wrote:
> I should note that while the package seems to meet the criteria for
> Salvaging (DevRef 5.12) I don't currently have the bandwidth to maintain
> it properly in the long run either. I'm happy to do a one-off NMU
Hi!
On Thu, Dec 22, 2022 at 11:06:05PM +0100, Cyril Brulebois wrote:
> Faidon Liambotis (2022-12-22):
> > Going forward there are a few options:
> > * Revert the change and depend on debconf again. This is the safest
> > option, as this has been the status quo since
Source: cdebconf
Version: 0.265
Severity: critical
cdebconf 0.265 dropped the "debconf" dependency, that Joey Hess
"temporarily" added in 2007 with cdebconf 0.123[1]. This was added to
"avoid anyone breaking their systems by removing debconf, which
dependencies now allow".
Unfortunately, that rem
On Sat, Nov 12, 2022 at 08:06:56AM +, stefa...@debian.org wrote:
> Hi Faidon (2022.11.11_22:25:52_+)
> > I don't mind having an NMU, though, whether targeted or for the new
> > upstream version itself.
>
> Sure, happy to NMU a new upstream version, too. I'll 0-day NMU that.
>
> [...]
>
> >
On Fri, Nov 11, 2022 at 11:56:18PM +0200, Stefano Rivera wrote:
> I've prepared an NMU for python-maxminddb (versioned as 2.0.3-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
Thank you so much Stefano! I've been meaning to update to the latest
upstr
On Sun, Jul 03, 2022 at 09:20:37PM +0200, Bastian Blank wrote:
> crun was not uploaded since before the release of Debian 11. It is now
> seriously out of date and even fails hard as root, see #1012053.
I built 1.4.5 using the existing Debian packaging and with no changes
other than dropping all
Package: marco
Version: 1.24.1-2
Severity: grave
Tags: patch
marco >= 1.23.2 has a memory/pixmap leak in the workspace switcher OSD,
that makes the desktop slower over time, and after a few weeks of
uptime, downright unusable. The effects can be observed using "xrestop",
where the Pxms column rise
Control: tags -1 patch
On Sat, Feb 13, 2021 at 02:53:58PM -0500, Andres Salomon wrote:
> Pulseaudio is failing to build on ppc64el. The version of pulseaudio in
> bullseye suffers from a pretty serious usability bug (see #980836)
> which should arguably be a higher severity, but let's focus on get
Package: nomad-driver-podman
Version: 0.1.0-2
Severity: grave
As discussed recently in debian-devel, nomad-driver-podman 0.1.0 works
with the podman Varlink API, which does not exist anymore in podman 3.0,
making this package unusable for all users (at least AIUI).
A new upstream release of nomad
On Fri, Jan 08, 2021 at 07:30:03PM +0100, Michel Le Bihan wrote:
> After updating libx11-xcb1 chromium and google chrome UI is not
> responding to any input and clicking anywhere on the app window causes
> the GNOME app is not responding dialog to appear. The app actually is
> not frozen because if
Package: mitmproxy
Version: 5.3.0-1
Severity: grave
Installing mitmproxy in a clean sid chroot, and running it (with no arguments)
results into a large backtrace that ends with...
pkg_resources.DistributionNotFound: The 'hyperframe>=6.0' distribution was
not found and is required by mitmproxy
Hi Andreas,
Thanks for reaching out. It sounds like this is already reported as
#951704 (Cc'ed now). I'll need to give this a closer look, but I hope I
can have an update within the next couple of weeks. Does this work?
Thanks!
Faidon
On Sun, Mar 15, 2020 at 10:33:20AM +0100, Andreas Tille wrote
On Mon, Dec 30, 2019 at 11:37:52PM -0500, Harlan Lieberman-Berg wrote:
>
>
> Based on this license change, it seems to me that geoipupdate can no
> longer be in main. Contrib may be a suitable home, however?
geoipupdate is already in contrib (it has always been that way). Did you
perhaps miss th
Package: src:python-static3
Version: 0.7.0-5
Severity: serious
Hi there,
tox's (new) maintainer here. python-static3 uses "tox" as an
autopkgtest, which is currently broken and that holds a newer version of
tox from migrating to testing. (Hence setting the severity to serious)
The use of tox her
On Wed, Jan 09, 2019 at 10:42:06PM +0100, Johannes Schauer wrote:
> Quoting Faidon Liambotis (2019-01-09 16:16:40)
> > > Until it is properly fixed upstream we can just temporarily disable
> > > --enable-prof, right?
> > We could, yes. This is a useful piece of fun
On Wed, Jan 09, 2019 at 11:23:19AM +0100, Johannes Schauer wrote:
> Maybe you can report this directly to upstream?
I thought of that, but then I saw that upstream is Piotr, who is also
listed as a Maintainer of this package. Is that not the case?
> Until it is properly fixed upstream we can just
Package: src:fakechroot
Version: 2.19-3
Severity: serious
Hi again,
So jemalloc 5.1.0-2 was recently uploaded to unstable. The build
currently fails due to the explicit dependency on libjemalloc1 (cf.
#918741), but as soon as this gets fixed, another issue is uncovered:
While building this packa
Package: src:fakechroot
Version: 2.19-3
Severity: serious
Hi,
I uploaded jemalloc 5.1.0-2 to unstable the other day. It involves a new
ABI and SONAME and thus a transition from libjemalloc1 -> libjemalloc2.
I noticed that your package Build-Depends directly on libjemalloc1, and
thus this package
On Fri, Aug 10, 2018 at 11:13:56PM +0200, Moritz Mühlenhoff wrote:
> > Please migrate to libssl-dev in the Buster cycle. The bug report about
> > the FTBFS is #828527. The log of the FTBFS can be found at
> >
> > https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/radsecproxy_1.6.7-
On Sat, Jul 07, 2018 at 04:03:39PM +0300, Ilias Tsitsimpis wrote:
> On Sat, Jun 30, 2018 at 03:59PM, Faidon Liambotis wrote:
> > I went to upstream's GitHub in order to see if anyone else had reported
> > this or to submit a PR, but to my surprise, it seems like upstream'
Package: python3-imaplib2
Version: 2.57-2
Severity: grave
Hi,
Using this test program and Gmail as the IMAP server:
M = imaplib2.IMAP4_SSL(host=IMAP_SERVER, debug=IMAP_DEBUG)
M.login(IMAP_USERNAME, IMAP_PASSWORD)
if (compress):
M.enable_compression()
M.SELECT(mailbox=IMAP
On Thu, Jan 18, 2018 at 10:36:24PM +0100, Salvatore Bonaccorso wrote:
> > > That link says:
> > > Versions Affected:
> > > Apache Tika 0.10 to 1.12
> > >
> > > So perhaps 1.5 isn't affected after all? I tried to find the relevant
> > > commit in the upstream git but failed :(
> >
> > Commit
On Fri, May 27, 2016 at 11:58:33AM +0200, Moritz Muehlenhoff wrote:
> please see http://seclists.org/oss-sec/2016/q2/413 for details.
That link says:
Versions Affected:
Apache Tika 0.10 to 1.12
So perhaps 1.5 isn't affected after all? I tried to find the relevant
commit in the upstream git
On Tue, Nov 07, 2017 at 05:07:42PM +, James Cowgill wrote:
> Ah nevermind - I see it FTBFS in experimental on lots of arches.
Yeah, I've fixed some in git already and been working with upstream on a
lot of those (upstream #761, #979, #985, #999). They've been extremely
collaborative (and even
Hi Julien!
On Fri, Oct 06, 2017 at 10:13:11PM +0200, Julien Cristau wrote:
> certspotter FTBFS on the mips and mipsel buildds with no useful error message:
>
> > dh_auto_build: go install
> > -gcflags=\"-trimpath=/<>/obj-mips-linux-gnu/src\"
> > -asmflags=\"-trimpath=/<>/obj-mips-linux-gnu/src\
Hi Andreas,
Thanks for the bug report.
On Fri, Sep 29, 2017 at 10:55:59PM +0200, Andreas Beckmann wrote:
> jemalloc 5 FTBFS on all 32-bit architectures since the signatures for
> operator new/delete have changed with GCC 7:
I don't think it's a GCC 7 issue. I think it was just a packaging error
On Fri, Feb 10, 2017 at 08:18:42PM -0500, Sandro Tosi wrote:
> is this really a serious bug which `is a severe violation of Debian
> policy (roughly, it violates a must or required directive), or, in the
> package maintainer's or release manager's opinion, makes the package
> unsuitable for release
Source: diamond
Version: 4.0.515-3
Severity: serious
In my setup, diamond takes a long time to stop after getting a SIGTERM
from systemd, thus slowing down the overall shutdown of the system by
about a minute (and also making it slow to perform restarts). When it
finally does stop, an error messag
On Tue, Jan 24, 2017 at 03:57:08PM +, Mike Gabriel wrote:
> I just spoke to the developer who worked on PR #110 for mate-screensaver. He
> said that one of the two commits was for beautifications, the one that made
> it into 1.16.1 is the actual fix-up commit.
That's great :)
> Saying this, i
forwarded 828527 https://project.nordu.net/browse/RADSECPROXY-66
tags 828527 + pending
thanks
On Sun, Jun 26, 2016 at 12:23:56PM +0200, Kurt Roeckx wrote:
> OpenSSL 1.1.0 is about to released. During a rebuild of all packages using
> OpenSSL this package fail to build. A log of that build can be
reopen 831529
reassign 831529 libavcodec57 7:3.1.1-2
forcemerge 831909 831529
thanks
Hi,
On Sun, Jul 24, 2016 at 02:53:57PM +0200, Sebastian Ramacher wrote:
> On 2016-07-24 14:19:36, Sebastian Ramacher wrote:
> > On 2016-07-22 13:27:09, Faidon Liambotis wrote:
> > > On Fri, Jul
On Sun, Jul 24, 2016 at 02:53:57PM +0200, Sebastian Ramacher wrote:
> On 2016-07-24 14:19:36, Sebastian Ramacher wrote:
> > Thank you for the info. Could you please let us know the version of libva1
> > and
> > i965-va-driver that you have installed?
>
> … and the versions of all other libva1-* p
On Fri, Jul 22, 2016 at 10:21:05AM +0200, Sebastian Ramacher wrote:
> Unfortunately I am unable to reproduce the issue. Since there are some
> accounts
> of random crashes when building ffmpeg with tree vectorization enabled, I've
> uploaded 7:3.1.1-3 with vectorization disabled. Could you please
Package: libavcodec57
Version: 7:3.1.1-2
Severity: grave
I ran Debian testing on my desktop. Since about a day ago, pidgin
started crashing unexpectedly. After a little bit of debugging, I found
that it reproducibly crashes when trying to play sounds. Going a step
further, I made the test case as
severity 829701 minor
thanks
On Wed, Jul 06, 2016 at 12:21:36PM +0200, Thorsten Glaser wrote:
> > Are there any other discussions about this where others agree with your
> > interpretation about this? #760306 is still waiting for a comment from
> > the ftp masters.
>
> Barring a comment from ftpm
Markus,
On Sat, Apr 30, 2016 at 11:28:53PM +0200, Markus Koschany wrote:
> > fretsonfire depends on the fonts-mgopen font which has been requested to
> > eb removed. (#819026). Please switch to a different font.
>
> providing patches or filing bug reports before requesting package
> removals are
Package: python-ctypeslib
Version: 0.0.0+svn20100125-5
Severity: grave
Hi,
gccxml since 0.9.0+git20140716-5 (dated Aug 7th, 2015) has been replaced
with a wrapper against CastXML. The wrapper is not fully compatible with
gccxml, which breaks most common invocations of h2xml (e.g. it's missing
the
reopen 765577 !
found 765577 215-14
thanks
On Mon, Mar 30, 2015 at 06:06:47AM +0200, Marco d'Itri wrote:
> I see that we have independently devised the same fix, I am attaching
> a test case and a more refined version of your patch.
I tried Jessie RC3 today and immediately found that the fix is,
Hi Martin,
On Fri, Mar 27, 2015 at 04:40:25PM +0100, Martin Pitt wrote:
> > If so, a mere "ipsec stop" after that should be able to crash
> > systemd.
>
> Not that, it just marks the unit as stopped but keeps the processes
> running. But killing the two daemons manually makes the cgroup empty
> a
Package: systemd
Version: 215-12
Severity: critical
I've managed to reproducibly crash systemd:
# grep systemd /var/log/syslog | tail -3
Mar 26 01:02:15 curium systemd[1]: Assertion 'path' failed at
../src/shared/cgroup-util.c:913, function cg_is_empty_recursive(). Aborting.
Mar 26 01:02:15 cur
Package: strongswan-starter
Version: 5.2.1-5
Severity: grave
strongswan-starter currently ships:
- /etc/init.d/ipsec
- /lib/systemd/system/strongswan.service
With the latter containing Alias=ipsec.service and also calling the
ipsec binary with --nofork as an (implicit) Type=simple unit. This is
On Wed, Mar 18, 2015 at 06:52:14PM +0100, Michael Biebl wrote:
> I'm with Marco here. Before adding any workarounds, we need to
> understand what the underlying problem is. Otherwise we are adding cruft
> which nobody understands anymore a few years from now.
>
> Since I can't reproduce the issue
reopen 775795
thanks
On 02/01/15 01:03, Gaudenz Steinlin wrote:
I created a patch to use /usr/sbin/service as suggested earlier in this
report to start/stop/status/restart services on Debian. I'm a bit
reluctant to just NMU puppet and would prefer if one of the maintainers
and/or Faidon could ha
Package: puppet
Version: 3.7.2-1
Severity: serious
Hi,
Puppet has an abstraction concept called "provider" for its types. The
Service type, one of puppet's basic types, is implemented by multiple
different providers, depending on the underlying init system. There is
the "init" provider, which i
reassign 775638 geoip-database 20141027-1
retitle 775638 IPv6 database is corrupt
severity 775638 grave
thanks
Hi,
thanks
On Sun, Jan 18, 2015 at 01:44:44AM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in jessie (in a jessie chroot, not a
> sid chroot), your package failed to b
Package: mate-session-manager
Version: 1.8.1-5
Severity: serious
Hi,
Since upstream commit[1] 8a20baf39f781184d6126e0947e9fd4d9a115fab,
mate-session-manager spawns gnome-keyring-daemon, with no option to turn
it off, or pass arguments to it (such as --components).
While this is bad in itself, it
Dear apt maintainers,
On Thu, Dec 11, 2014 at 01:35:27AM +0100, David Kalnischkies wrote:
> Attached is a patch which hopefully does exactly this. It is against
> experimental, but that shouldn't matter (expect for the testcase
> I think). I have run it on Linux amd64 (and armel) hardware as well
imilarly to gnome-shell's behavior.
+- 14_no_fade_on_user_switch.patch from Ubuntu, as to not fade on screen
+ lock. Prevents leaking of the screen contents on resume from suspend.
+
+ -- Faidon Liambotis Sat, 13 Dec 2014 11:32:25 +0200
+
gnome-screensaver (3.6.1-2) unstable; urgency=med
On Wed, Dec 03, 2014 at 06:18:45PM -, Dmitry Shachnev wrote:
> Please do not forget that the whole gnome-flashback (source) package fixes
> a lot of problems with gnome-panel. If we remove src:gnome-flashback from
> testing, that will leave gnome-panel users without:
>
> - Wallpaper;
> - Mouse
On Wed, Dec 03, 2014 at 04:28:33PM -, Dmitry Shachnev wrote:
> Control: tags -1 +moreinfo
>
> On Wed, 3 Dec 2014 16:46:40 +0200, Faidon Liambotis wrote:
> > I don't think that a desktop session with no (option for) volume,
> > battery/power or network management cont
reassign 734822 gnome-flashback 3.10.0-1
severity 734822 serious
thanks
On Fri, Jan 10, 2014 at 03:51:56AM +0100, Christoph Anton Mitterer wrote:
> A while since ago, NM applet didn't anymore start with GNOME classic
> (this was already before 3.8 and gnome-session-flashback)... but since
> then,
Package: gnome-flashback
Version: 3.8.1-7
Severity: grave
Hi,
First of all, there's a number of severity: normal/important bugs
reported against the gnome-ssession-fallback package that mention
keyboard shortcuts issues (#727047, #730831, #731245, #731418, #727046,
#730096). My investigation show
On Wed, Jun 26, 2013 at 10:50:20PM +0200, Jonas Meurer wrote:
as the subject already mentions, DRBD 8.3 userland in jessie/testing is
incompatible with DRBD 8.4 kernel modules from the 3.9 linux package.
DRBD kernel modules are at 8.4 branch in upstream linux kernel since
kernel release 3.8.
Ubu
Package: asterisk
Version: 1:11.5.1~dfsg-2
Severity: serious
I was surprised and initially happy to see Asterisk 11 uploaded into
sid. My happiness quickly diminished when I saw that the upload contains
the embedded pjproject as-is, despite this issue having been flagged for
months now and being
Package: rddmarc
Version: 1.1.3-1
Severity: grave
$ grep connect /usr/bin/dmarcfail
db = MySQLdb.connect(user='dmarc',passwd='xxx',db='dmarc', use_unicode=True)
$ grep -A 1 connect /usr/bin/rddmarc
my $dbh = DBI->connect("DBI:mysql:database=dmarc",
"xxx", "xxx")
severity 711872 minor
thanks
On Mon, Jun 10, 2013 at 03:43:37PM +0100, Alexander Clouter wrote:
The tests fail to start as the 'gdnsd' user does not exist on a fresh
system at build time (might be worth changing the tests to use the
'nobody' user? patch enclosed):
This is actually the case o
Package: git-buildpackage
Version: 0.6.0~git20130506
Severity: serious
Hi,
Building a package with overlay=True fails with the following backtrace:
Traceback (most recent call last):
File "/usr/bin/git-buildpackage", line 5, in
sys.exit(main(sys.argv))
File "/usr/lib/python2.
On Fri, May 10, 2013 at 10:23:04AM -0400, Jon Bernard wrote:
This is a bug report against liburcu/0.7.4-1 but you seem to have closed
it in an ltt-control upload. If it wasn't a liburcu bug in the first
place, you should have reassigned the bug before closing it; if it is a
liburcu bug OTOH, you
On Thu, Apr 11, 2013 at 03:47:19PM -0400, Jon Bernard wrote:
> > Additionally, since upstream is clearly supporting selected
> > architectures and falling back to #error for unsupported ones, your
> > package should properly mark those supported ones in the Architecture
> > field instead of relying
1 - 100 of 206 matches
Mail list logo
