On 2024-08-22 14:16, Andreas Tille wrote:
> Hi,
>
> I intended to fix bugs #1066354 and #836007 of safecat as Bug of the
> Day[1]. While #1066354 gcc-14 error seemed to be a low hanging fruit
> it turns out I need help to solve some linker issue[2]:
> [snip]
I noticed the change of upstream to [
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "kcollectd":
* Package name : kcollectd
Version : 0.12.1-1
Upstream contact : Antonio Russo
* URL : https://www.antonioerusso.com/projects
8EED5
> gpgv: Can't check signature: No public key
> uscan die: OpenPGP signature did not verify. at
> /usr/share/perl5/Devscripts/Uscan/Output.pm line 77.
I assume that means it is actually verifying the signature.
Should I add a lintian override to capture this situation?
1) unstable; urgency=medium
.
* Initial release (Closes: #1041718)
Best,
Antonio Russo
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
Most notably, upstream
has dropped support for
inkscape <1.3, and I am tracking that change here.
Best,
Antonio Russo
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
Thanks for for the couple replies I got!
On 2023-09-03 08:23, Bo YU wrote:
> Hi Antonio！
>
> On Sun, Sep 3, 2023 at 2:30 AM Antonio Russo wrote:
>>
>> Hello,
>>
>> I opened an ITP-closing RFS bug about a month and a half ago. It's got 0
>> replies.
Hello,
I opened an ITP-closing RFS bug about a month and a half ago. It's got 0
replies.
Is it OK for me to try to bump this? I would have at least hoped to get someone
to say
"I don't think this is fit for debian." before giving up on it.
Best,
Antonio
OpenPGP_0xB01C53D5DED4A4EE.asc
Descrip
urgency=medium
.
* Initial release (Closes: #1041718)
Best,
Antonio Russo
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
bian.net/debian/pool/main/k/keepassxc-proxy-client/keepassxc-proxy-client_0.1.6-1.dsc
Changes for the initial release:
keepassxc-proxy-client (0.1.6-1) unstable; urgency=medium
.
* Initial release (Closes: #1041718)
Best,
Antonio Russo
OpenPGP_0xB01C53D5DED4A4EE.asc
Description
er visible.
Best,
Antonio Russo
Hello,
> Please change the email address on this bug report from
> send_only.aurin...@auroville.org.in to b...@charlesmatkinson.org
See controlling the Debian BTS [1].
> I tried hard to make a source .deb but did not manage to do so.
> Would you like me to share the system I use to create the .
Hello Wookey,
On 2/3/21 6:44 AM, Wookey wrote:
> On 2021-02-02 23:42 -0700, Antonio Russo wrote:
>
> I've tested the builds on arm64 and armhf. I'm short of non-headless
> boxes here to test the X functionality on.
>
> So I've uploaded to get the migration
ardware to test this on, so, while I can
confirm that this builds (and works) on amd64, it would be nice if someone
could check that it works correctly on arm.
Best,
Antonio Russo
[1] https://tracker.debian.org/pkg/xpra
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956822
Package: sponsorship-requests
Severity: normal
X-Debbugs-Cc: aeru...@aerusso.net
Dear mentors,
I am looking for a sponsor for my package "kcollectd"
* Package name: kcollectd
Version : 0.12.0-1
Upstream Author : Antonio Russo
* URL
or package cleanup (bumped to the
new standards version 4.5.1 and aligning gbp.conf with my salsa layout).
Best,
Antonio Russo
OpenPGP_0xB01C53D5DED4A4EE.asc
Description: application/pgp-keys
OpenPGP_signature
Description: OpenPGP digital signature
ion of the warning about upstream
tarball signing and missing tests. I am still interacting with upstream to
get signed releases [1].
**My last upload is still in the NEW queue.** Should I wait for it to clear
before uploading my next revision?
Best,
Antonio Russo
[1] https://github.com/texte
package is lintian clean, with the exception of the warning about upstream
tarball signing and missing tests. I am still interacting with upstream to
get signed releases [1].
Best,
Antonio Russo
[1] https://github.com/textext/textext/issues/231
to sharpen the
dependencies and update by email address.
The package is lintian clean, with the exception of the warning about upstream
tarball signing and missing tests. I am still interacting with upstream to
get signed releases [1].
Best,
Antonio Russo
[1] https://github.com/textext/textext/
pt-library warning appears to be an issue with
dh_sphinxdoc (see [1], the last email dated Jul 13 from Alexis Murzeau).
I have not set up autopkgtests.
The packaging is maintained in Debian salsa [2], and builds in pbuilder.
Best,
Antonio Russo
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug
not close #964593 in the changelog, but should otherwise be
identical.
The mentors page often has trouble identifying a new version, but does appear
to be
showing up correctly now. Please be wary of this when downloading the package.
Best,
Antonio Russo
[1] https://salsa.debian.org/debian/pk
Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: pkg-kde-t...@alioth-lists.debian.net
Dear mentors,
I am looking for a sponsor for my package "kcollectd":
* Package name: kcollectd
Version : 0.11.99.0-1
Upstream Author : Antonio Russo (myse
Hello again,
Is there anything I can do to help move this process along?
Are you still willing to sponsor an upload for this package?
Thank you,
Antonio Russo
Just wanted to do a quick follow up:
Is there anything else you would like me to do to prepare this package
for submission?
Thanks,
Antonio
On 2020-06-10 18:30, Antonio Russo wrote:
> On 2020-06-10 08:53, Boyuan Yang wrote:
>> Signed tags/tarballs don't matter; they are totally
On 2020-06-10 08:53, Boyuan Yang wrote:
> Signed tags/tarballs don't matter; they are totally optional. Your
> debian/watch file is using mode=git, which is totally fine; however,
> you may also opt to monitor the github releases page like other Debian
> packages.
Understood. I've left it untouche
tream regarding signed git tags [4].
Thank you very much for looking at this,
Antonio Russo
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961741
[2] https://mentors.debian.net/package/inkscape-textext
[3] https://salsa.debian.org/aerusso-guest/textext
[4] https://github.com/textext/textext/i
pe extensions I have found.
The package is lintian clean, with the exception of the warning about
upstream tarball signing (and tests) [1]. I'm currently interacting with
upstream to get signed releases [2].
The packaging is maintained in Debian salsa [3], and builds in pbuilder.
Best,
e warning about
upstream tarball signing (and tests) [1]. I'm currently interacting with
upstream to get signed releases [2].
The packaging is maintained in Debian salsa [3], and builds in pbuilder.
Best,
Antonio Russo
[1] https://mentors.debian.net/package/inkscape-textext
[2] https://github
; Hi,
>
> since you used mentors.d.n to keep your package, please consider using
> the template it provides to send the RFS, so it is nicely formatted.
>
Thanks for taking a look. I'm still getting the hang of this.
> On Sat, Oct 12, 2019 at 08:53:18PM -0600, Antonio Russo wrote:
&
times. Please see my ITP [2],
mentors upload [3,4], and salsa packaging [5].
There are a couple outstanding issues, most importantly I don't understand
how Inkscape is getting dh_python3 to py3compile its extensions (and not
mine). I'd appreciate any help on that end, too.
Thank you,
Ant
>> I've changed the maintainer to be Qt/KDE, and changed my role to uploader
>> (and I've added you there as well, is that appropriate?).
>
> No please remove myself from uploaders, as I'm only the sponsor. I do not
> intend at the moment to care about new versions of kcollectd. You care about
>
reassign 935485 wnpp
retitle 935485 RFS: kcollectd/0.10.2-1 ITP -- simple collectd graphing
front-end for KDE
thanks
Changed to WNPP ITP bug per above.
kind of
UI software).
Is anyone here willing to sponsor this package, offer any criticism of
the package, or direct me to a place where I might get such help?
Thank you,
Antonio Russo
[1] https://bugs.debian.org/935223
[2] https://gitlab.com/aerusso/kcollectd
[3] https://bugs.debian.org/935485
oaded to mentors [5] [6].
Thank you,
Antonio Russo
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927455
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814935
[3] https://gitlab.com/aerusso/kcollectd
[4] https://salsa.debian.org/aerusso-guest/kcollectd
[5] https://mentors.debian.net/pa
I have a port of kcollectd to qt5, and I filed a bug against this
package (months ago), with an offer to maintain it.
How exactly can I find a sponsor to help me maintain an orphaned Debian package?
Thanks,
Antonio Russo
Forwarded Message
Subject: Bug#927455 closed by Debian
Package: src:kcollectd
Version: 0.9-5+b1
Severity: normal
--- Please enter the report below this line. ---
Upstream has been silent for almost a decade now. I have decided to fork and
maintain kcollectd [1].
I have a bugfix-only release, 0.9.1, which includes the current Debian patch
set, and f
On 6/22/18 4:17 AM, Fabian Grünbichler wrote:
>
> as promised, and unfortunately delayed a bit longer than I wanted.
> thanks for the initial push - some of the points are more for a
> discussion with upstream regarding their inclusion of some variant of
> this, some are for debian experimental.
>
#x27;d appreciate feedback.
Thanks,
Antonio Russo
[1] https://salsa.debian.org/aerusso-guest/zfs/commits/debian/git
[2] https://github.com/zfsonlinux/zfs/pull/7571
[3] https://github.com/zfsonlinux/zfs/pull/7597
rs, but
they're very busy and have not replied in the last few weeks.
Would it be possible to have someone look over the changes I've made
and/or make suggestions as to how I could get these changes incorporated
into Debian?
Thanks,
Antonio Russo
[1] https://github.com/aerusso/pkg
38 matches
Mail list logo
