Bug#1066079: RFS: ddclient/3.11.2-1 -- address updating utility for dynamic DNS services
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "ddclient": * Package name : ddclient Version : 3.11.2-1 Upstream contact : https://github.com/ddclient/ddclient * URL : https://ddclient.net * License : GPL-2.0+, Artistic or GPL-1+, Apache-2.0 * Vcs : https://salsa.debian.org/debian/ddclient Section : net The source builds the following binary packages: ddclient - address updating utility for dynamic DNS services To access further information about this package, please visit the following URL: https://mentors.debian.net/package/ddclient/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/d/ddclient/ddclient_3.11.2-1.dsc Changes since the last upload: ddclient (3.11.2-1) unstable; urgency=medium . * Add curl build dependency to enable the -curl argument * Suggest curl * Bump Standards-Version to 4.6.2 (no changes needed) * gbp.conf: Rename branches and tags to match current convention * gbp.conf: Set upstream-vcs-tag (for import-orig) * New upstream version 3.11.2 * Refresh patches * Update dependencies * Use dh_installchangelogs to install ChangeLog.md * debian/copyright: Set Upstream-Contact to project URL * debian/copyright: Update copyright year for debian/* Regards, OpenPGP_signature.asc Description: OpenPGP digital signature
MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
Hello, I am affected by this error in the autopkgtest of silx[1] 487s autopkgtest [22:01:24]: test gui: [--- 489s MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER) 489s glx: failed to create drisw screen 489s failed to load driver: zink 493s autopkgtest [22:01:30]: test gui: ---] Someone know how to avoid this issue the test command is here[2]. thanks for your help [1] https://ci.debian.net/packages/s/silx/testing/amd64/43836118/#S12 [2] https://salsa.debian.org/science-team/silx/-/blob/master/debian/tests/gui?ref_type=heads
Re: MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
On Tue, 12 Mar 2024 09:50:51 +0100 (CET) PICCA Frederic-Emmanuel wrote: > Hello, I am affected by this error in the autopkgtest of silx[1] > > 487s autopkgtest [22:01:24]: test gui: [--- > 489s MESA: error: ZINK: vkCreateInstance failed > (VK_ERROR_INCOMPATIBLE_DRIVER) 489s glx: failed to create drisw > screen 489s failed to load driver: zink > 493s autopkgtest [22:01:30]: test gui: ---] > > Someone know how to avoid this issue > > the test command is here[2]. > > thanks for your help > > [1] > https://ci.debian.net/packages/s/silx/testing/amd64/43836118/#S12 > [2] > https://salsa.debian.org/science-team/silx/-/blob/master/debian/tests/gui?ref_type=heads This affected a pkg of mine as well, and seems to be caused by a regression in mesa [1]. Long story short, they print messages to stderr when certain graphics hardware cannot be initialised, even when that is completely expected (because said hardware simply isn't present). For the autopkgtest, you can either wait it out or (temporarily!) tolerate output on stderr. [1]https://gitlab.freedesktop.org/mesa/mesa/-/issues/10293 pgpEwZpj0g2GK.pgp Description: OpenPGP digital signature
Re: MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER)
Do yu know If we have a Debian bug, so I can refer to this bug in mine ? I prefer to not hide the problem and wait u til mesa is fixed (if this is not too long). Do you have a idea of when this issue should be integrated into Debian mesa ?
autopkgtest and runner configuration
Hello, I have some failures depending on the architecture. If I remember correctly I was affected by an ipv6 / ipv4 vs ipv6 only configuration. so my question is simple: What should be the right snipset in order to display network information in the autopkgtest before running the test. Maybe there is somewhere this information already available about the runner configuration. thanks Frederic
Is there a way to set up a sid environment at this time?
Dear Mentors, Unfortunately, my SD card got corrupted (SD Card moment) and I do not have access to a sid environment right now. Is there a way to debootstrap a sid environment for packaging (from trixie perhaps) while the time_t transition is going on? Thanks, -- Shriram Ravindranathan OpenPGP_0xFC7E951A7BEF0836.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Re: Is there a way to set up a sid environment at this time?
On Tue, Mar 12, 2024 at 07:25:56PM +0530, Shriram Ravindranathan wrote: > Dear Mentors, > > Unfortunately, my SD card got corrupted (SD Card moment) and I do not have > access to a sid environment right now. Is there a way to debootstrap a sid > environment for packaging (from trixie perhaps) while the time_t transition > is going on? You should be able to debootstrap testing and you also should be able to upgrade it to sid. This worked for me right now for amd64. -- WBR, wRAR signature.asc Description: PGP signature
Re: Is there a way to set up a sid environment at this time?
Hi! Am 2024-03-12 14:55, schrieb Shriram Ravindranathan: Unfortunately, my SD card got corrupted (SD Card moment) and I do not have access to a sid environment right now. Is there a way to debootstrap a sid environment for packaging (from trixie perhaps) while the time_t transition is going on? Untested, just as an idea: You can debootstrap via snapshot.debian.org from a point before the transition started? Best regards, Alexander
Re: Is there a way to set up a sid environment at this time?
Hi Andrey, When I did a dist-upgrade from trixie it seemed to remove a bunch of necessary packages with error messages like this: `dpkg: libdb5.3:amd64: dependency problems, but removing anyway as you requested: apt-utils depends on libdb5.3.` Although just now I noticed there are no errors when I replace trixie with sid in sources.list and run `apt upgrade`. I suppose this would be sufficient for packaging? On 12/03/24 19:33, Andrey Rakhmatullin wrote: You should be able to debootstrap testing and you also should be able to upgrade it to sid. This worked for me right now for amd64. -- Shriram Ravindranathan OpenPGP_0xFC7E951A7BEF0836.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Re: Is there a way to set up a sid environment at this time?
On Tue, Mar 12, 2024 at 08:54:49PM +0530, Shriram Ravindranathan wrote: > When I did a dist-upgrade from trixie it seemed to remove a bunch of > necessary packages with error messages like this: This is not my experience with a minimal debootstrapped chroot. > Although just now I noticed there are no errors when I replace trixie with > sid in sources.list and run `apt upgrade`. I suppose this would be > sufficient for packaging? If you mean upgrade instead of dist-upgrade then that's not a real sid chroot. -- WBR, wRAR signature.asc Description: PGP signature
Bug#1053565: RFS: openvpn3-client/21+dfsg-1 [ITP] -- virtual private network daemon (version 3)
Package: sponsorship-requests Followup-For: Bug #1053565 X-Debbugs-Cc: ajq...@debian.org Hi Marc, Thank you for your efforts in packaging this package into Debian. I noticed that you conducted a thorough license check and re-uploaded the package into mentors. However, there are still some lintian warnings/errors present in the `debian/copyright` file. Please ensure to check this on the webpage after uploading, or preferably, run a local lintian check before uploading or committing. Additionally, Tobi suggested that the Python component might be better suited in a dedicated Python module package. What are your thoughts on this? Best regards, -Andrew
Re: Is there a way to set up a sid environment at this time?
On 2024-03-12 19:25 +0530, Shriram Ravindranathan wrote: > Dear Mentors, > > Unfortunately, my SD card got corrupted (SD Card moment) and I do not have > access to a sid environment right now. Is there a way to debootstrap a sid > environment for packaging (from trixie perhaps) while the time_t transition > is going on? Yes. I made one yesterday evening with debootstrap (for amd64) and it worked fine. But things are both in flux and in a less-than ideal state at the moment so I think it's a bit random exactly what does and doesn't work at any given moment. We are working on unbunging things so we can get back to our usual level of smooth updates soon. I expect unstable to be rather more unstable than usual for another week or two. Wookey -- Principal hats: Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature
Bug#1066131: RFS: streamlink/6.7.0-1 -- CLI for extracting video streams from various websites to a video player
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "streamlink" for a new upstream version 6.7.0. * Package name: streamlink Version : 6.7.0-1 Upstream Author : Streamlink Team * URL : https://streamlink.github.io/ * License : BSD-2-clause, Apache-2.0, MIT/Expat, SIL-OFL-1.1 * Vcs : https://salsa.debian.org/amurzeau/streamlink/ Section : python It builds those binary packages: python3-streamlink - Python module for extracting video streams from various websites python3-streamlink-doc - CLI for extracting video streams from various websites (documentation) streamlink - CLI for extracting video streams from various websites to a video player To access further information about this package, please visit the following URL: https://mentors.debian.net/package/streamlink/ Alternatively, you can download the package with 'dget' using this command: dget -x https://mentors.debian.net/debian/pool/main/s/streamlink/streamlink_6.7.0-1.dsc Changes since the last upload to unstable: streamlink (6.7.0-1) unstable; urgency=medium * New upstream version 6.7.0 * d/patches: fix tests by resetting the logger level on teardown -- Alexis Murzeau Tue, 12 Mar 2024 23:03:17 +0100 Regards, -- Alexis Murzeau PGP: B7E6 0EBB 9293 7B06 BDBC 2787 E7BD 1904 F480 937F| OpenPGP_0xE7BD1904F480937F.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1066131: Acknowledgement (RFS: streamlink/6.7.0-1 -- CLI for extracting video streams from various websites to a video player)
Hi,
I've re-uploaded the package to change how the tests are fixed.
Instead of patching upstream code, I've changed how pytest is called.
Upstream uses pytest tests' name ("nodeid") to order tests and they are
named relative to the "rootdir" [1].
By default, the rootdir used by pytest is where the pyproject.toml is,
so I need to change it to where the used `tests` directory is (that is
in /<>/.pybuild/cpython3_3.11/build/).
This way, the upstream configuration to properly order tests works and
there is no more test failures.
[1]:
https://github.com/streamlink/streamlink/blob/251fe08f8da8214dafdf094afd80c543b8e2e0fe/tests/conftest.py#L16
See also https://github.com/streamlink/streamlink/pull/5888.
--
Alexis Murzeau
PGP: B7E6 0EBB 9293 7B06 BDBC 2787 E7BD 1904 F480 937F|
OpenPGP_0xE7BD1904F480937F.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
