-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2025-07-22 at 08:43 +0200, Jochen Sprickerhof wrote:
> > as already said, that's not an option for us. There's no plan to retire
> > strongswan-charon (and strongswan-starter) packages.
>
> Why would you drop the alternate dependency in Fork
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2025-07-21 at 18:55 +0200, Jochen Sprickerhof wrote:
> > So, it seems to work on Bookworm -> Trixie but won't that mean we'll have
> > the
> > same problem again (for those installs) in Trixie -> Forky if I remove the
> > alternate dependency
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2025-07-21 at 18:42 +0200, Yves-Alexis Perez wrote:
> > If both should be in trixie I would say:
> >
> > Package: strongswan
> > Depends: charon-systemd | strongswan-charon, strongswan-swanctl
>
> Ah, good poi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2025-07-21 at 18:40 +0200, Jochen Sprickerhof wrote:
> > strongswan-charon is the "historical" (legacy) charon daemon, which is
> > beeing
> > phased out in favor of charon-systemd. That's why we updated the
> > dependency
> > for the strongs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2025-07-21 at 18:12 +0200, Jochen Sprickerhof wrote:
> > I have no idea why apt doesn't want to 'change charon-systemd:amd64'.
>
> The problem is that bookworm apt prefers keeping strongswan-charon
> installed over other solutions. This is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2025-07-20 at 12:25 +0200, Yves-Alexis Perez wrote:
> In any case, help would be appreciated on how to interpret apt output and
> how
> to make it accept the removal of strongswan-charon for upgrading the
> strongswan metapackage
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: tag -1 help
On Sat, 2025-07-19 at 20:25 +0200, Lucas Nussbaum wrote:
> > > MWE:
> > > PKG=strongswan; mmdebstrap --chrooted-customize-hook="set -x ; apt -y
> > > install $PKG && sed -e s/bookworm/trixie/ -i /etc/apt/sources.list &&
> > > a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2025-07-19 at 11:51 +0200, Lucas Nussbaum wrote:
> The following fails:
> - In bookworm, install strongswan
> - dist-upgrade to trixie
> I would expect strongswan to be upgraded, but it is not. It remains at the
> bookworm version.
> 'apt ins
On Tue, Feb 25, 2025 at 11:13:40AM +0100, Yves-Alexis Perez wrote:
> On Tue, Feb 25, 2025 at 10:03:37AM +, Luca Boccassi wrote:
> > On Tue, 25 Feb 2025 at 09:57, Yves-Alexis Perez wrote:
> > Would you be able to provide a patch that fixes them?
>
> Unfortunately no, but
On Tue, Feb 25, 2025 at 11:26:58AM +0100, Yves-Alexis Perez wrote:
> On Tue, Feb 25, 2025 at 11:13:40AM +0100, Yves-Alexis Perez wrote:
> > On Tue, Feb 25, 2025 at 10:03:37AM +, Luca Boccassi wrote:
> > > On Tue, 25 Feb 2025 at 09:57, Yves-Alexis Perez wrote:
> >
On Tue, Feb 25, 2025 at 10:03:37AM +, Luca Boccassi wrote:
> On Tue, 25 Feb 2025 at 09:57, Yves-Alexis Perez wrote:
> >
> > Hi,
> >
> > it seems that the efitools NMU actually broke the package (at least for
> > my use case).
> >
> > efitools 1.
Hi,
it seems that the efitools NMU actually broke the package (at least for
my use case).
efitools 1.9.2-3 contains multiple .efi binaries in /u/l/*/efitools, for
example on amd64
(https://packages.debian.org/bookworm/amd64/efitools/filelist):
/usr/lib/efitools/x86_64-linux-gnu/HashTool.efi
/usr
Package: adduser
Version: 3.139
Severity: grave
Hi Marc,
adduser 3.139 uses Encode.pm but doesn't depend on the package providing
it (libperl5.40 is optional). It's likely the package is still installed
on most standard installations but it won't be on minimal installs
I noticed the bug on a piu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2025-02-10 at 11:47 +, mag...@autistici.org wrote:
> Hi Yves-Alexis, hi Helmut!
>
> @Helmut: I'm writing to you too because Yves-Alexis raised
> the severity of the bug to serious and Yves-Alexis is asking
> below if this does apply to s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: reassign -1 x11-common
control: forcemerge 1094494 -1
On Thu, 2025-02-06 at 09:22 +0100, frax1...@axnet.nu wrote:
> Package: lightdm
> Version: 1.32.0-6+b1
> Severity: grave
> Justification: user security hole
> X-Debbugs-Cc: f...@axnet.nu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: severity -1 important
Control: tag -1 unreproducible moreinfo
On Mon, 2024-02-26 at 17:52 +, ael wrote:
> Package: xfce4-power-manager
> Version: 4.18.3-2
> Severity: normal
>
> Since the recent update on testing, several things are br
port
> > which was filed against the tumbler package:
> >
> > #1083022: tumbler fails to coinstall: trying to overwrite shared
> > '/usr/lib/systemd/user/tumblerd.service'
> > Debian Xfce Maintainers
> > It has been closed by Debian FTP Masters
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: forwarded -1
https://gitlab.xfce.org/panel-plugins/xfce4-notes-plugin/-/issues/84
On Wed, 2024-07-03 at 12:48 +, Matthias Klose wrote:
> Common build failures are new warnings resulting in build failures with
> -Werror turned on, or new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: severity -1 important
control: tag - unreproducible moreinfo
On Mon, 2024-05-13 at 18:28 +0200, Philippe Caillaud wrote:
> Dear Maintainer,
>
> I use mousepad almost each day for small text editing ; since a few days
> (maybe
> 2 or 3), mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2024-04-19 at 00:01 +0100, Peter Green wrote:
> Thanks, upstream has now accepted a patch that takes a slightly different
> approach to fixing the issue.
>
> https://github.com/canonical/lightdm/issues/352
Yes I saw. That's why I think this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2024-04-13 at 16:11 +0100, Peter Green wrote:
> > Hi, thanks for the patch. It looks a bit strong though, undefining stuff
> > like
> > that unconditionally. Do you have pointers to the Ubuntu bug or something?
> > I've looked at upstream com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2024-04-05 at 11:25 +0500, Andrey Rakhmatullin wrote:
> > Hi, thanks for the patch. It looks a bit strong though, undefining stuff
> > like
> > that unconditionally. Do you have pointers to the Ubuntu bug or something?
> I haven't checked the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2024-04-01 at 00:37 +0500, Andrey Rakhmatullin wrote:
> I assume the following patch from Ubuntu fixes this:
>
> --- a/tests/src/libsystem.c
> +++ b/tests/src/libsystem.c
> @@ -1,6 +1,9 @@
> #define _GNU_SOURCE
> #define __USE_GNU
>
> +#u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: severity -1 important
On Tue, 2024-03-26 at 12:25 +0100, Matthias Klose wrote:
> Package: src:ifuse
> Version: 1.1.4~git20181007.3b00243-1
> Severity: serious
> Tags: sid trixie ftbfs patch
>
> ifuse ftbfs from source, not finding the libp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2024-02-05 at 00:28 -0800, Steve Langasek wrote:
> Well, to clarify, the patch I sent was against 4.18 in unstable; but it
> applied cleanly to 4.19 in experimental (no new sonames in experimental vs
> unstable), so it's been uploaded there.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2024-02-04 at 11:14 +, Steve Langasek wrote:
>
> If you have any concerns about this patch, please reach out ASAP. Although
> this package will be uploaded to experimental immediately, there will be a
> period of several days before we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 1 Jan 2024 11:31:38 +0100 Paul Gevers wrote:
> Source: xfce4-power-manager
> Version: 4.18.2-1
> Severity: serious
> Control: close -1 4.18.3-1
> Tags: sid trixie
> User: release.debian@packages.debian.org
> Usertags: out-of-sync
>
> De
no effect.
>
> Maybe forwarding this to nvidia-driver should get some hints about this
Yes, feel free to do it and report back any progress.
I'm lowering the bug severity as well so it does migrate.
Regards,
--
Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2023-06-21 at 09:40 -0300, Adilson dos Santos Dantas wrote:
> These messages are when I stop lightdm.
Ah ok.
> >
> >
> > Also is there something peculiar about your hardware (Nvidia/AMD GPU for
> > example?) or software (specific configura
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2023-06-21 at 01:59 +, solneman33 wrote:
> I downgraded to xkb-data=2.35.1-1 lightdm=1.26.0-8 from testing repo and
> reinstalled xserver-xorg and xinit. That resolved the issue for me on both
> machines.
>
> I've never reported a bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2023-06-20 at 20:37 -0300, Adilson dos Santos Dantas wrote:
> I tried to use 1.32 again and it only
> generates /var/log/lightdm/lightdm.log. It doesn't generate seat0-
> greeter.log and x-0.lo. From the log attached below, one difference is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2023-06-20 at 12:45 +0200, Carlos Laviola wrote:
> Package: lightdm
> Followup-For: Bug #1038611
>
> Can't reproduce, starts up just fine for me.
>
> Could you perhaps include the logs from `/var/log/lightdm/´?
Hi Adilson,
I'm running 1.3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2023-05-03 at 16:10 +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package ships (or creates)
> a broken symlink.
>
> 0m9.1s ERROR: FAIL: Broken symlinks:
> /usr/lib/x86_64-linux-gnu/libmousepad.so -> libmousep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2023-02-26 at 05:11 +0300, Arthur Demchenkov wrote:
> Package: libxfconf-0-dev
> Version: 4.18.0-1
> Severity: serious
> Tags: ftbfs patch
> Justification: fails to build from source (but built successfully in the
> past)
>
> Dear Maintainer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2023-01-04 at 15:12 +0300, Сергей Фёдоров wrote:
> parole 4.16.0-2 when running in the terminal emulator outputs :
> free(): invalid pointer
> Emergency stop
>
> parole 4.16.0-1 is up and running.
Yes indeed, so we have an issue with -1 whi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2022-12-20 at 18:38 +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > make[1]: Entering directory '/<>'
> > dh_missing --fail-missing -X .la
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2022-11-02 at 19:14 +0100, Paul Gevers wrote:
> https://sources.debian.org/src/strongswan/5.9.8-1/debian/tests/control/
>
> line 2 says that the *first* two tests Depends on strongswan-scepclient.
> That means that autopkgtests tries to ins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2022-11-02 at 19:14 +0100, Paul Gevers wrote:
> Hi Yves-Alexis,
>
> On 02-11-2022 17:27, Yves-Alexis Perez wrote:
> > I'm not sure why the test is failing then and what I should have done
> > differently. Could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2022-10-31 at 21:01 +0100, Paul Gevers wrote:
> With a recent upload of strongswan the autopkgtest of strongswan fails
> in testing when that autopkgtest is run with the binary packages of
> strongswan from unstable. It passes when run with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: reassign -1 libical3
Control: affects -1 orage
On Fri, 14 Oct 2022 16:07:45 +0200 Slavko wrote:
> Hi,
>
> On Fri, 14 Oct 2022 15:50:29 +0200 Slavko wrote:
>
> > upgrade libical3:amd64 3.0.14-1+b1 3.0.15-2
>
> after i submit initial rep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2022-06-17 at 17:08 +0200, Moritz Mühlenhoff wrote:
> The following vulnerability was published for exo.
>
> CVE-2022-32278[0]:
> > XFCE 4.16 allows attackers to execute arbitrary code because xdg-open
> > can execute a .desktop file on an a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2021-10-24 at 00:51 +0800, Marc Gallet wrote:
> Am I to understand that the expected path forward with what is supposed to be
> a minor update offered on oldstable is that everyone shall dump their
> databases,
> delete the data folder, rest
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2021-10-22 at 15:22 +0200, Ondrej Zary wrote:
> With 10.3.29 running, I've dumped all databases (mysqldump --all-databases -
> p >mysql.dump), then dropped all databases, stopped mariadb and deleted
> /var/lib/mysql/ib*.
> Then restarted mari
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2021-10-14 at 19:38 +0200, Ondrej Zary wrote:
> MDEV-15912: Remove traces of insert_undo
>
> Let us simply refuse an upgrade from earlier versions if the
> upgrade procedure was not followed. This simplifies the purge,
> comm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2021-10-22 at 02:13 +0800, Marc Gallet wrote:
>
> Am I correct to assume this issue is still relevant for buster and that
> for now, I should simply defer the upgrade (marking the packages to be
> held back) and simply wait for this bug to b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2021-10-14 at 00:03 -0700, Otto Kekäläinen wrote:
> Right. Here is for Buster:
>
> https://salsa.debian.org/mariadb-team/mariadb-10.3/-/commit/8ccf2240960cbb609cedfeb269df22d43ccbba21
> https://salsa.debian.org/mariadb-team/mariadb-10.3/-/pi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2021-10-13 at 19:06 -0700, Otto Kekäläinen wrote:
> I added this patch to the packaging in
> https://salsa.debian.org/mariadb-team/mariadb-10.5/-/commit/2a8f83531a2ff22a31c61b8bef28dabf77b25b78
> and once the CI completes (if it runs without
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2021-10-12 at 21:58 +0200, Ondrej Zary wrote:
> > One thing you could also try is to start the server with 10.3.29 and
> > ensure that you have a clean shutdown (SET GLOBAL
> > innodb_fast_shutdown=0; SHUTDOWN) and only after that start with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2021-10-11 at 11:27 +0200, Jan Korbel wrote:
> Maybe this: https://bugs.freebsd.org/bugzilla//show_bug.cgi?id=257728
If I read the bug correctly, it points to
https://jira.mariadb.org/projects/MDEV/issues/MDEV-26537 and the commit
https://gi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: subscribe -1
On Sun, 10 Oct 2021 16:13:29 +0200 Ondrej Zary wrote:
> Package: mariadb-server
> Version: 1:10.3.31-0+deb10u1
> Severity: grave
> Justification: causes non-serious data loss
>
> Dear Maintainer,
> upgrading mariadb-server fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: severity -1 normal
On Tue, 2021-08-17 at 22:05 +0200, truetec...@tutanota.com wrote:
> Hello,
>
> When compiled with --enable-upower-glib, xfce4-power-manager doesn't seem to
> re-enable laptop displays after suspending the system. And, fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2021-05-13 at 20:58 +0200, Salvatore Bonaccorso wrote:
> Thank you! Btw, I sitll would try to check if release team would
> accept 4.16.8 itself. Note I'm as well not sure about if this will
> need a DSA or can be fixed via point release, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2021-05-11 at 21:45 +0200, Salvatore Bonaccorso wrote:
> The following vulnerability was published for thunar.
>
> CVE-2021-32563[0]:
> > An issue was discovered in Thunar before 4.16.7 and 4.17.x before
> > 4.17.2. When called with a regula
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2021-02-04 at 14:43 +0200, Adrian Bunk wrote:
> Yves-Alexis, do you have any objections to closing this bug now?
Yes. I have xfce4-screensaver (4.16) running on a Debian sid install and it
still happens every once in a while that the desktop
-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 orag
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2020-12-12 at 21:31 +0100, Aurelien Jarno wrote:
> > If you need more information don't hesitate to ask (I guess you don't
> > have an iDevice to plug for testing).
>
> Indeed, I do not have such a device. As a first step, it would be nice
>
On Sat, 2020-12-12 at 21:31 +0100, Aurelien Jarno wrote:
>
> Indeed, I do not have such a device. As a first step, it would be nice
> if you can set the environment variable LIBUSB_DEBUG=99 and run lsusb.
> That should give us an idea why the device is ignored.
Here are two logs (with .22 an .24)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: tag -1 pending
On Mon, 2020-11-02 at 21:07 +0100, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'sid' to 'experimental'.
> It installed fine in 'sid', then the upgrade to 'experimental'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: forcemerge 870641 -1
On Sun, 2020-10-18 at 10:23 +0200, franck wrote:
> Package: xfce4-power-manager
> Version: 1.6.1-1
> Severity: grave
>
> Dear Maintainer,
>
> [ Bug description ]
> Bug happens when the screen auto-locks due to user in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2020-03-20 at 09:06 +0100, Yves-Alexis Perez wrote:
> On Thu, 2020-03-19 at 18:39 +0100, Andreas Henriksson wrote:
> > There doesn't seem to have been any movement since your comment on the
> > upstream bug report. The x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2020-03-19 at 18:39 +0100, Andreas Henriksson wrote:
> There doesn't seem to have been any movement since your comment on the
> upstream bug report. The xfce4-notes-plugin is now the only remaining
> package in unstable that still depends on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2020-03-02 at 11:49 -0700, Sean Whitton wrote:
> > Hi Jonas, I got that issue earlier, and to be honest I kind of side with
> > Fabrice here, and I find it bit sad Buster was released with that kind of
> > behavior.
>
> It's definitely undes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2020-02-13 at 13:11 +0100, Andreas Henriksson wrote:
> Control: severity -1 serious
>
> Hello XFCE Maintainers,
>
> I'm bumping the severity of this bug report because the libindicators
> package in RC buggy and likely not going to make it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2020-02-09 at 21:02 +0100, Helmut Grohne wrote:
> strongswan fails to build from source in unstable, because it misses a
> build dependency on libiptc-dev. The library was formerly pulled by
> "something" and no longer is. The build now fails
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: severity -1 important
On Tue, 2019-12-24 at 16:16 +0100, Jérôme Bouat wrote:
> It seems a directory is missing :
> ---
> Could not enumerate user data directory /var/lib/lightdm/data: Error opening
> directory '/var/lib/lightdm/data': No su
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-09-22 at 11:04 +0200, Yves-Alexis Perez wrote:
> Obviously there might be people using python-plist and python-imobiledevice
> directly in python scripts and they'll have to migrate them to python3,
> which
> is not per
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-11-17 at 11:00 +, Mike Gabriel wrote:
> If you plan to drop maintenance sooner or later anyway, then please
> state that asap (packages are in deferred-15 from today again), so
> that I can change the uploads and make these bugs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-11-13 at 20:58 +, Mike Gabriel wrote:
> One last question: For the themes you maintain, is it ok if I provide
> the "Provides: any-murrine-theme" patches (as MRs or pushed commits)
> and possibly even NMU them for those murrine-l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-11-12 at 12:09 +0100, Mike Gabriel wrote:
>
> As I haven't had any reply nor statement nor veto nor anything from any
> of you on the above, here is what is going to happen, if noone interacts...
Hi Mike,
I'm unfortunately quite busy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-10-06 at 07:08 -0400, Jeremy Bicha wrote:
> Control: severity -1 serious
>
> The Debian GNOME team would like to remove libunique from Debian.
> Therefore, I'm bumping the severity of this bug to serious.
>
> Please see the master bug
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-09-29 at 07:10 -0400, Jeremy Bicha wrote:
> Control: severity -1 serious
>
> I propose that we remove albatross-gtk-theme from Unstable & Bullseye.
> A GTK theme that doesn't work with GTK3 isn't very helpful any more.
>
> https://gith
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2019-09-17 at 13:29 -0300, Lisandro Damián Nicanor Pérez Meyer wrote:
> I'm terribly sorry if we are being pushy here, it is indeed with no
> bad faith and we definitely don't want to annoy anyone. And yes, we
> are targeting at removing qt4
intended, but could
you please slow down a bit?
—
Yves-Alexis
> On 17 Sep 2019, at 18:05, Lisandro Damián Nicanor Pérez Meyer
> wrote:
>
> Hi!
>
>> On Tue, 17 Sep 2019 at 12:49, Yves-Alexis Perez wrote:
>>
>> Please don’t, I already told Moritz I’ll handle it w
Please don’t, I already told Moritz I’ll handle it when I have time.
—
Yves-Alexis
> On 17 Sep 2019, at 16:46, Lisandro Damián Nicanor Pérez Meyer
> wrote:
>
> Hi Yves-Alexis!
>
> lightdm is now one of the three packages holding qt4 in testing. Would
> it be possible for you to apply the pat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2019-09-15 at 23:26 +0200, Moritz Mühlenhoff wrote:
> > Attached is a patch which drops Qt4 support. It's only used by src:razorqt,
> > which is already RC-buggy anyway and which will be removed soon along with
> > Qt4.
>
> razorqt also got
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2019-08-29 at 17:31 +0700, Theppitak Karoonboonyanan wrote:
> Package: xfwm4
> Version: 4.14.0-1
> Severity: serious
> Justification: Policy 3.5
>
> Dear Maintainer,
>
> xfwm4 fails to start:
>
> $ xfwm4
> xfwm4: error while loading shared
Source: xfce4-sntray-plugin
Version: 0.4.11-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
xfce4-sntray-plugin doesn't seem to build from source anymore. We
noticed that as part of the xfconf transition (part of the Xfce 4.14
rel
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: severity -1 important
On Mon, 25 Jun 2018 16:16:49 +0200 Andreas Beckmann wrote:
> Source: xfce4-session
> Version: 4.13.0-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the
past)
>
> Hi,
>
>
On Sat, 2019-08-17 at 07:53 +0200, Helmut Grohne wrote:
> xfce4-power-manager fails to build from source for every architecture on
> the buildds. A typical failure is:
Hi Helmut, thanks for the report. It seems that xfpm requires libxfe4ui 4.13
although that's not in configure.ac.
Xfce 4.14 uploa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: reopen -1
On Sun, 2019-07-14 at 00:44 +0200, Adam Borowski wrote:
> But, in this case, I am very excited that you have a replacement for
> something I find to be hopelessly buggy -- and the replacement seems
> near-perfect. Thus, if you sw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2019-07-11 at 10:34 +0200, Adam Borowski wrote:
> So... is there any reason to not let xfce4-screensaver go to Bullseye?
> Any day that a human being suffers from light-locker is a bad day.
Hi Adam,
could you please refrain from such statem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Control: forcemerge -1 868087
On Thu, 2019-06-27 at 12:02 -0400, Onyuksel, Cem wrote:
> I'd like to point out that this bug has a similar effect on nvidia graphics
> as well, as pointed out in the bug report
> https://bugs.debian.org/cgi-bin/bugrepo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: affects -1 xserver-xorg-core
On Sat, 2019-06-22 at 17:34 -0400, John Franklin wrote:
> I've been suffering from this bug in a clean Buster system, too. A
> solution noted in another bug tracker is to explicitly tell X.org to
> use the inte
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-06-03 at 12:59 -0700, Russ Allbery wrote:
> Ah, good call. I was also seeing other problems with the Intel driver in
> combination with light-locker where the monitor resolution would be set to
> some incorrect value after restore from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2019-06-03 at 21:55 +0200, Yves-Alexis Perez wrote:
> I noted Andreas raised the severity, but I hope someone has an idea how to fix
> that because I don't.
Also, since it was posted on -devel, I guess there's a bit of e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-05-31 at 18:32 -0700, Russ Allbery wrote:
> This appears to be a bug in light-locker specifically, which is the
> default screen lock program with XFCE with lightdm. See, for instance:
>
> https://github.com/the-cavalry/light-locker/is
Package: src:wpa
Severity: grave
Tags: security
Justification: user security hole
Hi,
multiple vulnerabilities were discovered in wpa:
CVE-2019-9494 [cache attack against SAE]
CVE-2019-9495 [cache attack against EAP-pwd]
CVE-2019-9496 [SAE confirm missing state validation in hostapd/AP]
CVE-2019
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: severity -1 important
control: tag -1 unreproducible
On Wed, 2019-01-30 at 15:37 +1100, Dmitry Smirnov wrote:
> In Cinnamon xfce4-notes does not work any more: it starts without showing
> its
> window or tray icon and uses ~55% CPU continu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2019-01-04 at 08:39 +0900, Hideki Yamane wrote:
> Hi,
>
> With Bugs search "Cleaner view", I've found those bugs are not closed
> in unstable but are done in experimental.
Hi, I am well aware of these, thanks.
> Do you have a plan to pu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2018-12-16 at 12:06 +0200, Adrian Bunk wrote:
> Package: parl-desktop
> Version: 1.9.16
> Severity: serious
>
> The following packages have unmet dependencies:
> parl-desktop : Depends: xfce4-linelight-plugin but it is not installable
Ouch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, 2018-11-05 at 13:08 +0100, Pierre Chifflier wrote:
> Package: iptables
> Version: 1.8.1-2
> Severity: grave
> Tags: security
> Justification: breaks rules, inserts pass-all rules
> X-Debbugs-Cc: t...@security.debian.org,
> secure-testing-t..
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: severity -1 normal
On Tue, 2018-10-09 at 03:04 +0200, Jules Bernable wrote:
> Package: lightdm
> Version: 1.26.0-3
> Severity: grave
> Justification: renders package unusable
This is not a correct severity, the system is not unusable.
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
control: severity -1 important
control: retitle -1 "verve-focus program missing from package"
On Mon, 2018-09-17 at 20:33 +, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
>
> > severity 898950 serious
>
>
close 906489 1.26.0-1
thanks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, 2018-08-12 at 16:38 -0400, Jeremy Bicha wrote:
> Yvez, the Evolution bug was closed upstream. Should we close the bug
> in Debian too?
>
> https://bugzilla.gnome.org/796135
Yeah I guess so, it only adds noise. The status is not entirely cle
close 862436
thanks
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2018-03-10 at 10:20 +0100, Stuart Pook wrote:
> On 10/03/18 10:10, Yves-Alexis Perez wrote:
> > In any case, I really can't reproduce here, and you still didn't indicate
> > what
> > you changed to make it
close 899849 4.13.0-1
thanks
close 899773
fixed 899773 0.12.0-1
thanks
close 899744 4.13.3-1
thanks
1 - 100 of 779 matches
Mail list logo
