Phil,
I am currently in the middle of travel so I can't access stable internet. As
soon as I get to my destination I'll reupload to mentors with an adjusted
policy version. Though it might be a few hours.
Thomas
Sent from my Galaxy
Original message
From: Phil Wyett
Dat
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "nginx-snippets":
* Package name : nginx-snippets
Version : 1.0
Upstream contact : Thomas Ward
* URL :https://salsa.debian.org/teward/ngin
Based on discussion in
https://salsa.debian.org/nginx-team/nginx/-/issues/23 we believe we can
fix this by adding a `ConditionFileIsExecutable` line to the service file.
There is a pending merge request with this change on the Salsa repository.
Package: wnpp
Severity: wishlist
Owner: Thomas Ward
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name : nginx-snippets
Version : 1.0
Upstream Contact: Thomas Ward
* URL : https://salsa.debian.org/teward/nginx-snippets
* License : GPL-3.0
Forwarded upstream as https://github.com/chris2511/xca/issues/633
Sent from my Galaxy
XCA 2.8.0 is now pending in the FTP queue, and is also present on Salsa.
This includes the new 2.8.0 release of XCA as well as switching from Qt5
to Qt6, which was slated to land with 2.6.0-3 but were never made
available/uploaded. And of course 2.7.0 didn't make it in because of my
busy sche
Note that the Upstream Contact is the Copyright holder. However, this is a
public open source project now on GitHub, and members of the project have
already OK'd packaging this for Debian - refer to
https://github.com/pop-os/repolib/issues/79 where I ask if there is any issues
with me packaging
Package: wnpp
Severity: wishlist
Owner: Thomas Ward
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name : repolib
Version : 2.0.0
Upstream Contact: Ian Santopietro
* URL : https://github.com/pop-os/repolib
* License : GPL 3.0 and LGPL 3.0
Programming
Note that I have been having issues getting the newer XCA to build in the
source tree, then I had to deal with end-of-year stuff for my dayjob that
prevented me from gettimg back to this.
This is on my schedule to target end of the week to hopefully get something
pending in Salsa
Sent from m
nginx depends on nginx-common, which depends on nginx, which...
Ultimately this is a depends loop. Which I'll fix and push to Unstable shortly
by removing nginx-common Depends: nginx.
Thomas
Hello!
Currently, when we put a Pre-Depends on nginx-common for nginx in, we get a
Lintian failiure case:
{"type"=>"failure", "message"=>"redundant-installation-prerequisite (in section
for nginx) Depends -> Pre-Depends nginx-common (= ${source:Version})
[debian/control:24]"}
We already have
> I don't understand why nginx-common depends on nginx.
> If it wasn't, it would be installed before nginx naturally.
I don't think it should, that's my thought.
HOWEVER I did discover that nginx **has a direct Depends` on nginx-common.
Because it has a direct Depends on nginx-common it makes se
For the purposes of argument, the reason nginx I don't think pre-depends on
nginx-common is because nginx itself can be pulled in by other packages that
then want to maintain their own configuration and roll their own NGINX
configuration files.
While I definitely agree it should pre-depend on n
Fix added to Salsa repository for Unstable, pending tag added.
Thomas
Your updated version here fails too. When you look at the verbose data, it
catches a million quotes and still fails.
I rewrote the debian/watch file and fixed it in Salsa using a variation of
https://wiki.debian.org/debian/watch#GitLab and its updated April 2024
patterns, specifically to catch
A fix has been made available in Salsa, however as this is a very minor issue I
don't think we're going to release -3 of the package just for fixing the
d/watch file.
Tags: -1 - patch
Tags: -1 + confirmed
Hello!
The patch you've provided does not match any files on the specified tags or
releases page for the Tor Browser launcher tooling on the Tor gitlab.
As such I am removing the "patch" tag here because we don't have a working
updated d/watch file yet.
I can confirm this happens during a rebuild in my own sbuild chroots.
The core issue appears to be that when the make rules call help2man, the
version string provided is an empty string. Digging into d/rules, it looks
like DEB_VERSION_UPSTREAM_REVISION is unset during the process, which is why
Not a mentor but who's the upstream author / contact? (It isnt filled in in
your request)
Sent from my Galaxy
Original message
From: Jörg Frings-Fürst
Date: 7/21/24 14:09 (GMT-05:00)
To: sub...@bugs.debian.org
Subject: Bug#1076671: RFS: uriparser/0.9.8+dfsg-2 -- documenta
Control: tags -1 + pending
This is a leftover from the change from upstream to CMake among other things.
A fix has been added to debian/clean in Salsa for 2.6.0-2 (currently
unreleased) that will fix double-building and properly clean things.
Refer to
https://salsa.debian.org/debian/xca/-/comm
Source: xca
Severity: minor
Control: submitter -1 tew...@ubuntu.com
It was suggested by Mattia Rizzolo that XCA may build successfully against
qtbase5-dev instead of the specific Qt SQL library.
This is a bug that will remain open while this is investigated as to whether
this change works or no
reqs/patches to address the d/watch
and d/control issues, however I am not going to handle the outdated
software problem.
Thomas Ward
[1]: https://github.com/eteran/edb-debugger/releases
[2]: https://wiki.debian.org/debian/watch#GitHub
[3]: https://udd.debian.org/lintian/?packages=edb
For everyone's awareness: this same t64 transition is going on downstream in
Ubuntu, and I'm also tracing rebuilds, etc. with changed dependencies there as
well which are being done by other core devs there, so those changes may
trickle back up into Debian here.
Thomas
(this email is the one
The only package that has a changed name that I can see is `libqt5sql5` to
`libqt5sql5t64`. I have already put this in the revisions in Salsa at the
moment.
If `libqt5help5` has a rename pending to `libqt5help5t64` and that's not yet in
Unstable, then I can't make that revision safely.
Thom
Harald, check and see if the latest version uploaded (2.5.0) fixes the
issue. Note that I have been without a signing key for a bit due to
unforseen circumstances, so it took a bit longer to get it to land and
tested.
Package: sponsorship-requests
Severity: normal
Control: submitter -1 tew...@ubuntu.com
Dear mentors,
*Note: While I have DM status and can upload, there is a situation where
my signing key privkey is irrecoverable, due to computer death and the
destruction of my yubikey holding the privkey as
nt from my Galaxy
Original message
From: Jérémy Lal
Date: 8/29/23 05:16 (GMT-05:00)
To: Thomas Ward , 1050...@bugs.debian.org
Cc: Bastian Germann
Subject: Re: [Pkg-nginx-maintainers] Bug#1050186: Bug#1050186:
libnginx-mod-http-lua: depends on obsolete pcre3 library
Le lun. 21 août
Bastian:
As I understand the module, for over a year now the latest Lua module
from OpenResty requires LuaJIT to actually compile. See
https://salsa.debian.org/nginx-team/libnginx-mod-http-lua/-/blob/main/debian/control#L8
where this is in the build deps.
I have not tested removing the PCRE
All:
See the Lua NGINX module issue here in upstream:
https://github.com/openresty/lua-nginx-module/issues/1984
This has been an open issue since December 2021, and there has *NOT*
been massive movement yet upstream towards PCRE2 support.
The last info on that bug from July 13th indicates t
I would suggest that we move the configuration files out of `nginx` main
and keep it as a separate binary package, whether we call it
`nginx-common` or `nginx-config` or whatever.
In either case, there are benefits to having the configuration file
*separate* from the binaries (see Apache where
I'm looking after this package a bit downstream in Ubuntu, and have
multiple packages here in Debian that I'm DM for.
I'd be happy to comaintain the package with the team and everyone else,
in fact I have an upload prepared for the latest torbrowser-launcher and
would be happy to work with the
Unless we have confirmed that these 'flavors' don't rely on non-dynamic modules
that need compiled in at compile time I generally am in agreement. There were
options enabled at some flavors that are not invseparately packaged modules
because they needed to be in the executable at compile time.
Response from upstream:
The pastebinit -P option seems to now require an argument even
though the option didn't require one before...
Yes, because 1.) this allows one to both enable and disable private
pasting via command-line option which wasn't possible before, and 2.)
there are pas
Package: pastebinit
Severity: serious
Version: 1.6.2-1
(Serious severity selected by Package Maintainer - unfit for release in
current state)
When using pastebinit to post to the Debian pastebin (default), the
system returns a plain "https://paste.debian.net"; link and NO link to an
actual p
nstall nginx first, change the
configuration, disable IPv6, then reboot. That's how you *should* do
things with an autodeploy script).
Thomas Ward
Ubuntu Core Developer (https://launchpad.net/~teward)
Debian Maintainer (for nginx package among others)
On 10/7/22 14:37, Stuart Culligan
Source: qtchooser
Severity: wishlist
It was determined from
https://salsa.debian.org/qt-kde-team/qt/qtchooser/-/merge_requests/2 and
a downstream Ubuntu bug on Qt6 not working that QtChooser is dead
upstream on purpose.
If it is dead upstream on purpose and should NOT work with Qt6, could we
Source: mitmproxy
Severity: important
MITM Proxy version 8.0 has been available for some time now, and is not
packaged. Updating the package will fix the two CVE bugs that are
present in MITM Proxy here in the packaging.
The version of MITM Proxy that is packaged was last updated in December
Control: tags -1 + pending
This was a typo introduced in the fixing of the QA state in the
packaging when myself and Jan were given maintainer status.
My bad! I've got a fix pending in Salsa, but I don't think it will get
uploaded on its own until we have other things ready to go as well
(b
Because it does make sense that this hasn't been handled for 4+ years
that upstream has no intention to support this.
Thomas
On Sun, 3 Apr 2022 00:49:53 +0200 =?UTF-8?B?SsOpcsOpbXkgTGFs?=
wrote:
> On Sun, Apr 3, 2022 at 12:21 AM Thomas Ward
wrote:
>
> > Source: lu
Source: rlwrap
Severity: important
Hello.
The rlwrap package has a seriously outdated version of rlwrap and
multiple bugs open against it indicating it needs to be updated to a
newer version of rlwrap in order to fix those.
The last activity by the sole listed maintainer, Mike Miller
, show
homas,
On Wed, May 04, 2022 at 07:22:22PM +0000, Thomas Ward wrote:
You are correct - bage@ saying this was fixed and should've been
included in changelogs in the RFS threw me off. The fix requires
new commands and essentially 'functionality' added which is probably
why it was
ait for 1.22 release of NGINX OSS.
Thomas
-Original Message-
From: Salvatore Bonaccorso On Behalf Of
Salvatore Bonaccorso
Sent: Wednesday, May 4, 2022 15:16
To: 991...@bugs.debian.org; Thomas Ward
Cc: Moritz Mühlenhoff
Subject: Re: Bug#991328 closed by Thomas Ward ()
Control: reo
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "nginx":
* Package name : nginx
Version : 1.20.2-1
Upstream Author : Igor Sysoev
* URL : https://nginx.org
* License : BSD-4-clause, Expat, BSD-2-clause, BSD-3-clause
* Vcs : https://salsa.deb
or segfault in nginx core >=
1.15.0
when libnginx-mod-http-lua is loaded and init_worker_by_lua* is used.
* d/control: Add mips64el,ppc64,kfreebsd-amd64 to list of luajit
platforms.
* d/control: fix Homepage nginx.net -> nginx.org (Closes: #976158)
.
[ Thomas Ward ]
* d/wat
Control: tags -1 pending
This will be fixed in -9 when updated packaging is uploaded.
A merge request [1] included a downgrade of the Lua module to the last
known functional version, which solves the FTBFS problem as that version
of the Lua module can still build on s390x due to the older libl
Can I suggest that this be rejected as it has no review from the Debian
Maintainers Team (on git or otherwise)? (I've recently been added as a
maintainer on the Git side of this for the Salsa repo, though not an
uploader *yet* with my DM rights, but as we manage this on Git VCS...
this should b
Source: luajit
Severity: wishlist
Please support s390x if possible. NGINX's Lua module support depends on
libluajit exclusively now, and would need s390x support for proper support.
Thomas
So, it seems that this problem leads to a deeper problem, one with a
fix, and one that leaves the s390x support at an impasse.
Firstly, mips64el has libluajit available. We can fix the mips64el
builds by adding libluajit-5.1-dev as an explicit dependency for mips64el.
However, we can NO LONG
Source: nginx
Severity: wishlist
NGINX 1.18 was released back in 2020. This is substantially older than
Upstream versions, which released 1.20 in April of 2021 (nearly a year ago).
Please upgrade the package version in Debian to 1.20 as soon as
possible, and then when NGINX 1.22.0 releases th
source: nginx
found: 1.18.0-8
severity: serious
The builds for mips64el and s390x are failing to build and thus failing
to allow 1.18.0-8 to migrate.
Both error with luajit not found errors.
cc -c -fPIC -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security
ere during
this build. It also appears to run and work fine from the tests I've
done locally in an Unstable VM.
Regards,
Thomas Ward
.
Regards,
--
Thomas Ward
Package: lintian
Version: 2.111.0~bpo11+1, 2.114.0
I discovered during compilation of a (slightly) older package that still uses a
debhelper (>= 12)
compatibility with a debian/compat file stating 12 that the tag
missing-build-dependency-for-dh-addon
is unable to detect the fact that dh-autorec
Source: xca
Version: 2.3.0-1
Severity: grave
Tags: ftbfs experimental upstream
XCA 2.3.0 and 2.4.0 do NOT support OpenSSL 3.0 and fails to build when
put against the OpenSSL 3.0 libraries. Git has 2.4.0 staged in
UNRELEASED form for now, however there is no OpenSSL 3.0 support available.
We had similar discussions on this type of issue downstream in Ubuntu
[1] and after extensive discussions it was suggested that if someone
wants to use network-online.target for this they do an override in their
SystemD.
Given that network-online.target is not well defined, it was determined
Just for awareness: the canonical upstream repository *is* the OpenResty
lua-nginx-module repository you've linked.
However, keep in mind that there is a new dependency that the Lua module
will need going forward for Debian - `resty-core` which pulls in a ton
of extra OpenResty code which is n
:
> On Thu, Jan 31, 2019 at 04:36:45PM -0500, Thomas Ward wrote:
> > The GeoIP module is a core module in NGINX upstream. Keeping this in
> > mind, it's just packaged here as a dynamic module.
> >
> > For reference purposes, I have forwarded this bug report to ng
es
to handle issue with autoheader changes and build failures.
- debian/control: Replace Recommends postgresql dependency to
libqt5sql5-psql
Regards,
--
Thomas Ward
Package: libnginx-mod-nchan
Severity: serious
Version: 1.18.0-3
Copied from Downstream bug in Ubuntu on Launchpad
(https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1874831)
post-merge (where we merged from Debian into Ubuntu):
---
The libnginx-mod-nchan package which is built from the ngin
Notes: rejected downstream in Ubuntu for Security concerns (BREACH, etc.)Sent
from my Sprint Samsung Galaxy Note10+.
Original message From: Jérémy Lal Date:
6/30/20 15:36 (GMT-05:00) To: Debian Bug Tracking System
<919...@bugs.debian.org> Subject: Bug#919320: nginx-extras: Wo
Downstream in Ubuntu where nvinx-core originated it is its own binary - not
depended upon nginx-core. The nginx dynamic modules are also "OR" depended -
such that it needs one of the flavors installed not all of them. Consider
doing that to make the modules not have circular depends.Sent from
Tags: -1 + pending
Updated in VCS, but I have other things on my radar so at the moment I
can't push an update (E:OtherObligations).
Marking this as in-progress/pending regardless for now.
Upstream has incorporated a fix to this themselves. Upstream git commit
located
at:https://github.com/chris2511/xca/commit/76e3f86783b5b472c5601750d2ddca615570fffd
Will be incorporating this into the Salsa VCS packaging later today, and
will incorporate this fix into the next package release.
Th
Looks like OpenSSL is at fault, refer to
https://github.com/openssl/openssl/pull/10029Sent from my Sprint Samsung Galaxy
Note10+.
This was subsequently fixed in OpenSSL 1.1.1e - possibly this fix needs
included in OpenSSL in Unstable in order to fix the mismatches as this looks to
be fully OpenSSL at fault.(Info obtained from upstream bug)
null
Forwarded upstream:
https://github.com/chris2511/xca/issues/191
On 4/26/20 5:36 AM, Sander van Grieken wrote:
> Package: xca
> Version: 2.2.1-1
> Severity: normal
>
> XCA shipped oids.txt mismatches against openssl defined OIDs, causing two
> popups to appear at application startup.
>
> Warnings a
esent-Date:Sat, 28 Mar 2020 07:33:09 +0100
Resent-From:Bart Martens
Resent-To: Thomas Ward
Date: Sat, 28 Mar 2020 07:22:58 +0100
From: Razer raz
To: Bart Martens
For sure, I'm waiting for it since a while. Thanks for your interest !
Just for the record, I work intensiv
d by stdeb 0.8.5
Comaintainer in Uploaders is CC'd on this message; they do not have upload
rights either and any uploads from them will also go through Sponsors, however
I'm taking lead on the Debian package.
Regards,
--
Thomas Ward
Package: wnpp
Severity: wishlist
Owner: Thomas Ward
Package name : bubblemail
Version : 0.5
Upstream Author : Razer
URL : https://bubblemail.free.fr/
License : GPL-2
Programming Lang: Python
Description : An extensible mail notification service
s has been requested by others to me
on Freenode IRC.
Regards,
--
Thomas Ward
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "xca". This is a new upstream
version release.
* Package name : xca
Version : 2.2.1-1
Upstream Author : Christian Hohnstaedt
* URL : https://hohnstaedt.de/xca/
* License : BSD-3-clause
* Vcs
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "vmfs6-tools"
* Package name: vmfs6-tools
Version : 0.1.0-3
Upstream Author : Upstream Author : Thomas Ward and
others
* URL : https://salsa.
https://bugs.debian.org/943705 has been reported as the core cause.
The builds are being give-backed now, as we are fairly sure that the
issue reported in the FTBFS bug here was due to debhelper issues which
were fixed on the 7th, five days after the autobuilds were triggered.
I'm going to ma
.
Regards,
--
Thomas Ward
Hello, and thank you for the patch!
I'm making sure this builds before uploading for sponsoring, and have
given you credit in the changelogs. Thanks!
I ran this exact package through a rebuild in an sbuild environment just
now, and cannot reproduce your FTBFS. Automated build(s) failed to
reproduce this in a pbuilder environment as well.
Did you do anything to the package to make it trigger this FTBFS? What
Arch and Distro did you build a
Possibly. Perhaps I should go the Policy route and inquire whether we
should consider CDBS obsolete by later versions of Debian policy...
Thanks for the response though! :)
Thomas
On 11/6/19 6:03 PM, Chris Lamb wrote:
Hi Thomas,
Nope, all CDBS packages compat >> 10 FTBFS if using the cd
Nope, all CDBS packages compat >> 10 FTBFS if using the cdbs debhelper rulesets
with a straight cdbs include in debian/rules. Refer to the linked bug for
details cause that affects all CDBS built packages which try and use a compat
>> 10.
Sent from my iPhone
> On Nov 6, 2019, at 17:33, Chris L
package: lintian
Since Debhelper >= 10.9.2 and higher (and therefore compat >= 11), there
is a known issue in CDBS (refer to bug #885407 [1]) with the use of
dh_systemd_enable instead of dh_installsystemd. This has been on the
record since 2017 with the last activity on the bug over a year ag
Can you include the output of `nginx -V` please as well? Part of TLS
support is having a version of NGINX that is compiled against an OpenSSL
in the repositories for the version of Debian you're using which
supports TLS1.3, but that may not be the case in all releases of Debian.
Thomas
On
Identical/Similar reports in Ubuntu:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1712696
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1743592
Downstream, discussion on this in the Ubuntu Server Team indicated that
removing IPv6 support entirely on a system is what we consider
tags -1 + unreproducible
I have been unable to reproduce this since 2012, that said, the original
system this was on was a VERY low-spec VPS, in recent years I've run my
own infrastructure so it's not really an issue anymore.
Whether this is up for closure or not is the Maintainer's decision,
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "vmfs6-tools" for the ITP bug
I opened earlier (#939600).
* Package name : vmfs6-tools
Version : 0.1.0-1
Upstream Author : Thomas Ward and others (see ITP bug)
* URL : https://
Package: wnpp
Severity: wishlist
Owner: Thomas Ward
* Package name: vmfs6-tools
Version : 0.1.0
Upstream Author : Multiple (details below)
* URL : https://github.com/teward/vmfs6-tools
* License : GPL-2+
Programming Lang: C
Description : Tools to
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "xca" as I do not yet have
'unsponsored' upload privileges for this package even though I am the
maintainer.
* Package name : xca
Version : 2.1.2-2
Upstream Author : Christian Hohnstaedt
*
Hello.
Can you verify that cross-building is still broken in the version
available now in Unstable and Testing, as 1.4.1-1 has been superseded
for some time now? If it is still broken, please also update the patch,
however keep in mind configure.ac has changed so it's possible the issue
is n
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "xca"
* Package name : xca
Version : 2.1.2-1
Upstream Author : Christian Hohnstaedt
* URL : https://hohnstaedt.de/xca/
* License : BSD-3-clause
* Vcs : https://salsa.debian.org/debian/xca
S
Tobias, et. al:
On 7/13/19 2:17 PM, Thomas Ward wrote:
> On 7/13/19 1:26 PM, Tobias Frost wrote:
>> Ok, seems indeed a bumpy ride, glad that you were able to fix it.
>> Said that, I can also create a repository for you e.g in the Debian
>> namspace, (I see it is in your own
On 7/13/19 1:26 PM, Tobias Frost wrote:
> Ok, seems indeed a bumpy ride, glad that you were able to fix it.
> Said that, I can also create a repository for you e.g in the Debian
> namspace, (I see it is in your own namespace, this is OK but a Team's or
> the Debian namespace would be better). Let
Tobias,
Thanks for the response by the way - I appreciate more than just me
taking a look at this, and I definitely appreciate everyone being
willing to read
On 7/13/19 7:41 AM, Tobias Frost wrote:
> Hi Thomas,
>
> thanks for this ITS!
>
> On Wed, Jul 10, 2019 at 12:37:30PM -04
Also note that because of the package being out of date, and no response
from maintainer yet, downstream in Ubuntu the packages have diverged so
that this can be updated downstream from Debian. This is visible at
https://launchpad.net/ubuntu/+source/xca/2.1.2-0ubuntu1 if you wish to
see the packag
can be obtained from the SKS Key Servers shortly as it
has just been uploaded to the keyservers, or from the Ubuntu Key Server
[2].)
Thomas Ward
[1]: https://launchpad.net/~teward/+archive/ubuntu/xca
[2]:
https://keyserver.ubuntu.com/pks/lookup?fingerprint=on&op=index&search=0x5792F66164D057EFC6D06FAF5B8AD6F4C26A
signature.asc
Description: OpenPGP digital signature
Source: xca
Severity: wishlist
Hello.
The default package as-is does not allow for the use of Remote DB for
the Certificates storage. This means we only can use XCA Database 'flat
files'.
This differs from the Windows and Mac executables built upstream which
include that support.
This can be s
Source: xca
Severity: wishlist
Hello.
The XCA package in the Repository is a little bit out of date, as we are
on 2.1.2 which was released in November 2018.
Can you please update the packages to 2.1.2 from upstream?
Thomas
To all whom it concerns:
Following Dmitry's notes about source package name being incorrect, I
have uploaded a renamed source-package to Mentors.
You can download the package with dget and this command (with -ux
because you don't have my keys):
dget -ux
https://mentors.debian.net/debian/pool/mai
Hello.
On 2/1/19 9:27 AM, Dmitry Bogatov wrote:
> [2019-01-31 12:49] Thomas Ward
>> Package: sponsorship-requests
>> Severity: wishlist
>>
>> Dear mentors,
>>
>> I am looking for a sponsor for my package "imaplibext"
>>
>> *
Hi.
The GeoIP module is a core module in NGINX upstream. Keeping this in
mind, it's just packaged here as a dynamic module.
For reference purposes, I have forwarded this bug report to nginx
upstream's nginx-devel mailing list [1] for their response.
(Note that this is just me adding information
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "imaplibext"
* Package name: imaplibext
Version : 0.7.6-1
Upstream Author : Thomas Ward
* URL : https://gitlab.com/teward/imaplibext
Package: wnpp
Severity: wishlist
* Package name : imaplibext
Version : 0.7.6
Upstream Author : Thomas Ward
* URL : https://gitlab.com/teward/imaplibext
* License : AGPL-3+
Programming Lang: Python
Description : Python imaplib extension library providing
Just as an FYI, Upstream responded to an email I sent to them indicating
they are aware of this bug and have a fix in the works to be included in
a future version of chkrootkit.
There is no timeline on that from them, however; but we can indicate
that this has been forwarded upstream for them to d
1 - 100 of 177 matches
Mail list logo
