Package: nextcloud-desktop
Version: 3.16.2-1
Severity: wishlist
Tags: upstream
Dear Maintainer,
please update nextcloud-desktop to 3.16.4, which was released on April 28th.
Judging by the available milestones on GitHub this may be the last release from
the 3.16 branch and brings only bugfixes co
Package: zabbix-agent2
Version: 1:7.0.9+dfsg-1
Severity: normal
Dear Maintainer,
thank you for handling my last bug report regarding the PID location.
Unfortunately upstream also violates the FHS in regard to the placement of
sockets.
By default it sets ControlSocket to /tmp/agent.sock and Plug
Package: zabbix-agent2
Version: 1:7.0.6+dfsg-1+b1
Severity: normal
Dear Maintainer,
upstream stores its PID file in /tmp which is cared for by
config_debianisation.patch for zabbix-agent but not in the dedicated
config_agent2.patch for zabbix-agent2.
Please extend config_agent2.patch so that it
Hi,
On Sat, 15 May 2021 11:55:15 +0200 Elrond
wrote:
> Package: autopostgresqlbackup
> Version: 1.1-1
> Severity: wishlist
>
>
> Hi,
>
> Most backups on Debian go to /var/backups it seems.
> Could you modify autopostgresqlbackup to also put its
> backups there? Maybe /var/backups/autopostgresq
Package: prosody-modules
Version: 0.0~hg20240511.d3a72777f149+dfsg-1
Severity: wishlist
Dear Maintainers,
you have included mod_report_forward and mod_watch_spam_reports in prosody-
modules which both depend on mod_spam_reporting but which isn't included in
prosody-modules itself yet. So please i
Dear maintainers,
On Thu, 04 May 2023 16:23:10 +0200 Alan Krempler wrote:
> Package: php-smbclient
> Version: 1.0.6-8
> Severity: grave
> Justification: renders package unusable
>
> php-smbclient does not work with samba versions 4.17.5 and above:
> https://github.com/eduardok/libsmbclient-php/i
Hello everyone,
On Thu, 2023-08-31 at 08:55 +0200, Michael Biebl wrote:
> >
> > What we found so far is, that the AppArmor policy of lxc breaks any
> > systemd service using PrivateNetwork=yes or PrivateIPC=yes when
> > being
> > run under lxc (running under bookworm using the bookworm kernel).
Package: haproxy-log-analysis
Version: 2.0~b0-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
directly after installation of haproxy-log-analysis the postinst script throws
errors:
Selecting previously unselected package python3-haproxy-log-analysis.
Preparing to unpac
Package: prosody-modules
Version: 0.0~hg20230223.556bf57d6417+dfsg-1~bpo11+1
Severity: wishlist
Hello,
I would like to propose the inclusion of mod_net_proxy.
In case prosody cannot be deployed on a host directly facing the internet,
mod_net_proxy comes in very handy and it works very well.
Tha
Hi everyone,
> Hi William,
>
> On So 22 Mai 2022 22:15:17 CEST, Gacquer William wrote:
>
> > Hello
> >
> > A few months later, the bug persists.
> > Sadly I can't contribute but I pray every minute for the bug to be
> > fixed :)
> >
> > Best regards
> > William Gacquer
>
> I assume that xRDP
Dear Maintainer,
are you willing to accept this patch?
@Dan: Is your patch or at least the bug itself reported to upstream?
Thank you and kind regards,
Daniel
smime.p7s
Description: S/MIME cryptographic signature
Package: nextcloud-desktop
Version: 2.5.1-3+deb10u1
Severity: wishlist
It would be nice to let users of buster enjoy the improvements since 2.6
Thank you and kind regards,
Dan
-- System Information:
Debian Release: 10.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500,
Hi Martin,
am I right in assuming that this issue is blocking the updating of
newer dino-im releases after this commit?
https://github.com/dino/dino/commit/7012023d5997287b1ed300e03a4c5b91eb6c9c39
An update of libsignal-protocol-c before the buster freeze would be
highly appreciated.
Kind regard
I'd really love to have this package in buster.
But this means that it must be in testing before 2019-02-12. So not
much time left. The package doesn't have to be in perfect shape by then
but afterwards the soft freeze will be active!
Kind regards,
Dan
smime.p7s
Description: S/MIME cryptographi
Hi Victor,
I can confirm that the patch works! mod_auth_ldap gets loaded and users
can authenticate, but only if the option ldap_server consists of a
single hostname or IP. A space separated list of hostnames/IPs doesn't
work anymore.
Using a space separated list of e.g. three hostnames leads to t
Hi Martin,
> I don't know anything about Lua, but I forwarded your comment to
> the prosody MUC
thank you.
> and the wise people there suggest to remove
> three lines from the lua-ldap sources:
>
> --- a/src/lualdap.c
> +++ b/src/lualdap.c
> @@ -1090,9 +1090,6 @@ int luaopen_lualdap (lua_State
Thank you Victor, for uploading the new version of lua-ldap!
On my test system I upgraded prosody and lua-ldap to the new version
in backports. Unfortunately, mod_auth_ldap doesn't work anymore:
Dec 19 17:58:17 modulemanager error Error initializing module 'auth_ldap'
on '': Attempt to set
Hi Martin,
On Fri, 23 Nov 2018 14:24:52 +0100 "W. Martin Borgert" wrote:
> any progress in finding a new or the right upstream?
the more or less official looking successor repo on LuaRocks seems to be:
https://luarocks.org/modules/devurandom/lualdap
Which points to: https://github.com/lualdap/l
Package: prosody-modules
Version: 0.0~hg20170929.c53cc1ae4788+dfsg-3
Severity: wishlist
Hi!
At the moment only mod_auth_ldap2 is included in the package but development of
mod_auth_ldap has been more active recently and actually has a larger
featureset than mod_auth_ldap2, e.g. the possibility to
Package: prosody-modules
Version: 0.0~hg20170929.c53cc1ae4788+dfsg-3
Severity: wishlist
Hi!
mod_csi_battery_saver offers a more comprehensive featureset than
mod_throttle_presence and mod_filter_chatstates with timestamping, properly
handled carbon copies, support for handling encrypted messages
Package: prosody
Version: 0.10.0-1
Severity: wishlist
It would be great if stretch would receive a backport of prosody 0.10 from
testing :)
-- System Information:
Debian Release: 9.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Hi,
> From the attached log (scroll to the bottom...):
>
> Preparing to unpack .../prosody_0.10~hg745e0a783055-3_amd64.deb ...
> invoke-rc.d: could not determine current runlevel
> invoke-rc.d: policy-rc.d denied execution of stop.
> Unpacking prosody (0.10~hg745e0a783055-3) over (0.9.12-
Package: prosody-modules
Version: 0.0~hg20170719.cd828b1cb5b9+dfsg
Severity: normal
prosody-modules is currently packaged with mod_carbons (within the folder
/usr/lib/prosody/modules/mod_carbons).
Prosody 0.10 comes already shipped with mod_carbons. This didn't lead yet to
upgrading file conflicts
> Because this module needs a patched prosody 0.9, it does not
> make sense to add it to Debian before prosody 0.10 is released
> and packaged.
Actually, the patch was already backported to prosody 0.9, see:
https://hg.prosody.im/0.9/rev/ef22c17cc24d
So it has already been part of prosody since
> Because this module needs a patched prosody 0.9, it does not
> make sense to add it to Debian before prosody 0.10 is released
> and packaged.
Actually, the patch was already backported to prosody 0.9, see:
https://hg.prosody.im/0.9/rev/ef22c17cc24d
So it has already been part of prosody since
Package: prosody-modules
Version: 0.0~hg20160813.65d9093525ca+dfsg-3
Severity: wishlist
Tags: upstream
Dear Maintainer,
please consider updating prosody-modules to the latest upstream changeset as
there have been some fixes and additions in the modules that you provide in
your package, e.g. withi
Hi all,
On Thu, 22 Sep 2016 18:33:35 +0200 Axel Beckert wrote:
>
> Do I read that right, the chances for nextCloud in Debian are rather
> low while the chances to get ownCloud back in Debian raised due to the
> obnoxious upstream developers left together with nextCloud fork and
> the remaining d
Package: wnpp
Severity: wishlist
* Package name: libolm
Version : 2.0.0
Upstream Author : Richard van der Hoff
* URL : https://matrix.org/git/olm/
* License : ASL 2.0
Programming Lang: C, C++11
Description : An implementation of the Double Ratchet crypt
Victor, thank you!
Will you also upload 0.9.11 to jessie-backports, once it hits testing?
Best wishes,
Dan
smime.p7s
Description: S/MIME cryptographic signature
Hi Matthew,
> With my upstream hat on, I'd prefer not having package name collisions
> with our upstream repository. Our repository provides automated
> nightly builds, and when people install 'prosody-0.10' that's what
> they believe they are getting.
>
> A prosody-0.10 package in Debian would r
On Wed, 2 Nov 2016 18:19:04 +0100 Victor Seva wrote:
> On 11/02/2016 05:47 PM, W. Martin Borgert wrote:
> > Package: prosody
> > Version: 0.9.10-1
> > Severity: wishlist
> >
> > https://hg.prosody.im/0.10 contains the next planned release of
> > prosody. It would be nice to have it already in Deb
Hi Antonio,
> The help I need is
>
> 1) confirmation that this does still happen with the packages in jessie
yes, I can confirm that this still happens with the packages in jessie.
> 2) identifying exactly which commit on the upstream source, between 2.5
> and 3.0, fixes it.
It seems the fix w
Hi Antonio,
> > can we still expect an update for stable that fixes this?
>
> we could, but I need help as I explained earlier in this bug report.
unfortunatly I am not quite sure about the specifics of the help needed.
Do you mean testing the packages in your repo at
https://people.debian.org
Hi,
can we still expect an update for stable that fixes this?
Or do we have to wait for a backport of the version in stretch (if that
is in any way feasible)?
Kind regards,
Dan
Package: prosody-modules
Version: 0.0~hg20150813.12ac88940fe3-2
Severity: wishlist
I really appreciate the current selection of modules, but I think it
should by
default be expanded with at least those modules, that are tagged as
'stable' by
upstream.
The current list can be seen here:
https://mo
Package: shibboleth-sp2
Severity: wishlist
Tags: experimental
Hi there,
with Shibboleth 2.5 just released and wheezy in freeze state, I would like to
request packaging of version 2.5 for experimental.
I know that this has already been announced on pkg-shibboleth-devel [0], so
this report just se
Hi!
The latest vpnc packages uploaded to sid support hybrid auth
out-of-the-box (using GnuTLS libs). network-manager-vpnc should be
patched accordingly.
Greetings,
Dan
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
Am Sonntag, den 04.01.2009, 17:46 + schrieb Neil Williams:
> Package: splashy
> tag 505270 + unreproducible
> tag 505270 + moreinfo
> thanks
>
> This bug appears to only affect non-standard kernels not using
> initramfs *and* using /usr on a different partition.
>
wrong.
My configuration:
Am Freitag, den 02.01.2009, 15:10 +1300 schrieb Jochen:
> I can confirm this bug on 2 of my systems. However for me
> the /etc/directfbrc does not fix the error.
>
> Cheers
> Jochen
>
>
>
>
I can confirm this bug as well, even with 0.3.13-1 the error persists.
The /etc/directfbrc hack doesn't
Hello,
as pointed out in the links of the bug opener, this is a _security_
issue. Therefore I suggest raising the severity from normal to RC.
Best regards,
Da
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
A similar bug in splashy has been recently fixed, see: bug #486400
Is the fix related to a possible fix in usplash?
regards,
Dan
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
I can confirm this. The only difference is that i am using Gnome.
Best regards,
Dan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Subject: linux-image-2.6.24-1-686: confirming bug #469189 with QSI DVDRW
SDW-042
Followup-For: Bug #469189
Package: linux-image-2.6.24-1-686
Version: 2.6.24-4
hi,
i can confirm this bug on my Fujitsu Siemens Amilo A-7600 with the
drive
QSI DVDRW SDW-042. However, when i add vga=788 to the boot pa
43 matches
Mail list logo
