Thank you very much for the patch.
Applied it, it looks fine.
Hello dear Paul and all Release Team!
>Can you at least please comment on this bug? Do you recognize it? Can
>you reproduce it (I would guess not, seems like this would make lxde
>nearly useless for everybody)? *If* lxde is nearly useless for
>everybody, I'd like to know, then I think we
>You can test it by installing the version from unstable.
It is not in unstable yet, see
https://packages.debian.org/search?keywords=libssl-dev
and
https://tracker.debian.org/pkg/openssl
control: tags -1 - bookworm sid + bookworm-ignore experimental
Could you explain, please, how this issue is an RC bug if sid contains
version 1.1.1o and 3.0 version is only in experimental? And how should I
do and test required changes if said version is not in sid at all?
Thank you very much for finding this. I just tried to make lxpanel-dev to
be 'Multi-Arch: same' but apparently I was wrong and it should be marked
'Multi-Arch: no' instead, leaving its dependency on lxpanel as it used to
be.
>I've prepared an NMU for lxtask (versioned as 0.1.9-1.1) and uploaded
>it to DELAYED/14. Please feel free to tell me if I should cancel it.
Thank you very much. There is an issue with GIT which we tried to fix
and failed. It was what delayed the actual fix for so long. After all it
was decided
Hi,
>Personally, I was surprised that LXDE was kept in Debian; I thought it
>was going to be replaced by LXQt. Are you planning to keep LXDE in
>Bullseye?
Actually LXDE and LXQt are just similar but pretty different desktop
environments and not every LXDE user may feel happy to be forced to use
Hello Andreas!
You have written on Sunday, 26 January, at 10:36:
>Control: severity -1 serious
>Hello,
>On Sun, Jan 28, 2018 at 08:27:57PM +0200, Andriy Grytsenko wrote:
>> Thank you for this notice. I will try to find a way and handle this
>> situation ASAP, it's real
Yes, Yahoo unfortunately ended free service at January 3.
New API requires registering the application and has unknown restrictions
which probably will lead the weather plugin to DoS situation, because if
developer registers API to get a key then that limitation will be applied
to each user of
Hello Adrian!
Thank you very much for pointing on this issue, will work on it ASAP.
Thank you for a NMU but that isn't needed, I think 1.3.0 will come pretty
soon where this issue is fixed.
Cheers!
Actually this is a bug in gtk-doc, see
https://bugzilla.gnome.org/show_bug.cgi?id=783420
It should be fixed by gtk-doc upstream if I read that bugreport right,
although it's workarounded by libfm upstream, see the latest commit
b072ee0400432d72fdf86ba9fed74a7e0ec11ec1 in the libfm upstream GIT.
Thank you very much!
Package: pcmanfm
Version: 1.2.5-2
Version: 1.2.3-1.1
Severity: serious
Tags: upstream security
The socket placed in /tmp is predictable and public-writable. Therefore
if one user placed a symlink to another socket instead of socket for
another user then said another user will either be unable to
Package: libmenu-cache3
Version: 1.0.2-2
Severity: serious
Tags: upstream security
The socket placed in /tmp is predictable and public-writable. Therefore
if one user placed a symlink to another socket instead of socket for
another use then said another user will either be unable to get menu, or
Hello!
>the two bug https://bugs.debian.org/858567 (just fixed in a very
>recent upload) and https://bugs.debian.org/857795 are not present in
>the initial upload of the according package version, only in the
>recent BinNMUs. So I wonder if these issues might stem from a recent
>build
Thank you for reminding on that, will look at it ASAP.
control: tags -1 + jessie moreinfo
Have you tried to install version 0.9.3-1 from Stretch? I've not managed
to reproduce your issue yet but I suspect it is fixed in newer versions,
and it might be some configuration issue from MATE desktop as well.
control: reassign -1 lxde-common 0.99.2-2
Thank you very much for reporting this. It appears due to repackaging of
lxsession package, so lxde-common misses two dependencies now. Will fix
it ASAP.
Ah, forget about previous message, found the problem.
Thank you for a report, fixed version will come soon.
>Package: openbox-lxde-session
>Version: 0.99.2-1
>Severity: grave
>When trying to install openbox-lxde-session package, dpkg fails with an error
>message:
> dpkg: error processing archive .../openbox-lxde-session_0.99.2-1_all.deb
> (--unpack):
> trying to overwrite
Package: openbox-kde-session
Version: 3.6.1-3
Severity: grave
After installing package openbox-kde-session one would expect to have a
GUI session available. Although it isn't. It fails on running the file
that executes session:
root@ag:/# openbox-kde-session
/usr/bin/openbox-kde-session: 20:
Well, while your point is right, removal of system-tools-backends will
broke LXDE usability because there is no other alternative package to
manage users - other known users management tools are integrated into
GNOME and KDE, and gnome-system-tools is only standalone package which
can be used in
control: severity -1 important
This bug, while afecting usability of the system, still does not make it
completely unusable, therefore, according to the BTS policy, should have
another severity, see https://www.debian.org/Bugs/Developer#severities as
a reference.
And since there was no solution
Package: libobrender29
Version: 3.6.0-1
Severity: grave
This is actually an upstream bug but it is a problem because it makes any
of packages dependent on libobrender29 broken completely, any application
compiled using libobrender29 version 3.5.x will crash using libobrender29
version 3.6.0-1.
Package: lxappearance-obconf
Version: 0.2.2-2
Severity: grave
The latest package in sid is built against openbox library libobrender29
version 3.6.0-1 with broken ABI (see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788520)
and therefore version 0.2.2-2 of lxappearance-obconf should never
Hello!
Piotr Martycz has written on Sunday, 17 May, at 15:55:
This is a debian packaging problem unrelated to upstream.
Our unit file [1] assumes lxdm is going to acquire a
org.freedesktop.DisplayManager name on a dbus which is not the case,
apparently, therefore service is restarted after
control: forwarded -1 https://sourceforge.net/p/lxde/bugs/743/
Thank you very much for reporting this. The upstream author will be
notified about the problem and hopefully it will be fixed soon.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe.
Thank you for the patch, I hope it works and fixes the problem.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Thank you very much, everyone, for all that detailed comments.
I remove that Alias statement and hope that fixes the problem.
Reopen the ticket if something is still wrong, please.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
30 matches
Mail list logo
