Bug#1071092: systemd-resolved: Ping reply about 15 seconds after instead of near instantaneously

2024-05-25 Thread Patrick ZAJDA

On Tue, 14 May 2024 10:42:21 +0100 Luca Boccassi  wrote:
> On Tue, 14 May 2024 09:13:20 +0200 Patrick ZAJDA 
> wrote:
> > Package: systemd-resolved
> > Version: 254.5-1~bpo12+3
> > Severity: normal
> > Tags: ipv6 upstream
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > Dear Maintainer,
> >
> > I use Network-Manager as my network manager but this also applies for
> other E.G. same occurs with Systemd Network.
> > Until now, when sending a ping to a domain which resolves to an IPv6
> address, it takes a very short delay to have an output returned.
> > But with SystemD-resolved, resolution takes about 15 seconds.
> > This issue should have been fixed upstream [1] but I don't precisely
> know which SystemD version solves it nor if it is stable.
> > It makes ping less efficient with this long delay before having a
> reply.
> >
> > It occurs with the Backport version as specified but also with the
> version in Bookworm (252.22-1~deb12u1).
> >
> > Could it be possible to backport the fix to Bookworm?
> > For bookworm-backports, is it planned to release a new version when
> available?
>
> There will be no more backports updates.
>
> --

About Bookworm, do you have an idea of the moment the version with the 
fix will be available at least on bookworm-proposed-update?


Kind regards,

--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1071092: systemd-resolved: Ping reply about 15 seconds after instead of near instantaneously

2024-05-14 Thread Patrick ZAJDA
Package: systemd-resolved
Version: 254.5-1~bpo12+3
Severity: normal
Tags: ipv6 upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

I use Network-Manager as my network manager but this also applies for other 
E.G. same occurs with Systemd Network.
Until now, when sending a ping to a domain which resolves to an IPv6 address, 
it takes a very short delay to have an output returned.
But with SystemD-resolved, resolution takes about 15 seconds.
This issue should have been fixed upstream [1] but I don't precisely know which 
SystemD version solves it nor if it is stable.
It makes ping less efficient with this long delay before having a reply.

It occurs with the Backport version as specified but also with the version in 
Bookworm (252.22-1~deb12u1).

Could it be possible to backport the fix to Bookworm?
For bookworm-backports, is it planned to release a new version when available?

I personnaly switched back from Systemd-resolve to only use Network Manager and 
have not migrated any server (using SystemD Network)
because even if it looks only Ping is conserned, this behavior is not desirable
and makes Ping not unusable but near when not using it with an IPv4 directly 
IMO.

[1]: https://github.com/systemd/systemd/issues/28166

Best regards,

Patrick

- -- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-21-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages systemd-resolved depends on:
ii  dbus [default-dbus-system-bus]  1.14.10-1~deb12u1
ii  dbus-broker [dbus-system-bus]   36-1~bpo12+1
ii  libc6   2.36-9+deb12u7
ii  libssl3 3.0.11-1~deb12u2
ii  libsystemd-shared   254.5-1~bpo12+3
ii  systemd 254.5-1~bpo12+3

Versions of packages systemd-resolved recommends:
ii  libnss-myhostname  254.5-1~bpo12+3
pn  libnss-resolve 

Versions of packages systemd-resolved suggests:
ii  polkitd  122-3

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEF6TZmSao+HhR4xlgnUrTW+onPcoFAmZDDwQACgkQnUrTW+on
Pco5mw//ee7yo3MbDky4WeVdrq3IgIpTWd//WUquEnxwOKCcf+u/u85U6vuQXYC2
xRWn/w4kpcMT/l/fl9ABwluJgi4GL0pb+rRCsU0cfmpO3S9DjJBoeCrM88bJmjOU
1TXYklNo9jlU9anYb/Bc0oQNKDZrGDrTRfg6R/BLyZOBS40fhI4YG74cu+vcg7cq
tEs20N6yWHWQ8CeD5tBObV37ED0O3Sudpjp9Pdlx2hMMeee1f1xqsBljyHNOdk9b
EMJXUxcmKbsltrlteryGM+mnkMgbORwAWrSRdWMHpwNvrqGnjbyyzP+lHAEPF0Cl
z+jGvFBuhV29ZLKxCdPswmze+e752YSB5AIoiSH1wTPPopqaCR3YPc/kQfumh66f
CjP1PE/SZ9mtL2OL1psqsFBty3MyiIjiv5G5V8s8505+nlO77Cvj8BlMNkL/3x+o
VIqztGEH3vCb5whPoIvS9qHMDTiWjSL2WyuFlOc5uYnBqXBSHLzoBqjRPQvFSiH9
o7A2E8BPvy6RHFHQpu/m/Zj5TnRs3tK7gwoHnrPiXFqFin3B2XsirAQGsWsmHqOt
Ewd0/L2bfcV6iyNfsPmX8qsxrXVbFIq/zcMpKCfQlGccvMglhI0Yj/f7zC4sHfGI
nBFieYjbxGGgsygaKXrXAZE+9qDNveWrYIJfxnhYGHUxOOLJH1Q=
=Kz1h
-END PGP SIGNATURE-



Bug#1064592: meson: Python modules installed in python3 instead of python3.x

2024-02-24 Thread Patrick ZAJDA
Package: meson
Version: 1.0.1-5
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

When using Meson in a Python project, files are placed in 
/usr/local/lib/python3 instead of /usr/local/lib/python3.x.
Same when building a package, /usr/lib/python3 instead of /usr/lib/python3.x.

This can cause some issue when including some other modules, for example if 
building Orca from source and Speech Dispatcher from master.
The wrong version of Speech Dispatcher will be used.

Other distributions place Python files in /usr/local/lib/python3.x.
Using python3 path place files in a path which is not included in PYTHONPATH.
In PYTHONPATH, there is no python3 path included in paths from /usr/local.

Best regards,

Patrick

- -- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-18-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages meson depends on:
ii  ninja-build1.11.1-1
ii  python33.11.2-1+b1
ii  python3-pkg-resources  66.1.1-1
ii  python3-setuptools 66.1.1-1

Versions of packages meson recommends:
ii  dpkg-dev  1.21.22

meson suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEF6TZmSao+HhR4xlgnUrTW+onPcoFAmXaOXAACgkQnUrTW+on
PcoFExAAwPJf7X6MMcECzzGbH57LBGBtlYOAdMtkZJ7YavBvj8hXB0BmJm93hDZb
2qglLPNlcnS6LUZ5s/iffbboyNw/50t2RjnGwqJD1BTuafJ+ZslDIRLGGukWfjc7
c9jaRBUDlbFz2xVXiEJKHYfokiSJvVU/uxB62CkNqKXBbZ+dqYxLlqo/lEi0EVg9
Vh4gZdI20r50I4zu6s+/3kAOJoLMG5eGGffuvKQCumWxjksGSQ2EYlnsT/hlt/i1
YeX3kvgPBuO4dlICMULAqdy0qYXg9AAp3iE1n5vAmPIY5Vfez8n0rTG5uJZZJWly
m4QgOr+1+0LBJJ7H8ofs1l4buXV58zzCD6m76MnJ8BKlh/ZB8/+KVuhB561TJd1I
CSDiHDJSp2PeR/iHpoUcmrM5KeenObpINkKnVpIgXYamnpjOo4unmc2r70OwzBqK
pPlWzFomcBSZOCjxhFNu0s3KE+us2SkR/k54N3HLlRauiemwAexwHlF4rLaK7Nwr
+vd038cKt/MSk1ecPYYiCBlxGF1IxojzZTbcKNIyqZBTloTDxmCH9WHapILin97Z
pCpay+w9XAJMkkXrnvynpIRDu951mKgqP0oQYknNtzCy91DQery1Mghko2vKN22n
ZxIogu+6frlKCCnoCxPNP9o5YBRL0ANGGEERVvPNsSIvWp0zBpg=
=Lezi
-END PGP SIGNATURE-



Bug#1062932: Confirm, Bookworm still broken

2024-02-13 Thread Patrick ZAJDA



Le 13/02/2024 à 08:55, Kate Korsaro a écrit :

Hi guys,
tried an update this morning and it still broken for Bookworm.
It is not available in bookworm-updates yet, only in 
bookworm-proposed-updates then should be available in bookworm-updates 
later.

See Bug#1063675 for more information.
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1063675: nvidia-graphics-drivers 525.147.05-6~deb12u1 flagged for acceptance

2024-02-13 Thread Patrick ZAJDA



Le 13/02/2024 à 00:58, Jonathan Wiltshire a écrit :

It will be released in bookworm at the next point release, and all being
well earlier than that via bookworm-updates.

Testing of the packages through proposed-updates before then is
appreciated, as always.



Thanks.

FYI I've tested with proposed-updates (with some pining to only update 
NVIDIA related) and was able to update to 6.1.0-18 then reboot successfully.


--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1063675: nvidia-graphics-drivers 525.147.05-6~deb12u1 flagged for acceptance

2024-02-12 Thread Patrick ZAJDA



Le 12/02/2024 à 18:56, Jonathan Wiltshire a écrit :

package release.debian.org
tags 1063675 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: nvidia-graphics-drivers
Version: 525.147.05-6~deb12u1

Explanation: restore compatibility with newer Linux kernel builds; take over 
packages from nvidia-graphics-drivers-tesla; add new nvidia-suspend-common 
package

So the update won't be available in bookworm-update and we must add 
proposed-update to our sources to be able to update to latest kernel?

Or do I miss something?

Best regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1062932: nvidia-graphics-drivers: Version 525.147.05-6 not available in stable, dkms fails with kernel 6.1.0-18

2024-02-10 Thread Patrick ZAJDA
Source: nvidia-graphics-drivers
Version: 525.147.05-4~deb12u1
Followup-For: Bug #1062932

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

Kernel version 6.1.0-18 is now available on stable but it looks the version 
which fix DKMS issue has only been uploaded to unstable.
Consequence is DKMS fails to build NVIDIA modules when updating kernel in 
Bookworm.

ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 
'__rcu_read_lock'
ERROR: modpost: GPL-incompatible module nvidia.ko uses GPL-only symbol 
'__rcu_read_unlock'

Best regards,

Patrick


- -- System Information:
Debian Release: 12.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-17-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEF6TZmSao+HhR4xlgnUrTW+onPcoFAmXHj2IACgkQnUrTW+on
PcoLcxAAoP6H+4J3P/gbnzhPtKqyPtTWKXJQiz66ihT4ZQkY+BM29nuZfMW6d7yI
uIYjhybL3ArG+Or1FFfiG8OVPEvPKYlK7VQsXH6jWY//J+1YVEnOPUTJKP7AGcL/
tuL1ONTMwk715UY0q5W2CDtnrkYsIcQ7pxUd4DKUw8Kja7ZAhWcyJ7M09jTa6HAv
63aVI41Lw2JrRFmOdtIH9Hv4sYpXegpdsh6ZSmKmlahfKqMmcX++zqQDHJzPDtVS
3lwZ/ZEMhd0JDTWrtrshb64y/TztNkl9QLG1fOnG9m35rWpeQjVwz+VTDe88yKDQ
w/swAzXjxp1kygHqLAhZErN5eXBxtnPOZuKR2VUccnmXoEwpUuEhm/rwggo+zueQ
lxPHcPWfI1Vjwuhq9k16y2IguDMrnG5w+D15MnpK1qt5I8ZpKPFE9Qm3CDClTpZG
7kfwhQbbZG2h9LuZHGakrkB1wjpnuPCpIPdWoaYRAFcuZe5ITjP0egpg0xv3f6zg
RyYDKoltJyl4gq56gEykflqKnmHGN2SE6S/hL/AdPOcEIkV5G6P3Sa18Wx2S567D
uBJ9NwPCFylVFHpgQXBZyEiHwHt4q0WOdIoCyS43M04PjsxfK3Rwv9iIRq+tp+pz
PlqPLQU1jdJm43MhF5BEIZ8414L4loprN3z092uvnbKJL1Qs4ts=
=lBJv
-END PGP SIGNATURE-



Bug#1063511: RFS: pidgin-skype/20240122+gitab786a3+dfsg-2~bpo12+1 -- Skype plugin for libpurple messengers

2024-02-08 Thread Patrick ZAJDA
Package: sponsorship-requests
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear mentors,

I am looking for a sponsor for my package "pidgin-skype":

 * Package name : pidgin-skype
   Version  : 20240122+gitab786a3+dfsg-2~bpo12+1
   Upstream contact : Eion Robb 
 * URL  : https://github.com/EionRobb/skype4pidgin
 * License  : GPL-3+
 * Vcs  : https://salsa.debian.org/debian/pidgin-skype
   Section  : net

The source builds the following binary packages:

  pidgin-skype-common - Skype plugin for libpurple messengers (common files)
  pidgin-skype - Skype plugin for libpurple messengers (Pidgin-specific files)
  empathy-skype - Skype plugin for libpurple messengers (Empathy-specific files)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/pidgin-skype/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/p/pidgin-skype/pidgin-skype_20240122+gitab786a3+dfsg-2~bpo12+1.dsc

Changes since the last upload:

 pidgin-skype (20240122+gitab786a3+dfsg-2~bpo12+1) bookworm-backports; 
urgency=medium
 .
   * Rebuild for bookworm-backports.

Regards,
- -- 
  Patrick Zajda

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEF6TZmSao+HhR4xlgnUrTW+onPcoFAmXFzgwACgkQnUrTW+on
PcpPXQ//fUrHkyaaOuyMXACWJ2gGBBPCKUnUGPpxjyJ/RQY2mlIiBBcc7z5afHVV
V9vxyTo2K0IMF6A9NW0lHC31LrO3ZZSG4Nfko9agripHECjF7hGvABKnzcZLNOpB
xshtZ1TwCZqik28yWIK8IP+o+lGpF1Bp15L9XuQ32jWTHCq968yWc75jdUDzq755
qXs8/mp3uXvOA5QMm48uulHFRVgiNdY0yONPKex6+C0V3jWxWqBe1KnS+VrKwHhT
0lWeRe/4bKsIB5ZkjN+IcDtjzmSEpwLEVZaN0hnSgvekowKnYB/1UTeiVfNBI4n/
OXqDnOhi7H36s0pKPjPFQvla+F9HyVe3dUsvLftCQ1V7L+MKckYkn94zKq2GveUj
Ej4IsQZCF+ojusioF8FlfUU4kJm4/cPeoxDOEWZwdHB8wGJf3VymcslxNz3uba1B
0cFuom38F/Dz335FAxybQisSytYHYV1jPIdT7Nb1CgHqV0DIXhvOOKw61ny6aWR/
de0XXi99yOqQiBYt0usbhacwExHu+TEzV4xFJ/bm4NYqpVSny4qlPwIxMQdc62fm
VtCUZTP+krwh4RUk1R27rcCc0MBJ8D2Z+9KRaFnznvGGyOFkXKtKU5P1pcZVGCwi
O6+dyP+zWBRDI5WLHxOiLwqEMy+lK91BCpifBcqD2aypYD/Lalc=
=/25V
-END PGP SIGNATURE-



Bug#1062812: RFS: pidgin-skype/20240122+gitab786a3+dfsg-2 -- Skype plugin for libpurple messengers

2024-02-03 Thread Patrick ZAJDA
Package: sponsorship-requests
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear mentors,

I am looking for a sponsor for my package "pidgin-skype":

 * Package name : pidgin-skype
   Version  : 20240122+gitab786a3+dfsg-2
   Upstream contact : Eion Robb 
 * URL  : https://github.com/EionRobb/skype4pidgin
 * License  : GPL-3+
 * Vcs  : https://salsa.debian.org/debian/pidgin-skype
   Section  : net

The source builds the following binary packages:

  pidgin-skype-common - Skype plugin for libpurple messengers (common files)
  pidgin-skype - Skype plugin for libpurple messengers (Pidgin-specific files)
  empathy-skype - Skype plugin for libpurple messengers (Empathy-specific files)

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/pidgin-skype/

Alternatively, you can download the package with 'dget' using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/p/pidgin-skype/pidgin-skype_20240122+gitab786a3+dfsg-2.dsc

Changes since the last upload:

 pidgin-skype (20240122+gitab786a3+dfsg-2) unstable; urgency=medium
 .
   * debian/control: update VCS URLs

Regards,
- -- 
  Patrick Zajda

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEF6TZmSao+HhR4xlgnUrTW+onPcoFAmW+RdoACgkQnUrTW+on
PcrCyRAArnI8ynoFCzsn8tAksdoeo3iXnzvZuplxxw7XY4Mt6zRPWm9R5R8pGWib
fryPgXwqM59k43xBUwK/sEchNxPRrDmgFQGO30rVad3orfNknQdPNp8OIRyvoxFl
Rk1V6F/d838WN4F03r7uQZon73xa/8AQpldU1feLZMQqWHs+7LKfbAUPrxYGFI7U
etY2plX4OVLqhzKDGOfBYDnT0mLgI2Kr3UA/mSlF7Z8FPzinbxzSeQOs7ltVeDp3
aX8p154kmesjQRJp/FT3Y3Sg7mdJfeiZMZX5Nn5xVLEsB3ip3dngiWfCYyhURkwf
TsrjAFCrktRb3MqNejiyvbqZaFVT3NKbaxb2/kx4HdV1sEkFKj2dVeKSkqmBY2UM
ADlkf2hwTsdT3UNcTMXTliUnA5OeGDccJg96ysggzSQ3NtoUdj6jKEoxr2pZQ4tz
4scuFiNb9/DZ4dbAu3R/oolIiIqWdMP/fCzLUAwlW8i43OchCbb0TiF/BHSBJj7x
DrA/4E5rJxqTs5qIgZBu4/LTbAst0/qaaxKibWWTQHuau4F2k6sh42U6aENMO45o
XhEiBKvn5UgSflU32ciMKHKQqR49xzbiA6E+unE3WWs8REbaAF0HKpZeN76pBFL/
cctgE6cTwTX+qtEry2Hezsx91uJ+yFGMbcn1+QgduCQnjqRacvU=
=tU/I
-END PGP SIGNATURE-



Bug#1061079: RFS pidgin-skype

2024-02-02 Thread Patrick ZAJDA

Hello,

Le 30/01/2024 à 19:20, Gianfranco Costamagna a écrit :

Hello,
please switch VCS fields to the new location
https://salsa.debian.org/debian/pidgin-skype/-/blob/master/debian/control?ref_type=heads


Done, in both repositories.


And then just delete the old repository once the new version is uploaded in sid.

There is no rush, if you plan some upload in the near future.


It is really random, for upstream modification.

But it looks I could have to do something for auto-glib2.0 
<https://release.debian.org/transitions/html/auto-glib2.0.html> transition.

Which I don't really understand yet.

I plan to make a backport for Bookworm. Do you think I should:
- Backport this version even if VCS fields are not up to date?
- Make a new version with update VCS fields and backport it as soon as 
it is in testing?
- Wait again for the auto-glib2.0 
<https://release.debian.org/transitions/html/auto-glib2.0.html> 
transition. to make all needed modifications, create a version with also 
updated VCS fields and see what will happen for the backport?


Thanks,

Patrick


G.


Il martedì 30 gennaio 2024 alle ore 16:28:14 CET, Patrick ZAJDA 
 ha scritto:





Hello,

On Fri, 26 Jan 2024 18:36:02 +0100 Gianfranco Costamagna
 wrote:

Happily done, btw how do you feel about pushing your work somewhere

in Debian git repositories?

https://salsa.debian.org/debian/pidgin-skype might be a good place.

This way other people can help maintaining your package

I've just pushed all branches and tags to this repository and set CI.

What do you suggest me to do after knowing it is referenced in the
package meta-data?
Maintaining both repositories synced until there is a new version to
publish?

Thanks and best regards,



--
Patrick ZAJDA
<https://certification.nvaccess.org/>Logo certification NVDA expert 2022


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1061079: RFS pidgin-skype

2024-01-30 Thread Patrick ZAJDA

Hello,

On Fri, 26 Jan 2024 18:36:02 +0100 Gianfranco Costamagna 
 wrote:
> Happily done, btw how do you feel about pushing your work somewhere 
in Debian git repositories?

> https://salsa.debian.org/debian/pidgin-skype might be a good place.
>
> This way other people can help maintaining your package

I've just pushed all branches and tags to this repository and set CI.

What do you suggest me to do after knowing it is referenced in the 
package meta-data?
Maintaining both repositories synced until there is a new version to 
publish?


Thanks and best regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1061777: ITP: aresponses -- Asyncio response mocking. Similar to the responses library used for 'requests'

2024-01-29 Thread Patrick ZAJDA
Package: wnpp
Severity: wishlist
Owner: Patrick ZAJDA 
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

* Package name: aresponses
  Version : 3.0.0
  Upstream Contact: Bryce Drennan 
* URL : https://github.com/aresponses/aresponses
* License : MIT/Copyright (c) 2016 CircleUp Network, Inc
  Programming Lang: Python
  Description : Asyncio response mocking. Similar to the responses library 
used for 'requests'

Aresponse is an asyncio testing server for mocking external services.
Features:
 - Fast mocks using actual network connections
 - allows mocking some types of network issues
 - use regular expression matching for domain, path, method, or body
 - works with https requests as well (by switching them to http requests)
 - works with callables

Compared to similar packages, documentation provides more instruction and usage 
is really easyer within less lines.
Flexibility is also right for this lib when needing to test connection using 
AIOHTTP and instructions are included in the documentation to use Aresmonse 
with aiohttp test framework.
I use it to test PySMSBoxNet [1].
[1]: https://github.com/Nardol/pysmsboxnet

I need a sponsor for this package, idealy I wish to maintain this package by 
being a member of the Python Team.

Best regards,

Patrick

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEF6TZmSao+HhR4xlgnUrTW+onPcoFAmW33BIACgkQnUrTW+on
PcqsGg/7BqDd9kDfIzP+Z0uhTVGhwT4I6s5JGq+8yVpXuH0YEVxzNId4bUtP+ZTG
58njDbxjIUC8MnZntbNpgkjHhXbXIUTJusxkMQMZpMIVW2FjYfnEWHywZXuhvAOR
aaFYV9OHnUARPg59/Q1YtDlBnja7sQkvMMGsGtbObBQbmINU3cUnO2h5//qPqaJZ
XzpwgFuhWuIef8Iz+Jce65eEz0xugQX5nE9jmM5XSUssQ/WJ6q24xVaCXsgDHUu5
kuqCo7byhjlDgVLNc0o9Aoeowih+aPLn1D1CQvIkdlT8jGPzXUg63O7d+Xy2VC/1
GTxNvQPk34PpctmfM6p3PiDFS+T/3ivwmUbSA45tC7SWSFolhihu+GV8hg+Rx3w5
6xvV3TjoCVxSX3FP5/73/SzYA1Y4ifgaL1fYQVL8i8YUFqhxlaJkc6Pc4x6RTlyw
Zt35IF0lc7FPmY+jQCcCk7oBhWGr4gjWqbmWjtGi4O+b3rSVgi4WgRRy6drb7u8J
i2a3+ZeWhZ4fdAlxJFq9eRlA7oEdoqM7IVRlsjVIrSrhrf0ektx71lPMRK4/fIKP
ZSYedj2uf7ikbXLf5A1UHN8VXNqx3ZNtDe1qXDXVY7XZQ/y/buLg3fuSRarhJIvp
Z4cMzD5ntB+ev+UhKgREy0CDpF05IQZPg2hf2vG11JAV6VUqslw=
=yU7j
-END PGP SIGNATURE-



Bug#1061079: RFS pidgin-skype

2024-01-25 Thread Patrick ZAJDA

Hi,

I changed the version to 20240122+gitab786a3+dfsg-1 because the patch I 
added has been applied upstream and hardening work now.

Changelog is the same and this version is uploaded on Mentors.

Best regards,

--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1061079: RFS pidgin-skype

2024-01-18 Thread Patrick ZAJDA

Hello,

I fixed some lintian info and migrated debug symbols to new standard, 
they are now in pidgin-skybe-common-dbgsym instead of pidgin-skype-dbg


Best regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#856736: ITA: pidgin-skype -- Skype plugin for libpurple messengers (common files)

2024-01-17 Thread Patrick ZAJDA

On Tue, 16 Jan 2024 10:35:20 +0100 Patrick ZAJDA  wrote:
> Currently I have created a repository on Salsa [1] where I will push
> updates step by step.
>
> [1]: https://gitlab.com/Nardol/pidgin-skype

Oops, it is now really on Salsa:

https://salsa.debian.org/Nardol/pidgin-skype

Patrick


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1061079: RFS: pidgin-skype/20230710+git5daf79d+dfsg-1 [ITA] -- Skype plugin for libpurple messengers (Pidgin-specific files)

2024-01-17 Thread Patrick ZAJDA

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "pidgin-skype":

* Package name : pidgin-skype
Version : 20230710+git5daf79d+dfsg-1
Upstream contact : Eion Robb 
* URL : https://github.com/EionRobb/skype4pidgin
* License : GPL-3+
* Vcs : https://salsa.debian.org/Nardol/pidgin-skype
Section : net

The source builds the following binary packages:

pidgin-skype-common - Skype plugin for libpurple messengers (common files)
pidgin-skype - Skype plugin for libpurple messengers (Pidgin-specific files)
empathy-skype - Skype plugin for libpurple messengers (Empathy-specific 
files)

pidgin-skype-dbg - Skype plugin for libpurple messengers (debug symbols)

To access further information about this package, please visit the 
following URL:


https://mentors.debian.net/package/pidgin-skype/

Alternatively, you can download the package with 'dget' using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/p/pidgin-skype/pidgin-skype_20230710+git5daf79d+dfsg-1.dsc


Changes since the last upload:

pidgin-skype (20230710+git5daf79d+dfsg-1) unstable; urgency=medium
.
* New maintainer (Closes: #856736)
* Declare compliance with Debian Policy 4.6.2
* New upstream version
* Remove support for Skype and Skype DBus plugins
* Add SkypeWeb plugin (Closes: #788922)
* Use debian/watch to update from upstream source excluding icons
* Remove patches
* debian/controle:
- Move from contrib to main
- Adjust build dependencies
- Change descriptions, now only provide Skype web
* debian/*.links: update paths to icons
* debian/*.install: update paths to icons
* debian/rules:
- Adjust to new directory structure
- Fix custom-compression-in-debian-rules

Regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#856736: O: pidgin-skype -- Skype plugin for libpurple messengers (common files)

2024-01-16 Thread Patrick ZAJDA

Hi,

On Sat, 4 Mar 2017 14:57:52 +0100 Tobias Frost  wrote:
> Package: wnpp
> Severity: normal
>
> The current maintainer of pidgin-skype, Gabriele Giacone 
<1o5g4...@gmail.com>,

> is apparently not active anymore. Therefore, I orphan this package now.
>
> Maintaining a package requires time and skills. Please only adopt this
> package if you will have enough time and attention to work on it.
>

I am currently working on updating this package to latest standards then 
to use latest upstream version, which now only include skype web.
I have no time frame to give yet about when a version will be available 
to be uploaded on Mentor because there are a lot of changes to apply.


Currently I have created a repository on Salsa [1] where I will push 
updates step by step.


[1]: https://gitlab.com/Nardol/pidgin-skype

Best regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#788922:

2024-01-13 Thread Patrick ZAJDA

Hi,
On Wed, 28 Mar 2018 12:29:03 + (UTC) Jack Underwood 
 wrote:
> On Mon, 26 Jun 2017 16:03:56 +0200 Alex ARNAUD  
wrote:

> > I believe you could hijack the package due to the very long delay.
>
>
> This package has already been orphaned since 4 Mar 2017 see [1], do 
you still intend to adopt

> this package Vincent Bernat? Please say yes :).
>
> Best,
> Jack
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856736
>
>
If nobody is interested to adopt this packages and if this package has 
still interest to some people, I might plan to adopt it and will reply 
to #856736 if confirmed.


New upstream version does not requires Skype, moreover API is not 
supported anymore and this plugin now only support Skype Web.


Best regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1059029: RFS: harmony/0.7.2-1~bpo12+1 -- program and library for creating and managing Discord accounts

2023-12-19 Thread Patrick ZAJDA

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "harmony":

* Package name : harmony
Version : 0.7.2-1~bpo12+1
Upstream contact :
* URL : https://github.com/taylordotfish/harmony/
* License : GPL-3+
* Vcs :
Section : web

The source builds the following binary packages:

python3-harmony - program and library for creating and managing Discord 
accounts


To access further information about this package, please visit the 
following URL:


https://mentors.debian.net/package/harmony/

Alternatively, you can download the package with 'dget' using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/h/harmony/harmony_0.7.2-1~bpo12+1.dsc


Changes since the last upload:

harmony (0.7.2-1~bpo12+1) bookworm-backports; urgency=medium
.
* Rebuild for bookworm-backports.
.
harmony (0.7.2-1) unstable; urgency=medium
.
* New upstream release.
* New maintainer (closes: #1032369)
* Use tags to determine upstream version
* Declare compliance with Debian Policy 4.6.2, no changes needed.

Regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1058884: installation-reports: debian testing iso install in franch: Light-DM and mate desktop are in English

2023-12-17 Thread Patrick ZAJDA

Hi again,

I forgot to mention both installation were made in accessible mode, by 
pressing s then enter on boot.


Best regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057124: RFS: harmony/0.7.2-1 [ITA] -- program and library for creating and managing Discord accounts

2023-12-12 Thread Patrick ZAJDA

Hi,


Le 12/12/2023 à 07:57, Paul Wise a écrit :

* Suppress Lintian warning about man page
It is incorrect to suppress valid lintian warnings, instead you should
either ignore them or fix them, probably upstream in this case.


I removed the suppression of the lintian warning and sent the package again.
I plan to generate a manpage using help2man then suggest it upstream 
after some eventual modifications, I think it can wait for a next 
version seeing there are only --help and --debug in command line parameters.



While this package isn't possible to autopkgtest easily since it is for
a live proprietary service, you could add superficial testing that the
Python module can be imported; in the Source section of debian/control:

Testsuite: autopkgtest-pkg-python

Done in the last sent package of today.


These issues may be interesting to work on if you have spare time:

Upstream may like to modernise the Python packaging:

https://packaging.python.org/en/latest/tutorials/packaging-projects/

pycodestyle/pydocstyle/pyflakes3/pylint/vulture/ruff report some
(likely minor) code issues if you want to contribute fixes upstream.

Looks feasible, also for a next version to have all upstream or do you 
think all should be done for this version?


Best regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057124: RFS: harmony/0.7.2-1 [ITA] -- program and library for creating and managing Discord accounts

2023-12-04 Thread Patrick ZAJDA

Hello,

I missed to include the fix in debian/watch to check for upstream 
version, which was already documented in the changelog.

I re-uploaded the package to Mentors to fix my mistake.

Best regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1032369: O: harmony -- program and library for creating and managing Discord accounts

2023-11-29 Thread Patrick ZAJDA

Hi Pabs,

On Fri, 24 Nov 2023 09:45:24 +0800 Paul Wise  wrote:
> Patrick, since you recently adopted the Debian purple-discord package,
> perhaps you would be interested in adopting the harmony package too?
>

Yes I am, following to my previous message on this bug and your reply to 
the "private" mail I sent to you, I created RFS #1057124 to also adopt 
the Harmony package.


Best regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1032369: ITA: harmony -- program and library for creating and managing Discord accounts

2023-11-29 Thread Patrick ZAJDA

Hello,

After successfully taking over the maintenance of purple-discord, I have 
the intent to do the same for Harmony.


I've published a package on mentors and am going to create a RFS.

Best regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057124: RFS: harmony/0.7.2-1 [ITA] -- program and library for creating and managing Discord accounts

2023-11-29 Thread Patrick ZAJDA

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "harmony":

* Package name : harmony
Version : 0.7.2-1
Upstream contact :
* URL : https://github.com/taylordotfish/harmony/
* License : GPL-3+
* Vcs :
Section : web

The source builds the following binary packages:

python3-harmony - program and library for creating and managing Discord 
accounts


To access further information about this package, please visit the 
following URL:


https://mentors.debian.net/package/harmony/

Alternatively, you can download the package with 'dget' using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/h/harmony/harmony_0.7.2-1.dsc


Changes since the last upload:

harmony (0.7.2-1) unstable; urgency=medium
.
* New upstream release.
* New maintainer (closes: #1032369)
* Use tags to determine upstream version
* Declare compliance with Debian Policy 4.6.2, no changes needed.
* Suppress Lintian warning about man page

Regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1057022: RFS: purple-discord/0.9.2023.10.23.git.f8b0c59-1~bpo12+1 -- Discord messaging service plugin for libpurple

2023-11-27 Thread Patrick ZAJDA

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "purple-discord":

* Package name : purple-discord
Version : 0.9.2023.10.23.git.f8b0c59-1~bpo12+1
Upstream contact :
* URL : https://github.com/EionRobb/purple-discord/
* License : GPL-3+
* Vcs :
Section : net

The source builds the following binary packages:

purple-discord - Discord messaging service plugin for libpurple

To access further information about this package, please visit the 
following URL:


https://mentors.debian.net/package/purple-discord/

Alternatively, you can download the package with 'dget' using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/p/purple-discord/purple-discord_0.9.2023.10.23.git.f8b0c59-1~bpo12+1.dsc


Changes since the last upload:

purple-discord (0.9.2023.10.23.git.f8b0c59-1~bpo12+1) 
bookworm-backports; urgency=medium

.
* Rebuild for bookworm-backports.

Regards,
--
Patrick ZAJDA


OpenPGP_0x9D4AD35BEA273DCA.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1056402: RFS: purple-discord/0.9.2023.10.23.git.f8b0c59-1 [ITA] -- Discord messaging service plugin for libpurple

2023-11-22 Thread Patrick ZAJDA

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "purple-discord":

* Package name : purple-discord
Version : 0.9.2023.10.23.git.f8b0c59-1
Upstream contact :
* URL : https://github.com/EionRobb/purple-discord/
* License : GPL-3+
* Vcs :
Section : net

The source builds the following binary packages:

purple-discord - Discord messaging service plugin for libpurple

To access further information about this package, please visit the 
following URL:


https://mentors.debian.net/package/purple-discord/

Alternatively, you can download the package with 'dget' using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/p/purple-discord/purple-discord_0.9.2023.10.23.git.f8b0c59-1.dsc


Changes since the last upload:

purple-discord (0.9.2023.10.23.git.f8b0c59-1) unstable; urgency=medium
.
* New upstream snapshot
* New maintainer (Closes: #1032178)

Regards,
--
Patrick ZAJDA



Bug#1032178: ITA: purple-discord -- Discord messaging service plugin for libpurple

2023-11-21 Thread Patrick ZAJDA

Control: retitle -1 ITA: purple-discord -- Discord messaging service plugin for 
libpurple

Hello,

I am going to take over the maintenance of the purple-ddiscord package.
As soon as I will finish to make some other changes to the actually uploaded 
package to Mentors, I will fill a RFS which will also provide the last upstream 
version.

Best regards,

Patrick



Bug#1042872: (no subject)

2023-08-06 Thread Patrick ZAJDA

Hello,

I can reproduce it on Debian Bookworm.
Is the content you gave the exact one?

Because I had some source files which gave me this error and I noticed 
it was because I had a comment followed by a blank line.

If I remove the blank line after all comments, the warning is gone.

HTH,

Patrick



Bug#965026: grub-emu is unusable with orca nor BRLTTY

2020-07-14 Thread Patrick ZAJDA
Package: grub-emu
Version: 2.02+dfsg1-20
Severity: critical
Tags: a11y
Justification: breaks the whole system

Dear Maintainer,

I use Debian with Orca and BRLTTY and executed grub-emu.
When ran on mate-terminal, it shows an interface where BRLTTY displays "Screen 
not in text mode" and Orca doesn't speak at all.
The only solution to stop it is to killall -9 grub-emu from another terminal.

The most critical situation is when I run grub-emu from a TTY session. In this 
case, BRLTTY displays again "Screen not in text mode" and my system locked, I 
was not able to close grub-emu nor to use another TTY to kill it.
The only solution I found to reboot correctly was use SSH.

-- Package-specific info:

*** BEGIN /proc/mounts
/dev/nvme0n1p3 / ext4 rw,noatime,nodiratime,errors=remount-ro 0 0
/dev/nvme0n1p2 /boot ext2 rw,noatime,nodiratime 0 0
/dev/sda4 /var/vm ext4 rw,noatime,nodiratime,quota,usrquota,grpquota 0 0
/dev/nvme0n1p1 /boot/efi vfat 
rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
 0 0
/dev/sdb1 /home ext4 rw,relatime,quota,usrquota,grpquota 0 0
*** END /proc/mounts

*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="${saved_entry}"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  c520d8e3-9caa-45e3-9dc0-664205763df9
else
  search --no-floppy --fs-uuid --set=root c520d8e3-9caa-45e3-9dc0-664205763df9
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=fr_FR
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=1
  # Fallback normal timeout code in case the timeout_style feature is
  # unavailable.
  else
set timeout=1
  fi
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu 
--class os $menuentry_id_option 
'gnulinux-simple-c520d8e3-9caa-45e3-9dc0-664205763df9' {
savedefault
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  
1891f72e-62a2-4314-98c7-79626e392794
else
  search --no-floppy --fs-uuid --set=root 
1891f72e-62a2-4314-98c7-79626e392794
fi
echo'Chargement de Linux 5.6.0-0.bpo.2-amd64…'
linux   /vmlinuz-5.6.0-0.bpo.2-amd64 
root=UUID=c520d8e3-9caa-45e3-9dc0-664205763df9 ro  splash splash
echo'Chargement du disque mémoire initial…'
initrd  /initrd.img-5.6.0-0.bpo.2-amd64
}
submenu 'Options avancées pour Debian GNU/Linux' $menuentry_id_option 
'gnulinux-advanced-c520d8e3-9caa-45e3-9dc0-664205763df9' {
menuentry 'Debian GNU/Linux, avec Linux 5.6.0-0.bpo.2-amd64' --class 
debian --class gnu-linux --class gnu --class os $menuentry_id_option 
'gnulinux-5.6.0-0.bpo.2-amd64-advanced-c520d8e3-9caa-45e3-9dc0-664205763df9' {
savedefault
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; 
fi
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root  
1891f72e-62a2-4314-98c7-79626e392794
else
  search --no-floppy --fs-uuid --set=root 

Bug#961454: dahdi-dkms: Cannot compile using DKMS on kernel 5.4 backport and latter

2020-05-26 Thread Patrick ZAJDA

Hello,


It looks like the same issue as 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948983 




If I don't make a mistake, the error is the same.



Bug#961512: reportbug-gtk: Keyboard navigation broken in some situations

2020-05-25 Thread Patrick ZAJDA
Package: reportbug-gtk
Version: 7.5.3~deb10u1
Severity: normal
Tags: a11y

Dear Maintainer,

When launching the Reportbug GTK, it is not possible to use keyboard
navigation.
Nothing happens when I press Tab or Shift+Tab.
The only solution I found is to use Orca navigation commands (pav num 7 and 9)
and use "/" to left-clidk "Next" button.
Another annoying keyboard navigation related issue is when I press "Back", only
Back/Next/Cancel button can have the focus using keyboard, even when I try to
use mouse click I cannot modify fields values.
In the case it could be useful, I use Mate desktop.



-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.5.0-0.bpo.2-amd64 (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages reportbug-gtk depends on:
ii  gir1.2-gtk-3.0 3.24.5-5+hypra3
ii  gir1.2-vte-2.910.54.2-2
ii  python3-gi 3.30.4-1
ii  python3-gi-cairo   3.30.4-1
ii  python3-gtkspellcheck  4.0.5-1
ii  reportbug  7.5.3~deb10u1

reportbug-gtk recommends no packages.

reportbug-gtk suggests no packages.

-- no debconf information



Bug#961454: dahdi-dkms: Cannot compile using DKMS on kernel 5.4 backport and latter

2020-05-25 Thread Patrick ZAJDA


Le 24/05/2020 à 21:02, Geert Stappers a écrit :

To me it looks a generic DKMS thing.

So I should have reported it as a DKMS issue instead?

P.S.
What is behind  http://ix.io ?
As in "What source code runs at the ix.io  server?"


If it is better: http://paste.debian.net/1148681/ 
<http://paste.debian.net/1148681/>


The code of ix.io should be free but is still not and yes, we don't know 
the author. It is specified on the main page.


--
Patrick ZAJDA



Bug#961454: dahdi-dkms: Cannot compile using DKMS on kernel 5.4 backport and latter

2020-05-24 Thread Patrick ZAJDA
Package: dahdi-dkms
Version: 1:2.11.1.0.20170917~dfsg-7
Severity: important

Dear Maintainer,

When installing kernel 5.4 or 5.5 from buster-backports or running 
dpkg-reconfigure dahdi-dkms, there is an error inviting to consulte make.log.
This is the make.log I had after the error: http://ix.io/2n8n
It looks like there is an incompatibility with kernel 5.4 and 5.5 which 
prevents the compilation of DAHDI kernel modules.


-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.5.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dahdi-dkms depends on:
ii  dkms   2.6.1-4
ii  dpkg-dev   1.19.7
ii  gawk   1:4.2.1+dfsg-1
ii  gcc4:8.3.0-1
ii  libc6-dev  2.28-10
ii  make   4.2.1-1.2
ii  wget   1.20.1-1.1

Versions of packages dahdi-dkms recommends:
ii  dahdi-linux  1:2.11.1.0.20170917~dfsg-7

dahdi-dkms suggests no packages.

-- no debconf information