Bug#1075734: RFS: mangl/1.1.5-1 [ITP] -- Graphical man page viewer
Control: tags -1 +moreinfo On Sun, 14 Jul 2024 23:16:20 -0400 James Montgomery wrote: > On Sun, Jul 14, 2024 at 11:07 PM Otto Kekäläinen wrote: > > > Yes, using Salsa or CI is not required, but I was curious is there > > particular reason this package is not using Salsa-CI to validate > > that all easily testable things are correct? > > > > Hi Otto, > > Thank you for your review of mango. I was not aware that pipelines were > available for Debian packages, so I did not look in to setting one up. > > If there are any suggested standard/starter build templates I can reference > for implementation please let me know. I have several questions regarding the current status of the package. * What is the purpose of debian/mangl-docs.docs file? * I see that your package build-depends on cmake, but I cannot find anything related to CMake anywhere. Can you elaborate? Once you have a good answer to them, I can sponsor your package. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1077615: ITS: porg
Source: porg Version: 2:0.10-1.2 Severity: important X-Debbugs-CC: bran...@logyx.net Dear package porg maintainer in Debian, After looking into the package you maintain (porg, https://tracker.debian.org/pkg/porg), I found that this package received no maintainer updates in the past 8 years and was not in good shape. As a result, I am filing an ITS (Intent to Salvage) request against your package according to section 5.12 in Debian's Developers' Reference [1]. My current plan is to fix the release-critical bugs and refresh packaging. Please let me know whether you are still willing to maintain this package. According to the criteria listed at [2], I will upload a Non- maintainer Upload (NMU) of this package onto DELAYED/7 after 21 days (Aug 20, 2024) to continue with the package salvaging. If you find it necessary to pause the ITS process, please let me know immediately by replying this bug report. [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging [2] https://wiki.debian.org/PackageSalvaging -- Best Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1077559: tracy: Fail to build on most architectures
Source: tracy Severity: grave Version: 0.10+ds-1 X-Debbugs-CC: a...@digistorm.in Dear Debian tracy package maintainer, Your package fails to build on most Debian's official architectures, as shown on [1]. Example of build failure logs: In file included from ../../../server/../dtl/dtl.hpp:44, from ../../../server/TracyView_Compare.cpp:4: ../../../server/../dtl/Diff.hpp: In member function ‘void dtl::Diff::enableTrivial() const’: ../../../server/../dtl/Diff.hpp:168:27: error: assignment of member ‘trivial’ in read-only object 168 | this->trivial = true; | ~~^~ Please investigate into this issue and fix it with another upload. Thanks, Boyuan Yang [1] https://buildd.debian.org/status/package.php?p=tracy signature.asc Description: This is a digitally signed message part
Bug#1077488: sphinx-code-tabs: A new source-only upload is needed for testing migration
在 2024-07-30星期二的 09:48 +1000，Ben Finney写道： > On 29-Jul-2024, Boyuan Yang wrote: > > > As shown on https://tracker.debian.org/pkg/sphinx-code-tabs , your package > > was uploaded with binary arch:all package and cannot migrate to Debian > > Testing. > > Do I understand correctly that: > > * The only way for a package to be accepted through NEW queue (because > it is entering Debian for the first time) is to do a binary upload. Yes. Actually a source+binary upload. > * If successful, that upload will enter Debian ‘unstable’. Yes, but you could have targeted "experimental" instead. > * Because that upload was a binary upload, it cannot enter Debian > ‘testing’. Yes. > Is any of that incorrect? > > How is a NEW upload meant to migrate to Debian ‘testing’? See https://wiki.debian.org/SourceOnlyUpload . In short, there is a longstanding limitation that arch:all packages cannot be binNMUed. For now, doing a source-only upload after passing the NEW queue when your package generates arch:all packages is the only choice. Personally I am in favor of frequent uploads and rebuilds, so I don't see it as a major inconvenience. Anyway, eventually we all want to see this limitation solved on the FTP Masters side. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1077488: sphinx-code-tabs: A new source-only upload is needed for testing migration
Source: sphinx-code-tabs Version: 0.5.5-1 Severity: important X-Debbugs-CC: bign...@debian.org Dear Debian sphinx-code-tabs package maintainer, As shown on https://tracker.debian.org/pkg/sphinx-code-tabs , your package was uploaded with binary arch:all package and cannot migrate to Debian Testing. Please make another source-only upload to solve this problem following https://wiki.debian.org/SourceOnlyUpload . Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1077335: multcomp: Please make another source-only upload for testing migration
Source: multcomp Version: 1.4-26-1 Severity: important X-Debbugs-CC: e...@debian.org Dear Debian multcomp package maintainer, Your latest upload of package multcomp was not a source-only upload. As a result, it was blocked from migrating to Debian Testing. Please make another source-only upload as discussed in https://wiki.debian.org/SourceOnlyUpload . Thanks, Boyuan Yang
Bug#1077292: coremltools: Upstream Python 3.12 support not ready yet (by 2024-07)
Source: coremltools Severity: grave Version: 7.1-1 Control: forwarded -1 https://github.com/apple/coremltools/issues/2129 Dear Debian coremltools package maintainer, The coremltools upstream is still working on Python 3.12 support. As a result, it is not compatible with current Debian Testing/Sid which will only provides python3.12 in the repository. I am opening this bug report so that this issue can be tracked in Debian BTS. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076211: RFS: msc-generator/8.6.1-1 -- Draws signalling charts from textual description
在 2024-07-23星期二的 06:00 +，Gábor Németh写道： > On 2024-07-22 21:08, Boyuan Yang wrote: > > 在 2024-07-22星期一的 06:18 +，Gábor Németh写道： > > > Hi, > > > > > > On 2024-07-22 03:05, Boyuan Yang wrote: > > > > > https://mentors.debian.net/debian/pool/main/m/msc-generator/msc-generator_8.6.2-1.dsc > > > > > > > > I think all changes look okay except for adding the usage of > > > > dpkg-vendor and > > > > exporting a specific environment variable only on Debian in > > > > debian/rules. > > > > > > I'll try to explain. This env var: > > > > > > +VENDOR ?= $(shell dpkg-vendor --query vendor) > > > ... > > > +ifneq ($(VENDOR),Debian) > > > +export PNGDIFF_LUMA_DIFF = 10 > > > +endif > > > > > > In short, `dpkg-vendor` here only controls precision of PNG-generating > > > tests and has no effect on the binary tool itself whatsoever. > > > > > > [1] https://bugs.launchpad.net/ubuntu/+source/msc-generator/+bug/2061755 > > > > If you are tackling [1], I have to remind you that your dpkg-vendor > > comparison > > only applies to Debian and won't go into effect on Ubuntu. In other words, > > I understand that and in no case want to handle any other distros at > all. That is why I'm setting the variable for all cases *except* Debian. > > > My current understanding is that this environment variable loosens the > > comparison threshold in tests. > > That is right: I want to loosen the tests in every distro except Debian. > The rationale is that upstream's CI works on Debian so there we expect > the default (=stricter) test settings to pass. > > Can you agree? Okay if it is more strict in Debian than other derivatives and not vice versa. If possible, please add the following comment to your debian/rules so that future viewers are aware of this change: diff --git a/debian/rules b/debian/rules index 44591f3..53f6098 100755 --- a/debian/rules +++ b/debian/rules @@ -9,6 +9,7 @@ ifneq ($(ARCH),amd64) export MSC_TEST_ALLOWFAIL = 1 export PNGDIFF_NOFONT_MASK_RADIUS = 3 endif +# for dpkg-vendor, see https://bugs.debian.org/1076211#49 ifneq ($(VENDOR),Debian) export PNGDIFF_LUMA_DIFF = 10 endif I am uploading with the addition of this single comment line. Best, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076211: RFS: msc-generator/8.6.1-1 -- Draws signalling charts from textual description
在 2024-07-22星期一的 06:18 +，Gábor Németh写道： > Hi, > > On 2024-07-22 03:05, Boyuan Yang wrote: > > > https://mentors.debian.net/debian/pool/main/m/msc-generator/msc-generator_8.6.2-1.dsc > > > > I think all changes look okay except for adding the usage of dpkg-vendor and > > exporting a specific environment variable only on Debian in debian/rules. > > I'll try to explain. This env var: > > +VENDOR ?= $(shell dpkg-vendor --query vendor) > ... > +ifneq ($(VENDOR),Debian) > +export PNGDIFF_LUMA_DIFF = 10 > +endif > > only affects *tests*: the program `msc-gen` generates pixmaps and during > tests we verify if some known input is rendered to the same PNG as some > known canonical one. It becomes tricky exactly with downstream if a > library like libcairo/libpango has a somewhat different version not > otherwise affecting actual usability of the tool but causing one-two > pixel differences when generating the test PNGs, failing package > building and thus finally blocking a new package version to be accepted > [1]. The upstream CI works on Debian and we fully can control what is > expected on Debian, so in this sense the env var setting only makes > Debian testing more strictly adhering to upstream. > > In short, `dpkg-vendor` here only controls precision of PNG-generating > tests and has no effect on the binary tool itself whatsoever. I can > remove the distinction wrt. other ditros but would prefer to keep it to > be in sync with upstream build results. > > [1] https://bugs.launchpad.net/ubuntu/+source/msc-generator/+bug/2061755 If you are tackling [1], I have to remind you that your dpkg-vendor comparison only applies to Debian and won't go into effect on Ubuntu. In other words, it is useless in handling [1]. Besides Debian and Ubuntu, there are also countless derivatives (LinuxMint, PopOS, ...); you won't be able to handle them one by one. My current understanding is that this environment variable loosens the comparison threshold in tests. In that case, why not set this variable unconditionally so that it covers both Debian and Ubuntu? My preference is that we either set the variable unconditionally, or do not set it at all. Unless you could convince me that it is necessary to make the variable specific to only Debian and not applicable on Ubuntu/LinuxMint/... , please tweak your source code and prepare another version that does not utilize dpkg-vendor. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076211: RFS: msc-generator/8.6.1-1 -- Draws signalling charts from textual description
Hi, On Fri, 19 Jul 2024 12:41:54 + =?UTF-8?Q?G=C3=A1bor_N=C3=A9meth?= wrote: > Phil, > > I've prepared a new submission at mentors [1] and believe all the issues > were addressed: > > - A new upstream & corresponding changes in d/ clear up the licenses > (BTW thanks for mentioning `lrc` which I did not know about earlier; > it still complains about a few files that > have either "and" or "or" dual licensing but I believe d/copyright is > now correct) > - Both `pbuild --twice` and `reportest` finish without an error for me > - As does lintian: hardening was added to the build, and overrides for > false positives are now recorded > > Would you be so kind as to take a look? > > [1] > https://mentors.debian.net/debian/pool/main/m/msc-generator/msc-generator_8.6.2-1.dsc I think all changes look okay except for adding the usage of dpkg-vendor and exporting a specific environment variable only on Debian in debian/rules. Could you please explain it? A Debian-specific behavior will cause implicit behavior difference between Debian and downstream distributions, and is usually avoided unless you have a good justification. Once I receive a good explanation on it, I can sponsor and upload your package. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076663: [pkg-apparmor] Bug#1076663: apparmor-profiles: AppArmor parser error for /etc/apparmor.d/font-manager
Control: close -1 Control: fixed -1 font-manager/0.9.0-2 X-Debbugs-CC: jrf...@gmail.com appar...@cboltz.de pkg-apparmor-t...@alioth-lists.debian.net Hi, On Sun, 21 Jul 2024 17:56:45 + =?UTF-8?Q?Juan_Rafael_Fern=C3=A1ndez_Garc=C3=ADa?= wrote: > On Sun, 21 Jul 2024 at 14:40, Christian Boltz wrote: > > > > Hello, > > Hi again > > > Am Sonntag, 21. Juli 2024, 12:45:22 MESZ schrieb Juan-Rafael Fernandez: > > > Package: apparmor-profiles > > > Version: 3.1.7-1 > > > > The font-manager profile expects AppArmor >= 4.0, but you have 3.1.7. > > [1] I didn't check which package ships the font-manager profile, but I'm > > quite sure it isn't part of apparmor-profiles. > > I did. Font-manager. > > > You (or the font-manager package [1]) will need to change the profile to > > use abi/3.0 instead of abi/4.0 (and maybe remove rule types not yet > > supported in 3.x) for distributions that include AppArmor 3.x. > > That's easy to do locally, but should I open a file against > font-manager? Any plans to move to AppArmor 4.x anytime soon? Package font-manager maintainer here. Closing this bug since I have dropped /etc/apparmor.d/font-manager from Debian font-manager package already as a temporary mitigation. On the other hand, I am waiting for the AppArmor Debian packager to migrate to AppArmor 4.x so that this issue is properly solved. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1075717: mawk: rand() incorrect results on i386 - returns negative numbers and ignores srand()
在 2024-07-19星期五的 16:08 -0400，Thomas Dickey写道：
> On Fri, Jul 19, 2024 at 02:04:43PM -0400, Boyuan Yang wrote:
> > X-Debbugs-CC: kniel...@knielsen-hq.org dic...@his.com
> >
> > 在 2024-07-03星期三的 18:46 -0400，Thomas Dickey写道：
> > > On Wed, Jul 03, 2024 at 05:07:10PM -0400, Thomas Dickey wrote:
> > > > On Wed, Jul 03, 2024 at 11:03:09AM -0400, Boyuan Yang wrote:
> > > > > X-Debbugs-CC: t...@invisible-island.net
> > > > >
> > > > > 在 2024-07-03星期三的 16:28 +0200，Kristian Nielsen写道：
> > > > > > Package: mawk
> > > > > > Version: 1.3.4.20240622-1
> > > > > > Severity: normal
> > > > > >
> > > > > > Dear Maintainer,
> > > > > >
> > > > > > Running mawk produces wrong output from rand() on i386:
> > > > > >
> > > > > > $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> > > > > > 0.158578
> > > > > > $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> > > > > > -0.276944
> > > > > > $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> > > > > > -0.387807
> > > > > > $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> > > > > > 0.470306
> > > > > >
> > > > > > The result of rand() should never be negative; and it should be
> > > > > > deterministic after calling srand().
> > > > > >
> > > > > > This occurs on i386 (tested in sbuild --arch=i386 as part of
> > > > > > debugging a
> > > > > > reproducible build problem of package openscad).
> > > > > >
> > > > > > The expected output is the same value between 0 and 1, for example:
> > > > > >
> > > > > > $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> > > > > > 0.559536
> > > > > > $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> > > > > > 0.559536
> > > > > > $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> > > > > > 0.559536
> > > > > >
> > > > > > The longer story, for completeness: I am the maintainer for
> > > > > > openscad, and I
> > > > > > see openscad sometimes failing to build reproducibly on (only) i386
> > > > > > during
> > > > > > the past year. The root cause seems to be a test script that calls
> > > > > > awk and
> > > > > > behaves unexpectedly due to getting a negative number out of rand().
> > > > > >
> > > > > > The problem does not seem to occur on amd64 or arm64. Openscad
> > > > > > doesn't build
> > > > > > on armhf, so not sure if the problem in mawk is specific to i386 or
> > > > > > may be
> > > > > > specific to 32-bit for example.
> > > > >
> > > > > Ack. Reproducible on Debian Sid (mawk/1.3.4.20240622), not
> > > > > reproducible on Debian 12
> > > > > Bookworm (mawk/1.3.4.20200120). Likely a regression since 2020.
> > > >
> > > > odd - I can reproduce the problem, but what I'm seeing is older.
> > > > I'll investigate further.
> > >
> > > what I see is a problem with the configurable feature to use the system
> > > srand/rand functions. Apparently the relatively new configure check
> > > (and availability) for arc4random_stir/arc4random is not being scaled
> > > properly.
> > >
> > > The other bug that I see is that if the system rand/srand is used,
> > > then srand has no effect in the script. That is a drawback to the
> > > new/improved(?) arc4random functions: their developers chose to not
> > > support an
> > > equivalent to srand.
> > >
> > > This bug can be resolved by adding --enable-builtin-srand to the configure
> > > options. The issue with repeatability has come up before - see
> > >
> > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=63843
> > >
> > > but the scaling is actually a bug. The configure script's choice of
> > > random functions is a little awkward to work around other than by
> > > setting the configure option (actually a small patch to the configure
> > > script
> > > would work, by changing this line:
> > >
> > > for cf_f
Bug#1075717: mawk: rand() incorrect results on i386 - returns negative numbers and ignores srand()
X-Debbugs-CC: kniel...@knielsen-hq.org dic...@his.com
在 2024-07-03星期三的 18:46 -0400，Thomas Dickey写道：
> On Wed, Jul 03, 2024 at 05:07:10PM -0400, Thomas Dickey wrote:
> > On Wed, Jul 03, 2024 at 11:03:09AM -0400, Boyuan Yang wrote:
> > > X-Debbugs-CC: t...@invisible-island.net
> > >
> > > 在 2024-07-03星期三的 16:28 +0200，Kristian Nielsen写道：
> > > > Package: mawk
> > > > Version: 1.3.4.20240622-1
> > > > Severity: normal
> > > >
> > > > Dear Maintainer,
> > > >
> > > > Running mawk produces wrong output from rand() on i386:
> > > >
> > > > $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> > > > 0.158578
> > > > $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> > > > -0.276944
> > > > $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> > > > -0.387807
> > > > $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> > > > 0.470306
> > > >
> > > > The result of rand() should never be negative; and it should be
> > > > deterministic after calling srand().
> > > >
> > > > This occurs on i386 (tested in sbuild --arch=i386 as part of debugging a
> > > > reproducible build problem of package openscad).
> > > >
> > > > The expected output is the same value between 0 and 1, for example:
> > > >
> > > > $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> > > > 0.559536
> > > > $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> > > > 0.559536
> > > > $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> > > > 0.559536
> > > >
> > > > The longer story, for completeness: I am the maintainer for openscad,
> > > > and I
> > > > see openscad sometimes failing to build reproducibly on (only) i386
> > > > during
> > > > the past year. The root cause seems to be a test script that calls awk
> > > > and
> > > > behaves unexpectedly due to getting a negative number out of rand().
> > > >
> > > > The problem does not seem to occur on amd64 or arm64. Openscad doesn't
> > > > build
> > > > on armhf, so not sure if the problem in mawk is specific to i386 or may
> > > > be
> > > > specific to 32-bit for example.
> > >
> > > Ack. Reproducible on Debian Sid (mawk/1.3.4.20240622), not reproducible
> > > on Debian 12
> > > Bookworm (mawk/1.3.4.20200120). Likely a regression since 2020.
> >
> > odd - I can reproduce the problem, but what I'm seeing is older.
> > I'll investigate further.
>
> what I see is a problem with the configurable feature to use the system
> srand/rand functions. Apparently the relatively new configure check
> (and availability) for arc4random_stir/arc4random is not being scaled
> properly.
>
> The other bug that I see is that if the system rand/srand is used,
> then srand has no effect in the script. That is a drawback to the
> new/improved(?) arc4random functions: their developers chose to not support an
> equivalent to srand.
>
> This bug can be resolved by adding --enable-builtin-srand to the configure
> options. The issue with repeatability has come up before - see
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=63843
>
> but the scaling is actually a bug. The configure script's choice of
> random functions is a little awkward to work around other than by
> setting the configure option (actually a small patch to the configure script
> would work, by changing this line:
>
> for cf_func in arc4random_stir/arc4random srandom/random
> srand48/lrand48 srand/rand
> to
> for cf_func in srandom/random srand48/lrand48 srand/rand
>
> but I seem to recall that doesn't mesh with dpkg-buildpackage (ymmv).
I must be having difficulty understanding the analysis above.
From what I read, there could be two issues:
(1) the default, external, POSIX-compliant(?) implementation of srand()
call (from libc?) has different behavior than the mawk-internally-implemented
one, or whatever mawk expects. Switching to the internal one helps solve the
randomness/reproducibility issue.
-> However, I don't understand why this is only an issue on i386, while
other platforms (amd64, ...) seem not affected by this problem.
(2) The scaling bug of srand() return value should never be negative.
It is a different bug. Thomas proposed a patch to ditch the selection
from arc4random.
-> Still, I don't understand why this is only an issue on i386, while
other platforms (amd64, ...) seem not affected by this problem.
-> I noticed the existence of arc4random(3) and srandom(3) but obviously
don't have a good understanding to them yet.
-> It looks like if we enabled --enable-builtin-srand, both problem (1)
and (2) will be gone. Is that the case?
I would appreciate it if anyone could give a hint on some more insights,
or what could be done on the Debian side (isn't other distros also
affected by the bug?). I don't mind carrying a patch on aclocal.m4
if absolutely needed.
Thanks,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part
Bug#1075846: RM: tk-html3 -- ROM; dead upstream
On Sat, 6 Jul 2024 12:22:52 +0200 Ole Streicher wrote: > Package: ftp.debian.org > Severity: normal > Control: affects -1 src:tk-html3 > Control: block 1075832 by -1 > X-Debbugs-Cc: by...@debian.org > > > As discussed in #1075832, tkhtml3 and specifically hv3 are dead since a > long (>10years). I did "some" upstream maintenance, mainly fixing a few > compilation problems. It is heavily outdated now and should be removed. > > Please remove this package. It has no reverse dependencies and should no > longer be used. Just to confirm this Removal request. Please remove the package from Testing/Sid when available. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072274: ITP: fcitx5-varnam -- Fcitx5 wrapper for Varnam input method.
在 2024-07-18星期四的 22:00 +0530，Anoop M S写道： > Hi, > On Mon, 15 Jul 2024 00:43:38 +0530 Anoop M S wrote: > > Hi, > > On Sun, 14 Jul 2024 14:44:59 -0400 Boyuan Yang wrote: > > > Hi, > > > > > > 在 2024-07-14星期日的 20:59 +0530，Anoop M S写道： > > > > On Fri, 31 May 2024 10:48:21 -0400 Boyuan Yang > > wrote: > > > > > Hi, > > > > > > > > > > 在 2024-05-31星期五的 08:19 +，Anoop M S写道： > > > > > > Package: wnpp > > > > > > Severity: wishlist > > > > > > Owner: Anoop M S > > > > > > X-Debbugs-Cc: debian-de...@lists.debian.org, > anoo...@disroot.org > > > > > > > > > > > > * Package name : fcitx5-varnam > > > > > > Version : 0.0.1 > > > > > > Upstream Contact: Anoop M S > > > > > > * URL : > https://github.com/varnamproject/varnam-fcitx5 > > > > > > * License : GPL > > > > > > Programming Lang: C++ > > > > > > Description : Fcitx5 wrapper for Varnam input method. > > > > > > > > > > > > Fcitx5 wrapper for Varnam(https://www.varnamproject.com) Input > > > > Method Engine. > > > > > > Easily type Indian languages on Linux desktops. > > > > > > > > > > > > I would like to join Debian Input Method Team, and package and > > > > maintain it. > > > > > > And I would need a sponsor to upload it as well. > > > > > > > > > > Please prepare an initial version first. You can host it on your > > own > > > > Salsa git repo > > > > > or via mentors.debian.net , or choose whichever platform that is > > more > > > > convenient to you. > > > > > Please submit a regular RFS request and notify me once you are > > prepared. > > > > > > > > > > If it looks good, I can help to move your git packaging repo > to the > > > > Salsa Input Method > > > > > Team namespace, sponsor the upload and add you into the Salsa > Input > > > > Method Team group. > > > > > > > > > > Thanks, > > > > > Boyuan Yang > > > > > > > > I've prepared an initial release and sent RFS (#1076334). > > > > > > > > Kindly review at your convenience. > > > > > > The following issues are critical and must be fixed: > > > > > > * > > > https://github.com/varnamproject/varnam-fcitx5/blob/a2c9412461f68a5293cec24609076951e28a3b27/meson.build#L11-L29 > > > is unacceptable. The build system is only targeting on x86_64 (amd64) > > architecture, which is > > > not reasonable since Debian and Fedora both support multiple hardware > > architectures. > > I've addressed the raised issues in the upstream. And made few changes > in the package as well (haven't pushed the code yet). > Lintian currently showing following issues > * newer-standards-version 4.7.0 > * debian-watch-does-not-check-openpgp-signature > * prefer-uscan-symlink > > full text : https://paste.debian.net/plain/1323647 > > Are these ignorable? And is there anything else I need to follow to do > the version update > or can I create a fresh setup with only the new version? They are of low priority and you can revisit them later. If you would like, you can try to solve them following the text description you just saw in that terminal output. Please prepare a fresh setup with updated source code and version numbers so that Debian Developers can review. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076515: meson: Please switch from cython-legacy to cython3 for build-dependency
Source: meson Severity: important Version: 1.5.0-1 Control: block 1067200 by -1 Tags: patch X-Debbugs-CC: jpakk...@gmail.com Dear Debian meson package maintainer, Your package build-depends on package cython-legacy, which does not support Python 3.12 and is due to be removed. Please switch to cython 3.x (cython3) if possible. Upstream meson should have supported the cython 3.x series as well as the Debian-specific /usr/bin/cython3 executable path, and thus a plain replacement in the build-dependency list should be good enough. Of course, please test it out before making a new upload. Let me know if you have any questions. Best Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076389: ITS: rpmlint
在 2024-07-15星期一的 17:17 -0400，Boyuan Yang写道： > Hi, > > On 7/15/24 3:30 PM, Arturo Borrero Gonzalez wrote: > > Please go ahead, no need for delay. > > > > I have no time (or interest) in this package anymore. > > > > You may drop me from the maintainer list as well. > > Thanks for the update. Can you grant me the write permission > to the packaging repo https://salsa.debian.org/pkg-rpm-team/rpmlint ? > My Salsa username is https://salsa.debian.org/byang . Nevermind, looks like I already have the write permission. I will close this bug accoridngly. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076409: ITP: libideviceactivation -- Library to manage the activation process of Apple iOS device
Package: wnpp Owner: Boyuan Yang X-Debbugs-Cc: by...@debian.org Severity: wishlist * Package name : libideviceactivation Version : 1.1.1 Upstream Contact: Nikias Bassen * URL : https://github.com/libimobiledevice/libideviceactivation * License : LGPL-2.1-or-later Programming Lang: C Description : Library to manage the activation process of Apple iOS devices This project provides an interface to activate and deactivate iOS devices by talking to Apple's webservice alongside a command-line utility named ideviceactivation. This package will be maintained in Debian Salsa imobiledevice team. Thanks, Boyuan Yang
Bug#1076389: ITS: rpmlint
Hi, On 7/15/24 3:30 PM, Arturo Borrero Gonzalez wrote: Please go ahead, no need for delay. I have no time (or interest) in this package anymore. You may drop me from the maintainer list as well. Thanks for the update. Can you grant me the write permission to the packaging repo https://salsa.debian.org/pkg-rpm-team/rpmlint ? My Salsa username is https://salsa.debian.org/byang . Best, Boyuan Yang
Bug#1076401: RM: cvs-buildpackage -- RoQA; Orphaned; Unmaintained; Useless
Package: ftp.debian.org Control: affects -1 + src:cvs-buildpackage X-Debbugs-Cc: cvs-buildpack...@packages.debian.org devscri...@packages.debian.org User: ftp.debian@packages.debian.org Usertags: remove Severity: normal Dear Debian FTP Masters, I believe it is now the time to drop package cvs-buildpackage from Debian development archive. * This package was orphaned back in 2008. * No meaningful source code changes have taken place after 2008. * The CVS VCS packaging workflow is long gone, and no Debian packages in Sid uses it. [1] * There are no reverse dependencies or reverse build-dependencies. Package devscript has a suggestion on it but it is harmless (package maintainers CC-ed). Thanks, Boyuan Yang [1] https://trends.debian.net/vcs-hosting_unstable-packages.csv signature.asc Description: This is a digitally signed message part
Bug#1076394: O: wf-shell -- GTK-based panel and background client for Wayfire
Package: wnpp Control: affects -1 + src:wf-shell X-Debbugs-Cc: wf-sh...@packages.debian.org Severity: normal I intend to orphan the wf-shell package as I no longer use software from WayfireWM ecosystem. The package description is: Package wf-shell contains various components needed to build a fully functional DE based around wayfire. Currently it has only a GTK-based panel and background client. . Wayfire is a 3D Wayland compositor, inspired by Compiz and based on wlroots. It aims to create a customizable, extendable and lightweight environment without sacrificing its appearance. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076393: O: wf-config -- Wayfire-specific library for managing config files
Package: wnpp Control: affects -1 + src:wf-config X-Debbugs-Cc: wf-con...@packages.debian.org Severity: normal I intend to orphan the wf-config package as I no longer use software from WayfireWM ecosystem. The package description is: Wf-config is a library for managing configuration files, written for wayfire 3D wayland compositor. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076392: O: wcm -- Wayfire Config Manager
Package: wnpp Control: affects -1 + src:wcm X-Debbugs-Cc: w...@packages.debian.org Severity: normal I intend to orphan the wcm package as I no longer use software from WayfireWM ecosystem. The package description is: Wayfire Config Manager is a Gtk3 application to configure wayfire. It writes the config file that wayfire reads to update option values. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076391: O: wayfire -- 3D Wayland compositor
Package: wnpp Control: affects -1 + src:wayfire X-Debbugs-Cc: wayf...@packages.debian.org Severity: normal I intend to orphan the wayfire package as I no longer use software from WayfireWM ecosystem. The package description is: Wayfire is a 3D Wayland compositor, inspired by Compiz and based on wlroots. It aims to create a customizable, extendable and lightweight environment without sacrificing its appearance. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076390: O: wayfire-shadows -- Window Shadows Plugin for Wayfire
Package: wnpp Control: affects -1 + src:wayfire-shadows X-Debbugs-Cc: wayfire-shad...@packages.debian.org Severity: normal I intend to orphan the wayfire-shadows package as I no longer use software from WayfireWM ecosystem. The package description is: Wayfire is a 3D Wayland compositor, inspired by Compiz and based on wlroots. It aims to create a customizable, extendable and lightweight environment without sacrificing its appearance. . By default, the plugin will add fast and nice shadows around windows that use server side decorations. Additionally there is an option to make the focused window glow. signature.asc Description: This is a digitally signed message part
Bug#1076389: ITS: rpmlint
Package: rpmlint Severity: important Version: 2.5.0+ds1-0.1 X-Debbugs-CC: art...@debian.org Dear Debian rpmlint package maintainer, According to https://tracker.debian.org/pkg/rpmlint , you were listed as the package uploader of Debian package rpmlint. However, no maintainer upload from you was seen after 2016. As a result, I consider this package eligible to the Debian ITS (Intent to Salvage) procedure and thus is filing an ITS request against your package according to section 5.12 in Debian's Developers' Reference [1]. My current plan is to package the new upstream version and update the package uploaders list. Please let me know whether you are still willing to maintain this package. According to the criteria listed at [2], I will upload a Non- maintainer Upload (NMU) of this package onto DELAYED/7 after 21 days (Aug 05, 2024) to continue with the package salvaging. If you find it necessary to pause the ITS process, please let me know immediately by replying this bug report. [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging [2] https://wiki.debian.org/PackageSalvaging -- Best Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076307: mpd: Intent to backport to bookworm-backports
Control: notfound -1 0.23.15-1 Control: close -1 X-Debbugs-CC: kal...@debian.org f...@debian.org On Sat, 13 Jul 2024 23:13:18 -0400 Boyuan Yang wrote: > Source: mpd > Version: 0.23.15-1 > X-Debbugs-CC: kal...@debian.org f...@debian.org > > Dear Debian mpd package maintainers, > > I intend to backport mpd/0.23.15-1 to debian bookworm-backports. From what I > currently > see from the source code, it looks like a trivial no-change backport would be > enough. > > According to https://backports.debian.org/Contribute/ , uploading a backport > may or > may not be performed by the original package maintainer. As a result, I am > moving > forward to upload the backported package onto BACKPORTS-NEW for review now. > If you > find mpd unsuitable for backporting or needs further work for a proper > backport, please > let me know ASAP. > > The BACKPORTS-NEW queue can be found at > https://ftp-master.debian.org/backports-new.html . The backported version is now accepted into Debian bookworm-backports. Closing this bug report accordingly. Thanks, Boyuan Yang
Bug#1076354: O: kasumi -- Simple dictionary utility for Anthy
Package: wnpp Control: affects -1 + src:kasumi X-Debbugs-Cc: kas...@packages.debian.org X-Debbugs-Cc: debian-input-met...@lists.debian.org debian-japan...@lists.debian.org Severity: normal Since no real human package maintainers exist for package kasumi now, I intend to orphan the kasumi package. Its upstream is long dead. It will be affected by the FTBFS bug when building with GCC 14, as in https://bugs.debian.org/1075108 . The package description is: Kasumi is a personal dictionary management tool for Anthy. Anthy is a Japanese input method to convert Hiragana text to Kana Kanji mixed text. . Featuring add words, edit words, delete words, search words and so on. Thanks, Boyuan Yang
Bug#1072274: ITP: fcitx5-varnam -- Fcitx5 wrapper for Varnam input method.
Hi, 在 2024-07-14星期日的 20:59 +0530，Anoop M S写道： > On Fri, 31 May 2024 10:48:21 -0400 Boyuan Yang wrote: > > Hi, > > > > 在 2024-05-31星期五的 08:19 +，Anoop M S写道： > > > Package: wnpp > > > Severity: wishlist > > > Owner: Anoop M S > > > X-Debbugs-Cc: debian-de...@lists.debian.org, anoo...@disroot.org > > > > > > * Package name : fcitx5-varnam > > > Version : 0.0.1 > > > Upstream Contact: Anoop M S > > > * URL : https://github.com/varnamproject/varnam-fcitx5 > > > * License : GPL > > > Programming Lang: C++ > > > Description : Fcitx5 wrapper for Varnam input method. > > > > > > Fcitx5 wrapper for Varnam(https://www.varnamproject.com) Input > Method Engine. > > > Easily type Indian languages on Linux desktops. > > > > > > I would like to join Debian Input Method Team, and package and > maintain it. > > > And I would need a sponsor to upload it as well. > > > > Please prepare an initial version first. You can host it on your own > Salsa git repo > > or via mentors.debian.net , or choose whichever platform that is more > convenient to you. > > Please submit a regular RFS request and notify me once you are prepared. > > > > If it looks good, I can help to move your git packaging repo to the > Salsa Input Method > > Team namespace, sponsor the upload and add you into the Salsa Input > Method Team group. > > > > Thanks, > > Boyuan Yang > > I've prepared an initial release and sent RFS (#1076334). > > Kindly review at your convenience. The following issues are critical and must be fixed: * https://github.com/varnamproject/varnam-fcitx5/blob/a2c9412461f68a5293cec24609076951e28a3b27/meson.build#L11-L29 is unacceptable. The build system is only targeting on x86_64 (amd64) architecture, which is not reasonable since Debian and Fedora both support multiple hardware architectures. To avoid headaches, I highly recommend switching to CMake buildsystem and reuse fcitx5-provided CMake infrastructure. That will make the life easier. If Meson is the only choice, a more elegant solution is needed. Will https://mesonbuild.com/CMake-module.html help? * Please explain that why you are carrying patches in debian/patches/ directory, and why they cannot enter upstream project. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076307: mpd: Intent to backport to bookworm-backports
Source: mpd Version: 0.23.15-1 X-Debbugs-CC: kal...@debian.org f...@debian.org Dear Debian mpd package maintainers, I intend to backport mpd/0.23.15-1 to debian bookworm-backports. From what I currently see from the source code, it looks like a trivial no-change backport would be enough. According to https://backports.debian.org/Contribute/ , uploading a backport may or may not be performed by the original package maintainer. As a result, I am moving forward to upload the backported package onto BACKPORTS-NEW for review now. If you find mpd unsuitable for backporting or needs further work for a proper backport, please let me know ASAP. The BACKPORTS-NEW queue can be found at https://ftp-master.debian.org/backports-new.html . Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076142: soundkonverter: Upstream development ceased in 2022, consider removal?
Source: soundkoverter Version: 3.0.1-3 Tags: sid trixie Severity: serious X-Debbugs-CC: m...@debian.org mes...@debian.org p...@debian.org Dear Debian soundkonverter package maintainer, The upstream GitHub repository, https://github.com/dfaust/soundkonverter , has been archived since 2022. It is obvious that the upstream for soundkonverter is now dead. As a result, please consider excluding this package from the future Trixie release or have it completely removed from Debian Sid/Testing archive. Otherwise we the Debian package maintainers will need to maintain this software by ourselves. An imminent issue would be taglib 2.0 compatibility (which I will submit in a separate RC bug very soon). Please feel free to let me know if you have any thoughts. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076101: xsane: Recommends firefox | www-browser, but firefox is not in Stable/Testing repo
Source: xsane Version: 0.999-12 Severity: important X-Debbugs-CC: debian@jff.email Control: tags -1 +patch Hi Jörg Frings-Fürst, I noticed https://sources.debian.org/src/xsane/0.999-12/debian/control/#L31 , which has xsane to recommend firefox | www-browser. However, package firefox will not appear in Debian Testing/Stable, causing the installation of xsane to fall back to www-browser and results in an unexpected selection of www-browser. One of the most recent report can be found in [1], in which the LXQt ydesktop environment automatically brings in hv3 as the installed web browser. Hv3 is a very outdated web browser choice, and this shall never happen in a sane environment: aptitude why hv3 i task-lxqt-desktop Recommends xsane i A xsane Recommends firefox | www-browser i A hv3 Provides www-browser I believe the best solution shall be replacing the Recommends: line with firefox-esr | firefox | www-browser to ensure that the first choice is always available, no matter on Debian Testing/Stable/Sid/etc. If possible, I am looking to having this fix backported to Debian 12 as well. Please let me know if you have any comments. Thanks! Best, Boyuan Yang [1] https://www.reddit.com/r/debian/comments/1dw2yk8/hv3_web_browser/ signature.asc Description: This is a digitally signed message part
Bug#1076093: O: tkcvs -- Graphical front-end to CVS and Subversion
Package: wnpp Control: affects -1 + src:tkcvs X-Debbugs-Cc: tk...@packages.debian.org Severity: normal I intend to orphan the tkcvs package as I no longer have enough time to work on it. The package description is: TkCVS is a Tk based graphical interface to the CVS and Subversion version control systems. For CVS, it includes facilities for providing "user friendly" names to modules and directories within the repository, and provides a facility to interactively browse the repository looking for modules and directories. . Some of the features of TkCVS include: . File and directory browser, with optional display of hidden files, and display of the current directory's location within the CVS tree. . Push-button based check-in / check-out of CVS modules. Ability to add and delete files from the repository also using push buttons. . Module tree browser, and reports showing the structure of the CVS modules tree. Individual modules or entire directory trees may be checked out using the browser. . Updating of files from the repository when they change. . Tagging and branching of files from the file browser, and tagging and branching of modules from the module browser. . Exporting a CVS module or directory from the repository for delivery off-site. . Creation of patch files between two releases of a module, or between a release and the current (head) version. . Viewing of diff and status listings for currently checked out modules. signature.asc Description: This is a digitally signed message part
Bug#1076088: transition: libplist
Package: release.debian.org Severity: normal X-Debbugs-CC: cor...@debian.org Control: affects -1 src:libplist User: release.debian@packages.debian.org Usertags: transitions Dear Debian Release Team, I would like to start the transition as listed on auto-libplist page, https://release.debian.org/transitions/html/auto-libplist.html . The rebuild on all the packages is now complete. All packages can be built successfully. Some sourceful uploads are necessary to complete the transition, including libusbmuxd, libimobiledevice, ideviceinstaller, ifuse and usbmuxd. I can make team uploads to handle them. ### Level 1 - [x] libplist (experiemental only) ### Level 2 - [x] kodi (OK) - [x] libusbmuxd (experimental OK) - [x] uxplay (OK) ### Level 3 - [x] libimobiledevice (experimental OK) ### Level 4 - [x] gvfs - [x] ideviceinstaller (experimental OK) - [x] idevicerestore - [x] ifuse (experimental OK) - [x] libgpod - [x] solid - [x] upower - [x] usbmuxd (experimental OK) ### Level 5 - [x] kio-extras Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076041: ITP: libtatsu -- Library handling communication with Apple Tatsu Signing Server
Package: wnpp Owner: Boyuan Yang X-Debbugs-Cc: by...@debian.org Severity: wishlist * Package name: libtatsu Version : 1.3.0 Upstream Contact: Nikias Bassen * URL : https://github.com/libimobiledevice/libtatsu * License : LGPL-2.1-or-later Programming Lang: Description : Library handling communication with Apple Tatsu Signing Server This library provides functionality to handle the communication with Apple's Tatsu Signing Server (TSS). This package is a dependency to the new versions of libimobiledevice library. This package will be maintained under Debian salsa imobiledevice-team group. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1075760: hplip: diff for NMU version 3.22.10+dfsg0-5.1
Control: tags 1075760 + pending
Dear maintainer,
I've prepared an NMU for hplip (versioned as 3.22.10+dfsg0-5.1) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru hplip-3.22.10+dfsg0/debian/changelog
hplip-3.22.10+dfsg0/debian/changelog
--- hplip-3.22.10+dfsg0/debian/changelog2024-04-26 17:39:02.0
-0400
+++ hplip-3.22.10+dfsg0/debian/changelog2024-07-09 00:32:24.0
-0400
@@ -1,3 +1,10 @@
+hplip (3.22.10+dfsg0-5.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Use read_file instead of readfp for python 3.12 (Closes: #1075760)
+
+ -- Tianyu Chen Tue, 09 Jul 2024 12:32:24 +0800
+
hplip (3.22.10+dfsg0-5) unstable; urgency=medium
* take care of implicit function declarations (Closes: #1066348)
diff -Nru hplip-3.22.10+dfsg0/debian/patches/0085-python-3.12-compat.patch
hplip-3.22.10+dfsg0/debian/patches/0085-python-3.12-compat.patch
--- hplip-3.22.10+dfsg0/debian/patches/0085-python-3.12-compat.patch
1969-12-31 19:00:00.0 -0500
+++ hplip-3.22.10+dfsg0/debian/patches/0085-python-3.12-compat.patch
2024-07-09 00:32:24.0 -0400
@@ -0,0 +1,51 @@
+Description: Use read_file instead of readfp for python 3.12
+Author: Tianyu Chen
+Bug-Debian: https://bugs.debian.org/1075760
+Forwarded: no
+Last-Update: 2024-07-09
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/base/g.py
b/base/g.py
+@@ -128,7 +128,7 @@ class ConfigBase(object):
+ try:
+ fp = open(self.filename, "r")
+ try:
+-self.conf.readfp(fp)
++self.conf.read_file(fp)
+ except configparser.MissingSectionHeaderError:
+ print("")
+ log.error("Found No Section in %s. Please set the http
proxy for root and try again." % self.filename)
+--- a/ui/devmgr4.py
b/ui/devmgr4.py
+@@ -1227,7 +1227,7 @@ class DevMgr4(DevMgr4_base):
+
+ hplip_conf = ConfigParser.ConfigParser()
+ fp = open("/etc/hp/hplip.conf", "r")
+-hplip_conf.readfp(fp)
++hplip_conf.read_file(fp)
+ fp.close()
+
+ try:
+--- a/ui4/devmgr5.py
b/ui4/devmgr5.py
+@@ -1024,7 +1024,7 @@ class DevMgr5(QMainWindow, Ui_MainWindo
+
+ hplip_conf = configparser.ConfigParser()
+ fp = open("/etc/hp/hplip.conf", "r")
+-hplip_conf.readfp(fp)
++hplip_conf.read_file(fp)
+ fp.close()
+
+ try:
+--- a/ui5/devmgr5.py
b/ui5/devmgr5.py
+@@ -1072,7 +1072,7 @@ class DevMgr5(Ui_MainWindow_Derived, Ui_
+
+ hplip_conf = configparser.ConfigParser()
+ fp = open("/etc/hp/hplip.conf", "r")
+-hplip_conf.readfp(fp)
++hplip_conf.read_file(fp)
+ fp.close()
+
+ try:
diff -Nru hplip-3.22.10+dfsg0/debian/patches/series
hplip-3.22.10+dfsg0/debian/patches/series
--- hplip-3.22.10+dfsg0/debian/patches/series 2024-04-26 17:39:02.0
-0400
+++ hplip-3.22.10+dfsg0/debian/patches/series 2024-07-09 00:32:24.0
-0400
@@ -82,3 +82,4 @@
0082-Some-of-the-print-modes-for-DeskJet-815C-are-incorre.patch
0083-add-format-string-to-snprintf.patch
0084-take-care-of-implicit-declaration-of-functions.patch
+0085-python-3.12-compat.patch
signature.asc
Description: This is a digitally signed message part
Bug#1076032: hplip: Please package new upstream version (3.24.4)
Source: hplip Severity: important Version: 3.22.10+dfsg0-5 X-Debbugs-CC: alteh...@debian.org Dear Debian hplip package maintainer, The new upstream release of hplip has been available for a while. Please consider packaging the new version in Debian, and check the custom patches carried over by Ubuntu. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1076023: flowblade: Please migrate away from CDBS and python-distutils.mk
Source: flowblade Severity: important Version: 2.16.3-1 Dear Debian flowblade package maintainers, As the python3.12-default transition is now completed, the usage of python3-distutils shall be completely dropped, Your package still uses CDBS and python-distutils.mk, which is alarming. Please check whether such usage involves distutils, and if possible, migrate to the modern Python packaging infrastructure (dh-sequence-python3). Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1075760: hplip-gui breaks with python 3.12
Control: severity -1 grave On Thu, 4 Jul 2024 10:13:27 -0300 Adilson dos Santos Dantas wrote: > Package: hplip-gui > Version: 3.22.10+dfsg0-5 > Severity: normal > > Dear Maintainer, > > Updating hplip with the last version from sid pulls python 3.12 as default > python3 version > > Then it's breaks hplip leading some messages like this below: > > hp-toolbox > Traceback (most recent call last): > File "/usr/bin/hp-toolbox", line 38, in > from base.g import * > File "/usr/share/hplip/base/g.py", line 239, in > sys_conf = SysConfig() > ^^^ > File "/usr/share/hplip/base/g.py", line 184, in __init__ > ConfigBase.__init__(self, '/etc/hp/hplip.conf') > File "/usr/share/hplip/base/g.py", line 89, in __init__ > self.read() > File "/usr/share/hplip/base/g.py", line 130, in read > self.conf.readfp(fp) > > AttributeError: 'ConfigParser' object has no attribute 'readfp'. Did you > mean: ' > read'? > > Reverting back to the testing version fix these errors since it reverts > python3 package to 3.11. > > Probably it is related to this Arch Linux forum report: > > https://bbs.archlinux.org/viewtopic.php?id=295303 Bumping bug severity as the python3.12-default transition has completed. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1075988: intlfonts: Please package new version 1.4.2
Source: intlfonts Version: 1.2.1-10.1 Severity: normal A new upstream release of intlfonts is now available at https://ftp.gnu.org/gnu/intlfonts/intlfonts-1.4.2.tar.gz . Please consider packaging it in Debian. Thanks, Boyuan Yang
Bug#1075936: RM: python-ck -- RoQA; Dead Upstream; Unmaintained; Incompatible with Python3.12
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: by...@debian.org grigori.fur...@ctuning.org Severity: normal Dear Debian FTP Masters, I request removal of package python-ck from the Debian archive. * According to https://tracker.debian.org/pkg/python-ck , it received no maintainer upload since 2018. The most recent attempt to contact the package maintainer (in CC list) received no reply [3]. * Its upstream also states that the software is no longer being developed at [1]. * It is affected by the FTBFS with Python 3.12 as default python3 version. [2] As a result, please remove src:python-ck from Debian Sid/Unstable archive. Thanks, Boyuan Yang [1] https://github.com/mlcommons/ck/blob/a01aa289d3940824c5ef439992f61e0344c32362/ck/__ARCHIVED__/README.md [2] https://bugs.debian.org/1058260 [3] https://bugs.debian.org/1073798 signature.asc Description: This is a digitally signed message part
Bug#1075908: ITS: cairocffi
在 2024-07-07星期日的 17:01 -0400，Jean-Christophe Jaskula写道： > Hi Boyuan, > > I’m not active in the Debian community and won’t be possible to find time to > catch up and contribute again. Please move forward with your plan. Thanks for the quick response! I am making the necessary changes now. Best, Boyuan Yang > > On Jul 7, 2024, at 1:28 PM, Boyuan Yang wrote: > > > > Source: cairocffi > > Severity: important > > Version: 1.7.1-1 > > X-Debbugs-CC: jean.christophe.jask...@gmail.com > > > > Dear Debian cairocffi package uploader, > > > > According to information from https://tracker.debian.org/pkg/cairocffi , you > > are listed as the package uploader for Debian package cairocffi. However, > > package cairocffi saw no upload from you in the last 9 years (since 2015). > > As a result, I am filing an ITS (Intent to Salvage) request > > against your package according to section 5.12 in Debian's Developers' > > Reference [1]. > > > > As seen from DDPO page [2], it seems that package cairocffi is the only > > Debian package > > that you are listed as maintainer or uploader. As a result, I am wondering > > whether > > you are still active in the Debian activity. > > > > Please feel free to let me know whether you still would like to list > > yourself in the > > cairocffi package uploaders list. If yes, I will be happy to reconfirm your > > package > > maintainership. If there is no response in 21 days (by July 28, 2024), I > > will make > > a Debian package upload to remove your name from the package uploaders > > list. After > > that, you are still welcome to contribute to Debian project as a regular > > contributor. > > > > Thanks and looking forward to your reply, > > > > Best Regards, > > Boyuan Yang > > > > [1] > > https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging > > [2] > > https://qa.debian.org/developer.php?email=jean.christophe.jaskula%40gmail.com > signature.asc Description: This is a digitally signed message part
Bug#1075908: ITS: cairocffi
Source: cairocffi Severity: important Version: 1.7.1-1 X-Debbugs-CC: jean.christophe.jask...@gmail.com Dear Debian cairocffi package uploader, According to information from https://tracker.debian.org/pkg/cairocffi , you are listed as the package uploader for Debian package cairocffi. However, package cairocffi saw no upload from you in the last 9 years (since 2015). As a result, I am filing an ITS (Intent to Salvage) request against your package according to section 5.12 in Debian's Developers' Reference [1]. As seen from DDPO page [2], it seems that package cairocffi is the only Debian package that you are listed as maintainer or uploader. As a result, I am wondering whether you are still active in the Debian activity. Please feel free to let me know whether you still would like to list yourself in the cairocffi package uploaders list. If yes, I will be happy to reconfirm your package maintainership. If there is no response in 21 days (by July 28, 2024), I will make a Debian package upload to remove your name from the package uploaders list. After that, you are still welcome to contribute to Debian project as a regular contributor. Thanks and looking forward to your reply, Best Regards, Boyuan Yang [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging [2] https://qa.debian.org/developer.php?email=jean.christophe.jaskula%40gmail.com
Bug#1075832: tk-html3: Completely remove hv3 (and tk-html3), for good reasons
Source: tk-html3 Severity: serious Version: 3.0~fossil20110109-9 X-Debbugs-CC: oleb...@debian.org Dear Debian tk-html3/hv3 package maintainers, Today I encountered a discussion around package hv3 in Debian. With some brief investigation, I found some abnormally high popcon values [2] for hv3 and tk-html3, which is alarming since this software saw no upstream development since 2011 and definitely shall not see so many installations. My current thought is that it may have been accidentally introduced due to Provides: www-browser somewhere (e.g., with Debian XFCE installer as a default www-browser provider), but I haven't really dig into it. By all means, I believe tk-html3/hv3 shall not linger in Debian archive anymore in 2024. Especially since hv3 is a web browser, having an outdated web browser is especially problematic. Ubuntu also had the concensus [3] back in 2022. If you agree, please submit a RM bug against Debian FTP Masters to remove the source package. If you find this source package still useful, please consider dropping the hv3 binary package. At the very very least -- dropping the Provides: www-browser from hv3 could help if you don't want to remove anything at all. I don't see any reverse dependencies or reverse build-dependencies around tk-html3 (build-deps(1) seems to be reporting false positives), so the removal shall be harmless and beneficial. Please let me know if you have any comments. Thanks! Best Regards, Boyuan Yang [1] https://www.reddit.com/r/debian/comments/1dw2yk8/hv3_web_browser/ [2] https://qa.debian.org/popcon.php?package=tk-html3 [3] https://bugs.launchpad.net/ubuntu/+source/tk-html3/+bug/1982578 signature.asc Description: This is a digitally signed message part
Bug#1075782: libzdb: FTBFS on 32-bit 2038-safe architectures
select select.o ../libzdb.la -lsqlite3
In file included from zdbpp.cpp:6:
../zdb/zdbpp.h:406:14: error: ‘void zdb::PreparedStatement::bind(int, time_t)’
cannot be overloaded with ‘void zdb::PreparedStatement::bind(int, long long
int)’
406 | void bind(int parameterIndex, time_t x) {
| ^~~~
../zdb/zdbpp.h:398:14: note: previous declaration ‘void
zdb::PreparedStatement::bind(int, long long int)’
398 | void bind(int parameterIndex, long long x) {
| ^~~~
libtool: link: gcc -I../src -I../src/util -I../src/net -I../src/db
-I../src/exceptions -Wno-address -Wno-pointer-sign -g -O2
-Werror=implicit-function-declaration -ffile-
prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection
-Wformat -Werror=format-security -D_GNU_SOURCE -Wall -Wunused -Wno-unused-label
-funsigned-char
-std=c11 -Wl,-z -Wl,relro -o .libs/select select.o
-L/usr/lib/arm-linux-gnueabihf/ -lmariadb ../.libs/libzdb.so -lsqlite3
make[3]: *** [Makefile:449: zdbpp-zdbpp.o] Error 1
make[3]: *** Waiting for unfinished jobs
make[3]: Leaving directory '/<>/test'
make[2]: *** [Makefile:763: all-recursive] Error 1
Thanks,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part
Bug#1075781: O: tidy-html5 -- HTML/XML syntax checker and reformatter
Package: wnpp Control: affects -1 + src:tidy-html5 X-Debbugs-Cc: tidy-ht...@packages.debian.org ond...@debian.org Severity: normal I intend to orphan the tidy-html5 package as I don't have enough energy to drive the transition from the current tidy-html5 5.6.x to 5.8.x series. The package description is: Tidy corrects and cleans up HTML and XML documents by fixing markup errors and upgrading legacy code to modern standards. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1075717: mawk: rand() incorrect results on i386 - returns negative numbers and ignores srand()
X-Debbugs-CC: t...@invisible-island.net
在 2024-07-03星期三的 16:28 +0200，Kristian Nielsen写道：
> Package: mawk
> Version: 1.3.4.20240622-1
> Severity: normal
>
> Dear Maintainer,
>
> Running mawk produces wrong output from rand() on i386:
>
> $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> 0.158578
> $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> -0.276944
> $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> -0.387807
> $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> 0.470306
>
> The result of rand() should never be negative; and it should be
> deterministic after calling srand().
>
> This occurs on i386 (tested in sbuild --arch=i386 as part of debugging a
> reproducible build problem of package openscad).
>
> The expected output is the same value between 0 and 1, for example:
>
> $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> 0.559536
> $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> 0.559536
> $ echo | mawk 'BEGIN {srand(10);} {print rand()};'
> 0.559536
>
> The longer story, for completeness: I am the maintainer for openscad, and I
> see openscad sometimes failing to build reproducibly on (only) i386 during
> the past year. The root cause seems to be a test script that calls awk and
> behaves unexpectedly due to getting a negative number out of rand().
>
> The problem does not seem to occur on amd64 or arm64. Openscad doesn't build
> on armhf, so not sure if the problem in mawk is specific to i386 or may be
> specific to 32-bit for example.
Ack. Reproducible on Debian Sid (mawk/1.3.4.20240622), not reproducible on
Debian 12
Bookworm (mawk/1.3.4.20200120). Likely a regression since 2020.
CC the mawk upstream developer to make them aware of this issue.
Thomas: if you need help in setting up a proper Debian Sid i386 environment to
reproduce the issue and do debugging, feel free to let me know.
Thanks,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part
Bug#1074224: crossfire: diff for NMU version 1.75.0-6.1
Control: tags 1074224 + pending
Dear maintainer,
I've prepared an NMU for crossfire (versioned as 1.75.0-6.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru crossfire-1.75.0/debian/changelog crossfire-1.75.0/debian/changelog
--- crossfire-1.75.0/debian/changelog 2023-08-05 08:01:09.0 -0400
+++ crossfire-1.75.0/debian/changelog 2024-07-02 15:39:27.0 -0400
@@ -1,3 +1,12 @@
+crossfire (1.75.0-6.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches/0005-Fix-build-with-Python-3.12.patch:
+Cherry-pick upstream fix on Python 3.12 compatibility.
+(Closes: #1074224)
+
+ -- Boyuan Yang Tue, 02 Jul 2024 15:39:27 -0400
+
crossfire (1.75.0-6) unstable; urgency=medium
* Patch plugins/cfpython/cjson.c to use
diff -Nru crossfire-1.75.0/debian/patches/0005-Fix-build-with-Python-3.12.patch
crossfire-1.75.0/debian/patches/0005-Fix-build-with-Python-3.12.patch
--- crossfire-1.75.0/debian/patches/0005-Fix-build-with-Python-3.12.patch
1969-12-31 19:00:00.0 -0500
+++ crossfire-1.75.0/debian/patches/0005-Fix-build-with-Python-3.12.patch
2024-07-02 15:39:01.0 -0400
@@ -0,0 +1,96 @@
+From: Boyuan Yang
+Date: Tue, 2 Jul 2024 15:38:46 -0400
+Subject: Fix build with Python 3.12
+
+Applied-Upstream:
https://sourceforge.net/p/crossfire/crossfire-server/ci/472dd26ac74419baa0e6373cb04e095437e994c6/
+---
+ plugins/cfpython/cjson.c | 51
+ 1 file changed, 12 insertions(+), 39 deletions(-)
+
+diff --git a/plugins/cfpython/cjson.c b/plugins/cfpython/cjson.c
+index 1483d8f..da1547d 100644
+--- a/plugins/cfpython/cjson.c
b/plugins/cfpython/cjson.c
+@@ -687,18 +687,14 @@ static PyObject *encode_string(PyObject *string) {
+ #if defined(IS_PY26) || defined(IS_PY3K)
+ static PyObject *encode_unicode(PyObject *unicode) {
+ PyObject *repr;
+-Py_UNICODE *s;
+-Py_ssize_t size;
++Py_ssize_t size, pos;
+ char *p;
+ static const char *hexdigit = "0123456789abcdef";
+-#ifdef Py_UNICODE_WIDE
+ static const Py_ssize_t expandsize = 10;
+-#else
+-static const Py_ssize_t expandsize = 6;
+-#endif
+
+-s = PyUnicode_AS_UNICODE(unicode);
+-size = PyUnicode_GET_SIZE(unicode);
++int kind = PyUnicode_KIND(unicode);
++void *data = PyUnicode_DATA(unicode);
++size = PyUnicode_GET_LENGTH(unicode);
+
+ if (size > (PY_SSIZE_T_MAX-2-1)/expandsize) {
+ PyErr_SetString(PyExc_OverflowError, "unicode object is too large to
make repr");
+@@ -715,17 +711,21 @@ static PyObject *encode_unicode(PyObject *unicode) {
+ p = PyByteArray_AS_STRING(repr);
+
+ *p++ = '"';
++pos = 0;
+
+-while (size-- > 0) {
+-Py_UNICODE ch = *s++;
++const Py_UCS4 quote = PyByteArray_AS_STRING(repr)[0];
++
++while (pos < size) {
++Py_UCS4 ch = PyUnicode_READ(kind, data, pos);
++pos++;
+
+ /* Escape quotes */
+-if ((ch == (Py_UNICODE)PyByteArray_AS_STRING(repr)[0] || ch == '\\'))
{
++if ((ch == quote || ch == '\\')) {
+ *p++ = '\\';
+ *p++ = (char)ch;
+ continue;
+ }
+-#ifdef Py_UNICODE_WIDE
++
+ /* Map 21-bit characters to '\U00xx' */
+ else if (ch >= 0x1) {
+ *p++ = '\\';
+@@ -740,33 +740,6 @@ static PyObject *encode_unicode(PyObject *unicode) {
+ *p++ = hexdigit[ch&0x000F];
+ continue;
+ }
+-#else
+-/* Map UTF-16 surrogate pairs to Unicode \U escapes */
+-else if (ch >= 0xD800 && ch < 0xDC00) {
+-Py_UNICODE ch2;
+-Py_UCS4 ucs;
+-
+-ch2 = *s++;
+-size--;
+-if (ch2 >= 0xDC00 && ch2 <= 0xDFFF) {
+-ucs = (((ch&0x03FF)<<10)|(ch2&0x03FF))+0x0001;
+-*p++ = '\\';
+-*p++ = 'U';
+-*p++ = hexdigit[(ucs>>28)&0x000F];
+-*p++ = hexdigit[(ucs>>24)&0x000F];
+-*p++ = hexdigit[(ucs>>20)&0x000F];
+-*p++ = hexdigit[(ucs>>16)&0x000F];
+-*p++ = hexdigit[(ucs>>12)&0x000F];
+-*p++ = hexdigit[(ucs>>8)&0x000F];
+-*p++ = hexdigit[(ucs>>4)&0x000F];
+-*p++ = hexdigit[ucs&0x000F];
+-continue;
+-}
+-/* Fall through: isolated surrogates are copied as-is */
+-s--;
+-size++;
+-}
+-#endif
+ /* Map 16-bit characters to '\u' */
+ if (ch >= 256) {
+ *p++ = '\\';
diff -Nru crossfire-1.75.0/debian/patches/series
crossfire-1.75.0/debian/patches/series
--- crossfire-1.75.0/debian/patches/series 2023-08-04 14:48:39.
Bug#1074551: socat: diff for NMU version 1.8.0.0-4~bpo12+1
Control: tags 1074551 + patch Control: tags 1074551 + pending Dear maintainer, I've prepared an NMU for socat (versioned as 1.8.0.0-4~bpo12+1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru socat-1.8.0.0/debian/changelog socat-1.8.0.0/debian/changelog --- socat-1.8.0.0/debian/changelog 2024-01-06 02:47:44.0 -0500 +++ socat-1.8.0.0/debian/changelog 2024-07-01 13:50:40.0 -0400 @@ -1,3 +1,10 @@ +socat (1.8.0.0-4~bpo12+1) bookworm-backports; urgency=medium + + * Non-maintainer upload. + * Rebuild for bookworm-backports. (closes: #1074551) + + -- Boyuan Yang Mon, 01 Jul 2024 13:50:40 -0400 + socat (1.8.0.0-4) unstable; urgency=medium * Disable remaining tests for not working on buildds. signature.asc Description: This is a digitally signed message part
Bug#1074551: backporting socat 1.8 to bookworm
Source: socat Version: 1.8.0.0-4 X-Debbugs-CC: g...@debian.org 在 2024-06-30星期日的 13:32 +，Thierry写道： > Hi, > > socat 1.8 is in trixie. This version is a major improvement since it > provides supports for SOCKS5, a feature that was awaited for years [1]. > Could this version be backported to bookworm ? > > Ciao, > Thierry > > [1] see e.g. https://github.com/runsisi/socat/ Forwarding your request to notify the original package maintainer (@gcs) and register as a bug report. The original package maintainer could help with the backport process. If there's no comment from the original package maintainer, we may proceed with the backporting. Let's wait a few days before we proceed. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1074328: RM: shadowsocks-libev -- ROM; Abandoned Upstream; Affected by pcre2 removal
Package: ftp.debian.org Control: affects -1 + src:shadowsocks-libev X-Debbugs-Cc: shadowsocks-li...@packages.debian.org team+brid...@tracker.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: r...@debian.org Severity: normal Dear Debian FTP Masters, As discussed in https://bugs.debian.org/1072934 , I would like to drop packages around the ecosystem around shadowsocks-libev due to upstream abandoned the ss-libev codebase and moved to rust-based implementation. Package shadowsocks-libev is abandoned upstream for 3 years, and it is a leaf package in the dependency tree. It is affected by pcre2 removal. As a result, please remove this package from Debian Sid/Unstable archive. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1074311: fcitx5-bamboo: please add support for loong64
X-Debbugs-CC: z...@debian.org Hi, 在 2024-06-26星期三的 11:16 +，wuruilong写道： > Source: fcitx5-bamboo > Severity: normal > Tags: patch > X-Debbugs-Cc: wuruil...@loongson.cn > User: debian-loonga...@lists.debian.org > Usertags: loong64 > > Dear Maintainer, > > fcitx5-bamboo compiled incorrectly on loongarch, attachment patch solved the > problem. > Please merge the attached patch into the repository. --- fcitx5-bamboo-1.0.6/debian/control 2024-06-26 09:54:26.082295989 + +++ fcitx5-bamboo/debian/control2024-06-26 09:33:18.788488166 + @@ -10,7 +10,8 @@ debhelper-compat (= 13), extra-cmake-modules, gettext, - golang, + golang[!loong64], + golang-go[loong64], fcitx5-modules-dev, libfcitx5core-dev, pkg-config, @zhsj: Should the "golang" package also appear for loong64 architecture? If yes, then https://salsa.debian.org/go-team/compiler/golang-defaults/-/commit/1421df94d758a1bbc4b6fa7282fd0b3a020498b1 is not complete and shall be further revised. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1074273: RM: shadowsocks-v2ray-plugin -- RoQA; Abandoned Upstream; Affected by pcre2 Removal
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: by...@debian.org shadowsocks-v2ray-plu...@packages.debian.org Severity: normal Dear Debian FTP Masters, As discussed in https://bugs.debian.org/1073791 and https://bugs.debian.org/1072935 , I would like to drop packages around the ecosystem around shadowsocks-libev due to upstream abandoned the ss-libev codebase and moved to rust-based implementation. Package shadowsocks-v2ray-plugin is abandoned upstream for 3 years, and it is a leaf package in the dependency tree. It depends on shadowsocks-libev, which is affected by pcre2 removal. As a result, please remove this package from Debian Sid/Unstable archive. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1074001: ITP: libdjinterop -- C++ library to allow access to DJ record database formats
Package: wnpp Owner: Boyuan Yang Severity: wishlist * Package name: libdjinterop Version : 0.21.0 Upstream Contact: Name * URL : https://github.com/xsco/libdjinterop * License : LGPL-3.0-or-later Programming Lang: C++ Description : C++ library to allow access to DJ record database formats The libdjinterop library is a C++ library that allows access to database formats used to store information about DJ record libraries. . This library currently supports: - Engine Library, as used on "Prime"-series DJ equipment. This package is a dependency to the new version of mixxx. This package will be maintained in Debian Multimedia Team. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1073867: ITP: sqlite-modern-cpp -- Modern sqlite cpp wrapper
Package: wnpp Owner: Boyuan Yang Severity: wishlist * Package name: sqlite-modern-cpp Version : 3.2 Upstream Contact: 2017 aminroosta * URL : https://github.com/SqliteModernCpp/sqlite_modern_cpp * License : MIT Programming Lang: C++ Description : Modern sqlite cpp wrapper This library is a lightweight modern C++ wrapper around sqlite C API. This header-only c++ library is vendored into many existing Debian projects, and packaging it separately could help maintain the codebase at a central place. This library is a build-dependency for libdjinterop, which is a new build-dependency for package mixxx. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1073805: ITS: xdm
Source: xdm Version: 1:1.1.11-3.1 Severity: important X-Debbugs-CC: k...@debian.org debia...@lists.debian.org Hi, If I remember correctly, kibi@ said their X-related packages is no longer being worked on. I don't see that the Xorg team umbrella is meaningfully having some of these package maintained, and thus I am filing an ITS (Intent to Salvage) request against this package according to section 5.12 in Debian's Developers' Reference [1]. I am planning to refresh packaging, introduce the latest upstream release and put my name into the package uploaders field. If possible, I would also like to join the Salsa xorg-team so that its Salsa repo could be updated. I had a long pending request for Salsa team joining, but looks like the request was either dismissed or disappeared. Otherwise I could move the git packaging maintenance to Salsa Debian namespace. According to the criteria listed at [2], I will upload a Non- maintainer Upload (NMU) of this package onto DELAYED/7 after 21 days (July 09, 2022) to continue with the package salvaging. If you find it necessary to pause the ITS process, please let me know immediately by replying this bug report. [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging [2] https://wiki.debian.org/PackageSalvaging -- Best Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1073799: magic-wormhole: Please package new py3.12-compatible release 0.14.0
Source: magic-wormhole Severity: important X-Debbugs-CC: jroll...@finestructure.net anar...@debian.org Version: 0.13.0-1 Dear Debian magic-wormhole package maintainers, A new upstream release of magic-wormhole v0.14.0 is now available. It declares compatibility with Python 3.12, which should also solve https://bugs.debian.org/1073069 . In Debian, we are also trying to solve all issues that blocks the migration to Python 3.12, and your upload will need to be solved. If you need any help, please feel free to let me know. Thanks! Best, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1073798: ITS: python-ck
Source: python-ck Version: 1.9.4-1.1 Severity: important X-Debbugs-CC: grigori.fur...@ctuning.org Dear package python-ck maintainer in Debian, After looking into the package you maintain (python-ck, https://tracker.debian.org/pkg/python-ck), I found that this package received no maintainer updates in the past 6 years and was not in good shape. As a result, I am filing an ITS (Intent to Salvage) request against your package according to section 5.12 in Debian's Developers' Reference [1]. My current plan is to refresh packaging, fix RC bugs and co-maintain it under Debian Python Team. Please let me know whether you are still willing to maintain this package. According to the criteria listed at [2], I will upload a Non- maintainer Upload (NMU) of this package onto DELAYED/7 after 21 days (July 09, 2024) to continue with the package salvaging. If you find it necessary to pause the ITS process, please let me know immediately by replying this bug report. [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging [2] https://wiki.debian.org/PackageSalvaging -- Best Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1073791: shadowsocks-v2ray-plugin: Consider removing the package
Source: shadowsocks-v2ray-plugin Version: 1.3.1-4 Severity: serious X-Debbugs-CC: r...@debian.org rogershim...@gmail.com shadowsocks-v2ray-plu...@packages.debian.org Tags: sid Hi, Following the previous communication in March, I am considering to take action and remove related packages in the ss-libev ecosystem. Package shadowsocks-v2ray-plugin will be removed together with shadowsocks-libev. I plan to file RM bug to Debian FTP Masters after 7 days (on 2024-06-25). If you have any questions, please feel free to let me know. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072291: libzdb: diff for NMU version 3.1-1
Control: tags 1072291 + patch Control: tags 1072291 + pending Dear maintainer, I've prepared an NMU for libzdb (versioned as 3.1-1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Regards. diff -Nru libzdb-3.1/debian/changelog libzdb-3.1/debian/changelog --- libzdb-3.1/debian/changelog 2024-03-01 02:26:07.0 -0500 +++ libzdb-3.1/debian/changelog 2024-06-17 16:03:35.0 -0400 @@ -1,3 +1,10 @@ +libzdb (3.1-1) unstable; urgency=medium + + * Take over package maintenance via ITS process. (Closes: #1072291) + * debian/control: Update Vcs-* fields to use Debian Salsa GitLab. + + -- Boyuan Yang Mon, 17 Jun 2024 16:03:35 -0400 + libzdb (3.1-0.3) unstable; urgency=medium * Non-maintainer upload. diff -Nru libzdb-3.1/debian/control libzdb-3.1/debian/control --- libzdb-3.1/debian/control 2024-03-01 02:26:07.0 -0500 +++ libzdb-3.1/debian/control 2024-06-17 16:03:32.0 -0400 @@ -1,6 +1,6 @@ Source: libzdb -Priority: extra -Maintainer: Jack Bates +Priority: optional +Maintainer: Boyuan Yang Build-Depends: dpkg-dev (>= 1.22.5), autotools-dev, debhelper (>= 10), dh-autoreconf, @@ -12,8 +12,8 @@ Standards-Version: 3.9.8 Section: libs Homepage: http://tildeslash.com/libzdb -Vcs-Git: git://anonscm.debian.org/collab-maint/libzdb.git -Vcs-Browser: https://anonscm.debian.org/git/collab-maint/libzdb.git +Vcs-Git: https://salsa.debian.org/debian/libzdb.git +Vcs-Browser: https://salsa.debian.org/debian/libzdb Package: libzdb-dev Section: libdevel signature.asc Description: This is a digitally signed message part
Bug#1073577: RM: simple-obfs -- ROM; Abandoned Upstream; Affected by pcre2 Removal
Package: ftp.debian.org Control: affects -1 + src:simple-obfs X-Debbugs-Cc: simple-o...@packages.debian.org team+brid...@tracker.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: r...@debian.org Severity: normal Dear Debian FTP Masters, As discussed in https://bugs.debian.org/1072935 , I would like to drop packages around the ecosystem around shadowsocks-libev due to upstream abandoned the ss-libev codebase and moved to rust-based implementation. Package simple-obfs is abandoned upstream for 5 years, and it is a leaf package in the dependency tree. It depends on shadowsocks-libev, which is affected by pcre2 removal. As a result, please remove this package from Debian Sid/Unstable archive. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1073576: pgreplay: Please monitor and package new upstream release
Source: pgreplay Version: 1.2.0-2.1 Severity: important Tags: sid X-Debbugs-CC: c...@debian.org cyril.bouth...@isvtec.com cy...@bouthors.org Dear Debian pgreplay package maintainer, The pgreplay upstream located at https://laurenz.github.io/pgreplay/ now has a new upstream release of version 1.3.0. Please consider updating the upstream monitoring script and package the new version in Debian. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1058104: astropy-helpers: FTBFS: ModuleNotFoundError: No module named 'imp'
X-Debbugs-CC: oleb...@debian.org Hi, On Thu, 14 Dec 2023 08:51:59 +0100 Ole Streicher wrote: > Control: tags -1 wontfix > > astropy-helpers is an outdated helper package for building packages in > the Astropy ecosystem. It is recently superceded by extension-helpers. > The package should end its career now, and be removed before trixie. > > I think that there are no longer Debian packages build-dependent from > astropy-helpers. If there are, thes should be instead updated and/or > ported to extension-helpers. == -> % build-rdeps python3-astropy-helpers Reverse Build-depends in unstable/main: --- astroquery hipspy Found a total of 2 reverse build-depend(s) for python3-astropy-helpers. Reverse Build-depends in unstable/contrib: -- No reverse build-depends found for python3-astropy-helpers. Reverse Build-depends in unstable/non-free: --- No reverse build-depends found for python3-astropy-helpers. Reverse Build-depends in unstable/non-free-firmware: No reverse build-depends found for python3-astropy-helpers. === Two reverse-dependencies exist, and both of them are not having active upstream development. You are also listed as the uploader for them. If you believe that this issue will not be fixed upstream, please review the current status of these packages and determine how to proceed. Thanks! Best, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1073136: RM: kmfl-related packages -- ROM; superseded by src:keyman
X-Debbugs-CC: e...@sil.org Dear Debian FTP Masters, This is a confirmation from the Input Method Team that the package removal requests are legit. Package libkmfl, kmflcomp, ibus-kmfl are now obsolete and superceded by src:keyman. For more background information, see https://lists.debian.org/debian-input-method/2024/06/msg00054.html and https://lists.debian.org/debian-input-method/2022/03/msg7.html . Please feel free to proceed with package removal from Debian Sid. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072945: RM: megadown -- RoQA; Dead Upstream; Unmaintained; Incompatible with Python3
Package: ftp.debian.org User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: by...@debian.org vivia.nikolai...@puri.sm Severity: normal Dear Debian FTP Masters, As discussed in https://bugs.debian.org/1007941 , package megadown is unmaintained upstream for more than 5 years with no maintainer Debian upload since 2018. The current version is not compatible with Python3 which makes it RC-buggy. As a result, please remove it from Debian Sid repo for QA purposes. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072942: wbxml2: Please package new upstream release 0.11.9
Source: wbxml2 Version: 0.11.8+dfsg-5 Severity: normal X-Debbugs-CC: sunwea...@debian.org Dear Debian wbxml2 package maintainer, A new upstream release of wbxml2 is available as 0.11.9. Please consider packaging it. In the meanwhile, I would like to take the chance to suggest monitoring upstream issue https://github.com/libwbxml/libwbxml/issues/74 . This issue is opened back when wbxml2 was orphaned, and the preparation of future releases shall take this issue's fix into consideration. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072936: colordiff: Please package new upstream release 1.0.21
Source: colordiff Version: 1.0.20-1 Tags: sid Severity: normal X-Debbugs-CC: da...@sungate.co.uk Dear Debian colordiff package maintainer, A new upstream release of package colordiff 1.0.21 is now available. Please consider packaging it in Debian. I can provide package upload sponsorship if you need it. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072935: simple-obfs: Consider removing the package
Source: simple-obfs Version: 0.0.5-6 Severity: serious X-Debbugs-CC: r...@debian.org rogershim...@gmail.com Tags: sid Hi, Following the previous communication in March, I am considering to take action and remove related packages in the ss-libev ecosystem. The first targeted package would be simple-obfs. I plan to file RM bug to Debian FTP Masters after 7 days (on 2024-06-17). If you have any questions, please feel free to let me know. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072934: shadowsocks-libev: Consider removing the package
Source: shadowsocks-libev Version: 3.3.5+ds-10 Severity: serious X-Debbugs-CC: r...@debian.org rogershim...@gmail.com Tags: sid Hi, Following the previous communication in March, I am considering to take action and remove related packages in the ss-libev ecosystem. Package shadowsocks-libev will be removed together with simple-obfs. I plan to file RM bug to Debian FTP Masters after 7 days (on 2024-06-17). If you have any questions, please feel free to let me know. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072927: ITP: python-localzone -- Low-calorie python library for managing DNS zones
Package: wnpp Owner: Boyuan Yang Severity: wishlist * Package name: python-localzone Version : 0.9.8 Upstream Contact: Andrew Grant Spencer * URL : https://github.com/ags-slc/localzone * License : BSD-3-Clause Programming Lang: Python Description : Low-calorie python library for managing DNS zones Localzone is a simple python library for managing DNS zones. While localzone may be a low-calorie library, it's stuffed full of everything that a hungry hostmaster needs. This package is an optional dependency to dns-lexicon library. This package will be maintained under Debian Python Team umbrella. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072851: ITP: python-truncnorm -- Moments for truncated multivariate normal distributions for Python
Package: wnpp Owner: Boyuan Yang Severity: wishlist * Package name: python-truncnorm Version : 0.0.2 Upstream Contact: Jaakko Luttinen * URL : https://github.com/jluttine/truncnorm * License : Expat Programming Lang: Python Description : Moments for truncated multivariate normal distributions for Python Package truncnorm provides support of arbitrary order moments for doubly truncated multivariate normal distributions as a Python library. This package is a dependency to the new version of python-bayespy. This package will be maintained under Debian Science Team umbrella. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072850: python-mkdocs: Please package new version 1.6.0
Source: python-mkdocs Severity: normal Version: 1.5.3+dfsg-1 X-Debbugs-CC: b...@debian.org c.schoen...@t-online.de Dear Debian python-mkdocs maintainer, A new upstream release of mkdocs is available. Please consider reviewing it (as well as the compatibility of related packages) and have it packaged in Debian. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072833: python-cmarkgfm: Please package the new upstream release 2024+
Source: python-cmarkgfm Version: 0.8.0-3 Severity: important X-Debbugs-CC: ol...@debian.org Dear Debian python-cmarkgfm package maintainer, A new upstream release of your package 2024.1.14 is available. Besides, the current packaged version is vulnerable to multiple CVEs. Please consider preparing a new packaged version soon. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072826: importlib-resources: Please package new upstream version 6.4.0
Source: importlib-resources Version: 6.0.1-1 Severity: normal X-Debbugs-CC: jo...@freesources.org Dear Debian importlib-resources package maintainer, A new upstream release of importlib-resources, v6.4.0, is available. Please consider packaging it in Debian. I could also help with package upgrading, and may make a team upload in the near future. If you prefer to handle the upgrade yourself, please feel free to let me know by replying this bug report at any time. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072549: gl4es: Broken autopkgtest: unconditionally depends on gcc-multilib
Source: gl4es Version: 1.1.6+ds-1 Severity: grave X-Debbugs-CC: tsu.y...@gmail.com ship...@gmail.com Dear Debian gl4es package maintainers, As currently shown on the package tracker https://tracker.debian.org/pkg/gl4es , package gl4es is experiencing autopkgtest failures on some architectures. Looking deeper, it seems that gl4es unconditionally depends on binary package gcc-multilib, which is not available on certain architectures. I am not sure why we need gcc-multilib in autopkgtest tests. Please adjust the source code accordingly, possibly following one of the following options: * Limit autopkgtest architectures and only run it where gcc-multilib is available. * Rework on autopkgtest script so that gcc-multilib is not needed, and only depends on the native gcc tools. * If gl4es only supports a limited set of architectures, please consider limiting the supported hardware architecture in debian/control file. I have zero knowledge on how gl4es works, so I cannot recommend a best option for you. Please take a look and solve this issue properly. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072548: instead: Please package new upstream release 3.5.1
Source: instead Version: 3.3.2-1.1 Tags: sid X-Debbugs-CC: joe.s...@gmail.com Severity: normal Dear Debian instead package maintainer, A new upstream release of package instead is available. Please consider packaging it in Debian. Feel free to let me know if you need any package sponsorship. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072546: ITP: xcb-util-errors -- Helper library for printing information about X11 errors
Package: wnpp Owner: Boyuan Yang Severity: wishlist * Package name: xcb-util-errors Version : 1.0.1 Upstream Contact: Uli Schlachter * URL : https://gitlab.freedesktop.org/xorg/lib/libxcb-errors * License : Expat Programming Lang: C Description : Helper library for printing information about X11 errors xcb-util-errors is a utility library that gives human readable names to error codes and event codes and also to major and minor numbers. . The necessary information is drawn from xcb-proto's protocol descriptions. . This library is especially useful when working with extensions and is mostly useful for debugging. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072496: download file forbidden
Package: snapshot.debian.org Severity: normal Hi, 在 2024-06-02星期日的 22:49 +0200，jiri ht写道： > > Good morning > I tried to download qcad > > https://snapshot.debian.org/archive/debian/20060824T00Z/pool/main/q/qcad/qcad_2.0.5.0-1-2_amd64.deb > > and this was answer: > Forbidden > You don't have permission to access this resource. > > Apache Server at snapshot.debian.org Port 80 > > > > > > This file and too source and diff files cannot be downloaded. > > I tried to download other files and this is working. > > > Can You answer me or repair it please ? You are reaching the debian-www mailing list, which is not in charge of the maintenance of snapshot.debian.org. The bottom of snapshot.debian.org website says: "Please report bugs against the snapshot.debian.org package." I am doing you a favor to forward your report to a standalone bug report for snapshot.debian.org. Next time, please submit your bug report following the instructions on https://www.debian.org/Bugs/Reporting . Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072476: bookworm-pu: package lua5.4/5.4.4-3+deb12u1
Package: release.debian.org Control: affects -1 + src:lua5.4 X-Debbugs-Cc: lua...@packages.debian.org User: release.debian@packages.debian.org Usertags: pu Tags: bookworm X-Debbugs-Cc: sgolo...@debian.org locutusofb...@debian.org lena.voy...@canonical.com Severity: normal [ Reason ] As described in https://bugs.debian.org/1072460 , the current lua5.4 in Debian Stable (Bookworm) misses several symbols that were supposed to be exported while they still present in the lua headers. This causes undefined references at link time when building some packages. This bug is documented in https://bugs.debian.org/1034800 , and the fix is already present in Debian Testing/Unstable. This will be a non-maintainer upload. The list maintainer, the team as well as the recent uploaders were informed in advance (in Bug#1072460 and the CC list of the current bug report). [ Impact ] If the update is not approved, some software will fail to be built from source in Debian. One of the example is xmake 2.9.1+ (https://tracker.debian.org/pkg/xmake). [ Tests ] Manually tested. [ Risks ] Minimal. The changes only involve manually-maintained symbol table at debian/version-script. Only new symbols are added and no symbol was removed, making this change harmless. [ Checklist ] [X] *all* changes are documented in the d/changelog [X] I reviewed all changes and I approve them [X] attach debdiff against the package in (old)stable [X] the issue is verified as fixed in unstable [ Changes ] Add missing symbols into debian/version-script. For details, see the attached debdiff. Thanks, Boyuan Yang diff -Nru lua5.4-5.4.4/debian/changelog lua5.4-5.4.4/debian/changelog --- lua5.4-5.4.4/debian/changelog 2022-07-17 07:56:01.0 -0400 +++ lua5.4-5.4.4/debian/changelog 2024-06-02 10:34:23.0 -0400 @@ -1,3 +1,11 @@ +lua5.4 (5.4.4-3+deb12u1) bookworm; urgency=medium + + * Non-maintainer upload. + * debian/version-script: Export additional missing symbols for lua 5.4.4. +(Closes: #1034800) + + -- Boyuan Yang Sun, 02 Jun 2024 10:34:23 -0400 + lua5.4 (5.4.4-3) unstable; urgency=medium * Add a patch from upstream which fixes CVE-2022-33099, double free diff -Nru lua5.4-5.4.4/debian/version-script lua5.4-5.4.4/debian/version-script --- lua5.4-5.4.4/debian/version-script 2022-07-17 07:56:01.0 -0400 +++ lua5.4-5.4.4/debian/version-script 2024-06-02 10:32:23.0 -0400 @@ -6,6 +6,7 @@ lua_callk; lua_checkstack; lua_close; + lua_closeslot; lua_compare; lua_concat; lua_copy; @@ -35,6 +36,7 @@ lua_isstring; lua_isuserdata; lua_isyieldable; + luaL_addgsub; lua_len; lua_load; lua_newstate; @@ -66,6 +68,7 @@ lua_resume; lua_rotate; lua_setallocf; + lua_setcstacklimit; lua_setfield; lua_setglobal; lua_sethook; signature.asc Description: This is a digitally signed message part
Bug#1072460: lua5.4: Fix Bug#1034800 for Stable via Bookworm proposed-updates
Source: lua5.4 Severity: important Version: 5.4.4-3 X-Debbugs-CC: lena.voy...@canonical.com locutusofb...@debian.org sgolo...@debian.org Dear Debian lua5.4 maintainers, I was hit by Bug#1034800 when backporting xmake (https://tracker.debian.org/pkg/xmake) to Debian bookworm-backports. The missing symbols is totally a Debian packaging error, and I consider it valid to have the fix included in the Bookworm stable release. As a result, I would like to prepare a stable proposed-update upload that targets https://bugs.debian.org/1034800 . Note that I am not a Lua team member. I will notify you when the stable-pu is submitted to the Release Team for review. If any of you have any concerns at any time, please feel free to drop me an email to pause the process. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072368: libdivide: Please package new upstream release 0.5
Source: libdivide Severity: normal Version: 3.0-1 Tags: sid X-Debbugs-CC: g...@debian.org Dear Debian libdivide package maintainer, A new upstream release of libdivide is available since 2021: https://github.com/ridiculousfish/libdivide/releases/tag/5.0 . Please consider packaging it in Debian. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1007941: megadown: Should we remove this package?
X-Debbugs-CC: vivia.nikolai...@puri.sm p...@debian.org On Sat, 19 Mar 2022 08:22:23 +0800 Paul Wise wrote: > On Fri, 18 Mar 2022 20:06:14 -0400 Boyuan Yang wrote: > > > The package you maintain (megadown, https://tracker.debian.org/pkg/megadown > > ) > > has a longstanding release-critical bug (depends on removed python2), which > > made the package unusable. > > In the latest upstream version the package only needs Python 2 for > MegaCrypter password protected links, not in general and in addition > the fix for using Python 3 is trivial: s/python/python3/ Given that 2 years have passed with nothing has improved, and that the package maintainer had zero activity in Debian, I propose to remove the package after all. There's no reason to keep it if both package maintainer and upstream original author are doing nothing. On the other hand, no other Linux distributions are providing package megadown [1]. As a result, I plan to submit the package removal request to Debian FTP Masters 15 days later (after Jun 15, 2024) if no one objects. [1] https://repology.org/project/megadown/packages Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072367: keynav: Please monitor upstream snapshots on GitHub
Source: keynav Version: 0.20180421~git6505bd0d-3 Tags: sid X-Debbugs-CC: a...@debian.org Severity: important Dear Debian keynav package maintainer, The upstream development of keynav is now happening at https://github.com/jordansissel/keynav , by the same maintainer. Please adjust your debian/watch monitoring script and track upstream GitHub snapshots. Thanks! Best, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072357: pkg-kde-tools: FTBFS on armhf/mips64el/riscv64: Broken tests due to 0.17.2 changes
Source: pkg-kde-tools
Version: 0.17.2
Severity: grave
X-Debbugs-CC: mity...@debian.org
Dear Debian pkg-kde-tools maintainers,
It became clear that the fix in 0.17.2 broke some of the tests related to
time_t on several architectures, and the FTBFS is caused by mixing {time_t}
and {int64_t}. Please check the build logs for more information.
*
https://buildd.debian.org/status/fetch.php?pkg=pkg-kde-tools=armhf=0.17.2=1716721655=0
*
https://buildd.debian.org/status/fetch.php?pkg=pkg-kde-tools=mips64el=0.17.2=1716721905=0
*
https://buildd.debian.org/status/fetch.php?pkg=pkg-kde-tools=riscv64=0.17.2=1716721753=0
Another similar failure in the ports arch (loong64):
*
https://buildd.debian.org/status/fetch.php?pkg=pkg-kde-tools=loong64=0.17.2=1716722208=0
Thanks,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part
Bug#1072292: flvmeta: Please package new upstream release 1.2.2
Source: flvmeta Version: 1.2.1-1 Severity: normal X-Debbugs-CC: neutr...@debian.org Dear Debian flvmeta package maintainer, A new upstream release for flvmeta, v1.2.2, is available at https://github.com/noirotm/flvmeta/releases . Please consider packaging it in Debian. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072291: ITS: libzdb
Source: libzdb Version: 3.1-0.3 Severity: important X-Debbugs-CC: j...@nottheoilrig.com Dear package libzdb maintainer in Debian, After looking into the package you maintain (libzdb, https://tracker.debian.org/pkg/libzdb), I found that this package received no maintainer updates in the past 11 years and misses upstream releases. As a result, I am filing an ITS (Intent to Salvage) request against your package according to section 5.12 in Debian's Developers' Reference [1]. My current plan is to refresh packaging and package the latest upstream release. Please let me know whether you are still willing to maintain this package. According to the criteria listed at [2], I will upload a Non- maintainer Upload (NMU) of this package onto DELAYED/7 after 21 days (Jun 21, 2024) to continue with the package salvaging. If you find it necessary to pause the ITS process, please let me know immediately by replying this bug report. [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging [2] https://wiki.debian.org/PackageSalvaging -- Best Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1072274: ITP: fcitx5-varnam -- Fcitx5 wrapper for Varnam input method.
Hi, 在 2024-05-31星期五的 08:19 +，Anoop M S写道： > Package: wnpp > Severity: wishlist > Owner: Anoop M S > X-Debbugs-Cc: debian-de...@lists.debian.org, anoo...@disroot.org > > * Package name : fcitx5-varnam > Version : 0.0.1 > Upstream Contact: Anoop M S > * URL : https://github.com/varnamproject/varnam-fcitx5 > * License : GPL > Programming Lang: C++ > Description : Fcitx5 wrapper for Varnam input method. > > Fcitx5 wrapper for Varnam(https://www.varnamproject.com) Input Method Engine. > Easily type Indian languages on Linux desktops. > > I would like to join Debian Input Method Team, and package and maintain it. > And I would need a sponsor to upload it as well. Please prepare an initial version first. You can host it on your own Salsa git repo or via mentors.debian.net , or choose whichever platform that is more convenient to you. Please submit a regular RFS request and notify me once you are prepared. If it looks good, I can help to move your git packaging repo to the Salsa Input Method Team namespace, sponsor the upload and add you into the Salsa Input Method Team group. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1071739: marked as done (packages.debian.org: Removal of spam domain from download mirror page)
On Sat, 2024-05-25 at 10:06 +0200, Holger Wansing wrote: > > > Am 24. Mai 2024 20:16:35 MESZ schrieb Holger Wansing : > > > > > > Am 24. Mai 2024 20:10:35 MESZ schrieb Thomas Lange : > > > > > > > > On Fri, 24 May 2024 20:02:35 +0200, Holger Wansing > > > > > > > > said: > > > > > > > Hi Thomas, > > > > you fixed this in master branch. > > > > Are you sure about this? > > > > I somehow seem to remember, that debian-master branch is used for > > > packages.d.o ... > > > you are right, debian-master seems to be the correct branch. > > > I will fix it also in debian-master. > > > > > > Do you know if the branch master is used for anything? > > > > Don't know. > > Maybe we should just make debian-master the default branch (instead of the > master one)? As far as I know the master branch is the shared code between packages.debian.org and packages.ubuntu.com. This is just another indication that packages.debian.org is undermaintained. Seriously, how can I join the team force in making changes to packages.debian.org? I have been looking for a solution since I became a Debian Developer (which is 2017). * The latest pending issue that I care is https://lists.debian.org/debian-www/2023/12/msg00029.html , and it is still not solved yet. * And the continuous 503 Service Unavailable error, which lasted for more than several months and indicates a broken backend instance, is also not resolved: -> % LC_ALL=C wget -vv https://packages.debian.org/unstable/wget2-dev --2024-05-28 15:41:34-- https://packages.debian.org/unstable/wget2-dev Resolving packages.debian.org (packages.debian.org)... 128.31.0.51, 195.192.210.132, 2a02:16a8:dc41:100::132, ... Connecting to packages.debian.org (packages.debian.org)|128.31.0.51|:443... connected. HTTP request sent, awaiting response... 503 Service Unavailable 2024-05-28 15:42:56 ERROR 503: Service Unavailable. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1067303: trash-cli in Debian: test problems again
X-Debbugs-CC: j...@debian.org stef...@karapetsas.com and...@andreafrancia.it Hi Jonathan, Stefano, On Sun, 26 May 2024 14:04:40 +0200 Andrea Francia wrote: > Hi Jonathan and Lucas, > I solved the problem in the new release (0.24.5.26). > > I tested it with these commands: > git clone https://salsa.debian.org/debian/trash-cli.git > cd trash-cli > git remote add upstream https://github.com/andreafrancia/trash-cli > git fetch upstream > git merge 0.24.5.26 > debuild -b -uc -us Can you take a look and prepare a new release into Sid recently? If not, would you mind a NMU into DELAYED/15 with the fix included? Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1071936: hardinfo: Claims transitional package but others depend on it
close 1071936 thanks Hi, On Sun, 2024-05-26 at 11:06 +0200, Michael Rasmussen wrote: > Package: hardinfo > Version: 2.1.5-1 > Severity: important > > Dear Maintainer, > > dpkg -s hardinfo > Package: hardinfo > Status: install ok installed > Priority: optional > Section: oldlibs > Installed-Size: 31 > Maintainer: Boyuan Yang > Architecture: all > Version: 2.1.5-1 > Depends: hardinfo2 > Description: transitional package > This is a transitional package. It can safely be removed. > Homepage: https://github.com/hardinfo2/hardinfo2 > > sudo apt purge hardinfo > The following packages were automatically installed and are no longer > required: > hardinfo2 sysbench > Use 'sudo apt autoremove' to remove them. > > REMOVING: > hardinfo* > > Summary: > Upgrading: 0, Installing: 0, Removing: 1, Not Upgrading: 4 > Freed space: 31,7 kB This is completely normal with no issue. No package depends on package hardinfo so your title makes no sense. It is package hardinfo that depends on hardinfo2. Uninstalling package hardinfo will not affect the status of hardinfo2. That being said, you should explicitly mark package hardinfo2 as manually-installed to ensure that it will not be removed with "auto autoremove". Since the title of your bug report is not the fact, I am considering that the report is invalid and closing this bug. If you have any other valid concerns, please feel free to open a separate bug report. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#487835: [hardinfo] phoronix & hardinfo?
Control: tags -1 +confirmed Control: forwarded -1 https://github.com/hardinfo2/hardinfo2/discussions/16#discussioncomment-9531650 On Tue, 24 Jun 2008 14:50:41 +0200 =?ISO-8859-1?Q?Matthias_Kr=FCger?= wrote: > Package: hardinfo > Version: 0.4.2.3-4 > Severity: wishlist > > --- Please enter the report below this line. --- > Is it possible to make hardinfo using the benchmarks of the phoronix > test suite? > A phoronix-version for Debian can be found at > http://www.phoronix-test-suite.com/index.php?k=downloads . > > Thank you for your fine work! Matthias Krüger On 2024-05-23, the hardinfo(2) upstream expressed interest in utilizing the Phoronix test suite. Keeping it as a wishlist bug. For more details, please see https://github.com/hardinfo2/hardinfo2/discussions/16#discussioncomment-9531650 . However, given that the phoronix test suite has some difficulties in being packaged in Debian in the past, I (as a Debian package maintainer) do not expect this to be effectively implemented in Debian anytime soon. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1071521: ukui-screensaver: predictable filenames under /tmp with system()
Hi. This bug is same as1064340. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064340 We will fix it and upload at soon. Thanks. xibowen
Bug#1071670: ITP: libperl-critic-plicease-perl -- Perl module that includes Perl::Critic policies used by Plicease
Package: wnpp Owner: Fernando Yang Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org * Package name: libperl-critic-plicease-perl Version : 0.06 Upstream Author : Graham Ollis * URL : https://metacpan.org/release/Perl-Critic-Plicease * License : Artistic or GPL-1+ Programming Lang: Perl Description : Perl module that includes Perl::Critic policies used by Plicease The Perl::Critic::Policy::Plicease policies are an eclectic collection of Perl::Critic policies. Some policies are application specific, you should review and include them only on a case by case basis. The package will be maintained under the umbrella of the Debian Perl Group. -- Generated with the help of dpt-gen-itp(1) from pkg-perl-tools.
Bug#1071373: ITS: hardinfo
Hi Simon, On Wed, 2024-05-22 at 16:38 +, Simon Quigley wrote: > Hello, > > Firstly, I would like to thank you and others for your persistence in > this effort. I am glad that there is interest in this package again. > > My original interest in maintaining hardinfo was due to its inclusion in > Lubuntu, prior to our switch to LXQt. It was one of the first packages I > worked on as an "up and coming" Debian Developer, and to my > understanding, the packaging as of 2018 was fully up to date and > standards-compliant. > > That being said, I no longer have as much interest in this package as I > used to. Boyuan, please go ahead and take over maintainership if you are > interested. My only request is that I stay as a co-maintainer, since > this package has sentimental value to me. > > Thank you again for your efforts. Proceed. Thank you for the detailed reply. I will proceed with package uploads and keep your name in the uploader list. Thank you for all your past work! Best, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1071553: RM: comparepdf -- RoQA; Dead Upstream; Orphaned; Unmaintained
Package: ftp.debian.org Control: affects -1 + src:comparepdf User: ftp.debian@packages.debian.org Usertags: remove X-Debbugs-Cc: by...@debian.org Severity: normal Dear Debian FTP Masters, Please consider removing package comparepdf from Debian Sid archive. * It has been orphaned in https://bugs.debian.org/1070967 . * It received no maintainer upload in the past 12 years. * Its upstream is now dead (the original author has withdrawn all his open-source software release due to EU Cyber Resilience Act). * Its popcon is relatively low (~120). * It has no reverse dependencies and reverse build-dependencies. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1071528: ITP: hardinfo2 -- Hardinfo2 offers System Information and Benchmark for Linux Systems
On Mon, 2024-05-20 at 15:55 -0400, Jeremy Bícha wrote: > On Mon, May 20, 2024 at 11:09 AM Lucas Castro wrote: > > Package: wnpp > > Severity: wishlist > > Owner: Lucas Castro > > X-Debbugs-Cc: debian-de...@lists.debian.org > > > > * Package name : hardinfo2 > > Version : 2.1.2 > > Upstream Contact: Name > > * URL : https://hardinfo2.org/ > > * License : GPL-2 > > Programming Lang: C > > Description : Hardinfo2 offers System Information and Benchmark for > > Linux Systems > > > > Hardinfo2 is based on hardinfo, which have not been released >10 years. > > Hardinfo2 is the reboot that was needed. > > > > Hardinfo2 offers System Information and Benchmark for Linux Systems. It is > > able to > > obtain information from both hardware and basic software. It can benchmark > > your system and compare > > to other machines online. > > > > Features include: > > - Report generation (in either HTML or plain text) > > - Online Benchmarking - compare your machine against other machines > > > > Status > > -- > > - Capabilities: Hardinfo2 currently detects most software and hardware > > detected by the OS. > > - Features: Online database for exchanging benchmark results. > > - Development: Currently done by contributors, hwspeedy maintains > > > > Hardinfo2 is based on hardinfo, which have not been released >10 years. > > Hardinfo2 is the reboot that was needed. > > Please see https://bugs.debian.org/1071373 (ITS: hardinfo) and > coordinate with Boyuan Yang on updating hardinfo. Currently we are under coordination. We plan to take substantial actions only after the ITS is cleared, and whether the name of the future package eventually is hardinfo or hardinfo2 will be determined later. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1035759: ITA: sniproxy -- Transparent TLS and HTTP layer 4 proxy with SNI support
Control: retitle -1 RFA: sniproxy -- Transparent TLS and HTTP layer 4 proxy with SNI support Control: noowner -1 X-Debbugs-CC: r...@ringlet.net On Fri, 12 May 2023 14:09:09 +0300 Peter Pentchev wrote: > control: retitle -1 ITA: sniproxy -- Transparent TLS and HTTP layer 4 proxy > with SNI support > control: owner -1 ! > > Thanks for your work on sniproxy over the years! > > G'luck, > Peter > > -- > Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com > PGP key: http://people.FreeBSD.org/~roam/roam.key.asc > Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 Hi, You expressed the interest to take over package maintenance for sniproxy a while ago. However, no package upload was made in the last 9 months. As a result, I am reverting the ITA status back to the RFA report. If you are still willing to adopt this package, please feel free to make another package upload to take over package maintenance. Thanks! Best, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1071373: ITS: hardinfo
Source: hardinfo Version: 0.5.1+git20180227-2.1 Severity: important X-Debbugs-CC: tsimo...@debian.org Dear package hardinfo maintainer in Debian, After looking into the package you maintain (hardinfo, https://tracker.debian.org/pkg/hardinfo), I found that this package received no maintainer updates in the past 6 years and was not in good shape. As a result, I am filing an ITS (Intent to Salvage) request against your package according to section 5.12 in Debian's Developers' Reference [1]. My current plan is to fix RC bugs and work with the hardinfo2 upstream. Please let me know whether you are still willing to maintain this package. According to the criteria listed at [2], I will upload a Non- maintainer Upload (NMU) of this package onto DELAYED/7 after 21 days (Jun 08, 2024) to continue with the package salvaging. If you find it necessary to pause the ITS process, please let me know immediately by replying this bug report. [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging [2] https://wiki.debian.org/PackageSalvaging -- Best Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1071279: pkg-kde-tools: Nondeterministic, broken batchpatch outcome
Source: pkg-kde-tools Version: 0.17.1 Severity: important X-Debbugs-CC: p...@debian.org mity...@debian.org delta...@debian.org Dear Debian pkg-kde-tools developers, As discussed in OFTC #debian-qt-kde, while utilizing pkg-kde-tools in the packaging of src:taglib, I found that the batchpatch functionality is not yielding deterministic results: = [~/src/debian/multimedia-team/taglib] [debian/experimental *] -> % git rev-parse HEAD ; for i in 1 2 3 4 5 6 7 8 9; do git restore debian/libtag2.symbols ; pkgkde-symbolshelper batchpatch -v 2.0.1 < ./taglib_experimental_logs/* > /dev/null 2> /dev/null ; git diff | wc -l ; done 3609f305d309fe0dd4e24b9579ed80ec06555f69 0 22 22 13 31 22 0 36 31 == Steps to reproduce: 1. git clone https://salsa.debian.org/multimedia-team/taglib 2. cd taglib/ 3. wget 'https://salsa.debian.org/byang/pkg-kde-tools-bugreport-20240517/-/raw/main/taglib_experimental_logs_20240517.tar.xz?ref_type=heads=false' -O a.xz 4. tar xavf a.xz 5. git checkout 3609f305d309fe0dd4e24b9579ed80ec06555f69 6. git rev-parse HEAD ; for i in 1 2 3 4 5 6 7 8 9; do git restore debian/libtag2.symbols ; taskset 1 pkgkde-symbolshelper batchpatch -v 2.0.1 < ./taglib_experimental_logs/* > /dev/null 2> /dev/null ; git diff | wc -l ; done Expected behavior: The batchpatch invocations always yield the same result (and line numbers). The current behavior: The batchpatch invocations yield different outputs (different line numbers). Please consider looking into it. Thanks! Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#1071239: gtkterm: Please package new version 1.3.1
Source: gtkterm Severity: important X-Debbugs-CC: wvdak...@wilsoft.nl Version: 1.2.1-1 Tags: sid Dear Debian gtkterm maintainer, As shown in https://github.com/wvdakker/gtkterm/tags , the gtkterm upstream has released a new upstream version 1.3.1. Please consider packaging it since it contains the fix to RC bug https://bugs.debian.org/1066645 . If you need any upload sponsorship, please let me know. Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part
