Bug#1068676: New Upstream Release, Package Problems, vcswatch issues.

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

Bug#1067697: Update Build-Depends for the time64 library renames

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

Bug#1067697: Update Build-Depends for the time64 library renames

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.

Bug#1053757: (no subject)

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.

Bug#1053907: RFS: xca/2.5.0-1 -- x509 Certification Authority management tool based on QT

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

Bug#1050186: [Pkg-nginx-maintainers] Bug#1050186: Bug#1050186: libnginx-mod-http-lua: depends on obsolete pcre3 library

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

Bug#1050186: [Pkg-nginx-maintainers] Bug#1050186: libnginx-mod-http-lua: depends on obsolete pcre3 library

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

Bug#1050186: [Pkg-nginx-maintainers] Bug#1050186: libnginx-mod-http-lua: depends on obsolete pcre3 library

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

Bug#1032517: [Pkg-nginx-maintainers] Bug#1032517: Bug#1032517:

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

Bug#796295: Happy to Help

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

Bug#1025763: [Pkg-nginx-maintainers] Bug#1025763: nginx: do nginx-extras nginx-full nginx-core nginx-light still make sense ?

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.

Bug#1024612: (no subject)

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

Bug#1025035: pastebinit not returning proper URL for pastes going to paste.debian.net

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

Bug#1021393: closed by Thomas Ward ()

figuration, 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 wrote: Ok I guess I should hav

Bug#1011935: QtChooser is dead by choice upstream, no Qt6 Support

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

Bug#1010938: Please update package to latest upstream versions

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

Bug#1010798: nginx-common: duplicate extension "woff" in /etc/nginx/mime.types

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

Bug#1008858: [pkg-lua-devel] Bug#1008858: Please support s390x

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: luajit > >

Bug#1010584: ITS: rlwrap

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 ,

Bug#991328: NGINX patch for CVE pending in Salsa

, On Wed, May 04, 2022 at 07:22:22PM +, 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 wasn't added in upstream. I

Bug#991328: closed by Thomas Ward ()

--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: reopen -1 Hi Thomas, On Wed, May 04, 2022 at 04:45:

Bug#1009976: RFS: nginx/1.20.2-1 [Team] -- small, powerful, scalable web/proxy server

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 :

Bug#1009709: RFS: nginx/1.0-2 [RC] -- small, powerful, scalable web/proxy server

t 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/watch: Upd

Bug#1008787: (no subject)

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

Bug#1009313: (no subject)

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

Bug#1008858: Please support s390x

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

Bug#1008787: Deep dive discovered partial fix

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

Bug#1008855: Please package newer NGINX Stable version 1.20.0

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

Bug#1008787: NGINX FTBFS: Lua dependencies missing

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

Bug#1005360: RFS: xca/2.4.0-2 -- x509 Certification Authority management tool based on QT

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

Bug#1003072: RFS: xca/2.4.0-1 -- x509 Certification Authority management tool based on Qt

. Regards, -- Thomas Ward

Bug#1001552: Improper detection of tag satisfaction cases in missing-build-dependency-for-dh-addon tag

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

Bug#1001498: No OpenSSL 3.0 support in XCA 2.3.0 and later

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.

Bug#1000406: nginx-common: Nginx starts before DNS is ready

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

Bug#986787: (no subject)

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

Bug#921034: Depends on MaxMind GeoIP Legacy databases - superseded by GeoIP2

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 nginx >

Bug#969610: RFS: xca/2.3.0-1 -- x509 Certification Authority management tool based on QT

) fixes    to handle issue with autoheader changes and build failures. - debian/control: Replace Recommends postgresql dependency to    libqt5sql5-psql Regards, --   Thomas Ward

Bug#964203: libnginx-mod-nchan distributes old/incompatible module

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

Bug#919320: nginx-extras: Would you please consider replacing Gzip module with Brotli for compression?

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:

Bug#963860: nginx-full: circular dependency hell

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

Bug#960580: (no subject)

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.

Bug#958886: (no subject)

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.

Bug#958886: (no subject)

Looks like OpenSSL is at fault, refer to  https://github.com/openssl/openssl/pull/10029Sent from my Sprint Samsung Galaxy Note10+.

Bug#958886:

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

Bug#958886: xca: OID LN differs warning popups at startup

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

Bug#955191: Fwd: bubblemail

-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 intensively

Bug#955191: RFS: bubblemail/0.5-1 [ITP] -- Extensible mail notification service

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

Bug#955188: ITP: bubblemail -- An extensible mail notification service

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

Bug#954744: RFS: xca/2.2.1-1~bpo10+1 -- x509 Certification Authority management tool based on QT

s has been requested by others to me on Freenode IRC. Regards, -- Thomas Ward

Bug#950599: RFS: xca/2.2.1-1 -- x509 Certification Authority management tool based on QT

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

Bug#947777: RFS: vmfs6-tools/0.1.0-3 -- Tools to access VMFS6 filesystems

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.

Bug#947328: (no subject)

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

Bug#947485: RFS: xca/2.1.2-3 [RC]-- x509 Certification Authority management tool based on QT

. Regards, -- Thomas Ward

Bug#947481: Patch Acceptance

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!

Bug#947328: FTBFS Not Reproducible in multiple build test envs (sbuild, pbuilder, etc.)

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

Bug#944260: lintian: Add a detection/tag for when compat is >> 10 and cdbs in build-depends

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

Bug#944260: lintian: Add a detection/tag for when compat is >> 10 and cdbs in build-depends

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

Bug#944260: lintian: Add a detection/tag for when compat is >> 10 and cdbs in build-depends

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

Bug#944006: nginx-extras missing TLS1.3

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

Bug#942817: Additional Data

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

Bug#697030: Unreproducible

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

Bug#939624: RFS: vmfs6-tools/0.1.0-1 [ITP] -- Tools to access VMFS6 filesystems

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://

Bug#939600: ITP: vmfs6-tools -- Tools to access VMFS6 filesystems

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

Bug#939433: RFS: xca/2.1.2-2 -- x509 Certification Authority management tool based on QT

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

Bug#896891: (no subject)

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

Bug#935462: RFS: xca/2.1.2-1 [ITS] -- x509 Certification Authority management tool based on QT

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  

Bug#931806: your mail

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

Bug#931806: your mail

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

Bug#931806: your mail

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

Bug#931806: (no subject)

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

Bug#931806: ITS: xca

s 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=index=0x5792F66164D057EFC6D06FAF5B8AD6F4C26A signature.asc Description: OpenPGP digital signature

Bug#928678: Enable Remote DB Support

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

Bug#927233: XCA: Outdated, please provide newer XCA

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

Bug#921020: RFS: python-imaplibext/0.7.6-1 [ITP]

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

Bug#921020: RFS: imaplibext/0.7.6-1 [ITP]

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" >> >> *

Bug#921034: Depends on MaxMind GeoIP Legacy databases - superseded by GeoIP2

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

Bug#921020: RFS: imaplibext/0.7.6-1 [ITP]

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

Bug#920952: ITP: imaplibext -- Python imaplib extension library providing UID-based commands

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

Bug#919254: (no subject)

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

Bug#919805: ruby-mail is "too new" for this

3.4.6 Redmine doesn't support ruby-mail beyond 2.6.4.  Neither does the latest 3.4.x release. This package would need to be updated to Redmine 4.0.1 and track the 4.0.x series to get the proper ruby-mail support. (Looking into this downstream in Ubuntu, this was discovered.  I am simply sharing

Bug#920214: httpie: out of date, please update to 1.0.2

Package: httpie Severity: wishlist Dear Maintainer, httpie is significantly out of date.  The version in Debian at present - 0.9.8-2 - was last updated in 2017.  Since then, there have been four newer versions of HTTPie, the latest being 1.0.2.  This includes major changes from HTTPie 1.0.0

Bug#919320: nginx-extras: Would you please consider replacing Gzip module with Brotli for compression?

FYI if I remember right BREACH is a risk in Brotli as well. Also Brotli has a few code level concerns that the Ubuntu Security Team saw in a cursory review that could lead to crashes which made it judged 'not suitable for inclusion'. Just wanted to share this info. On Mon, Jan 14, 2019, 17:46

Bug#915499: nginx: ship a snippet for strong SSL options

t; On Tuesday, December 4, 2018 9:55 PM, Thomas Ward > wrote: > > I should point out that "strong" options are typically only for the most > modern grades of interactivity of SSL compatibility. Therefore > Cipherli.st's recommendations are not altogether the most same

Bug#915499: nginx: ship a snippet for strong SSL options

I should point out that "strong" options are typically only for the most modern grades of interactivity of SSL compatibility. Therefore Cipherli.st's recommendations are not altogether the most same approach to this even if it's a non-default config snippet. Permit me to ask this, but what basis

Bug#900068: searx cannot run in uWSGI; CI fails as well

Package: searx Version: 0.14.0+dfsg1-2 Severity: important During testing of observed downstream autopkgtest failures in Ubuntu, the `searx` package fails to run under uWSGI, which its upstream documentation says to utilize.  The crash error is absorbed by uWSGI and processed as a segmentation

Bug#897926: Enable --with-compat configure argument

Source: nginx Severity: wishlist I have received multiple requests in downstream PPAs and repositories to enable the `--with-compat` configuration option. This would allow for users to build additional dynamic modules with binary module compatibility. It was stated in an October 12, 2016 email

Bug#856530: fPIE not enabled for Jessie Backports

Source: nginx Severity: wishlist Version: 1.10.3-1~bpo8+1 As part of a discussion with the NGINX maintainers on IRC chat in the #debian-nginx channel on OFTC, we established fPIE/fPIC is enabled proper in Debian Unstable and Debian Experimental. We also established there were build issues when

Bug#842276: nginx-common.config dpkg --compare-versions will mishandle return codes should the check fail

Source: nginx Severity: serious Version: 1.6.2-5+deb8u3 This was originally identified as a result of my own failure downstream in Ubuntu when applying the patches from Debian for CVE-2016-1247. One of the things added was nginx-common.config. In this, the following set of code exists:

Bug#834747: nginx-extras: Feature request: Add 3rd party module graphite-nginx-module.

Please note that there is currently a "Won't Fix" for "No New Modules or Flavors", which may still apply here. This is bug #790623 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790623) -- Thomas On Thu, Aug 18, 2016 at 10:39 AM, Roman V. Nikolaev wrote: > Package:

Bug#826475: pymssql fetch functions return nothing, traces back to freetdx and 1.0.x incompatibility

Package: python-pymssql Version: 1.0.2+dfsg-1 Severity: important Tags: fixed-upstream It has been observed by myself and others that pymssql version 1.0.2 has some type of incompatibility with freetdx 0.91, such that in 1.0.x of pymssql when you attempt to fetchone() from a cursor after query

Bug#823608: nginx-common: Move nginx.vim to a separate package?

In my opinion, creating a package for a single file (with the exception of the Dynamic Modules), is a little overkill to do. While I can understand that this is something desirable to some, I can see this as an 'extra annoyance' for packaging teams, here and downstream. I'm of the opinion that

Bug#815095: nginx-extras: Feature request: Add 3rd party module nginx-sticky-module-ng

Refer to this Debian bug for this (the "master sticky" bug - all New Addon requests are no longer being processed or accepted - https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790623 Thomas On 02/18/2016 12:54 PM, Hannes Hoerl wrote: > Package: nginx-extras > Severity: wishlist > > Dear

Bug#813228: Cert Validation Wasn't In 1.4

ZNC 1.4 never had certificate validation. That feature was added in ZNC 1.6. Therefore you are asking for a new feature or item to be added, so the bug is a Wishlist type bug. I would be extremely wary of incorporating this change into 1.4's packaging if only due to the fact that you haven't

Bug#806340: Please update display-dhammapada to latest upstream release

Source: display-dhammapada Severity: wishlist Hello. It was requested (to a downstream location where I keep an eye on) to have display-dhammapada updated to version 1.2 which includes bug fixes and improvements. Currently, 1.0 is packaged in Debian, which is at least two years out of date...

Bug#796094: Include spnego nignx module in the builds

:09 AM, Thomas Ward wrote: Control: submitter -1 sorin.sbar...@gmail.com ... I think that it would be extremely helpful to include the spnego module in nginx builds. Source https://github.com/stnoonan/spnego-http-auth-nginx-module Risk considerations: this module is not enabled

Bug#796240: nginx: jessie-backports package should be based on stable branch

My thoughts are in line below On 08/20/2015 12:42 PM, Jonh Wendell wrote: Source: nginx Severity: normal I think we should offer as part of backport the stable version of upstream package. In nginx case, stable branch is 1.8. 1.9 is the development version (called by upstream 'mainline')

Bug#796094: Include spnego nignx module in the builds

Source: nginx Severity: wishlist Control: submitter -1 sorin.sbar...@gmail.com Initially reported downstream, and pushed to here by Thomas Ward from Launchpad.net. This was requested against the downstream PPA builds, however there should not be a delta between the PPAs and Debian, save for fail

Bug#796094: Include spnego nignx module in the builds

On 08/19/2015 08:09 AM, Thomas Ward wrote: Control: submitter -1 sorin.sbar...@gmail.com ... I think that it would be extremely helpful to include the spnego module in nginx builds. Source https://github.com/stnoonan/spnego-http-auth-nginx-module Risk considerations: this module

Bug#792231: This needs examined as soon as possible

On 08/03/2015 10:41 AM, Tristan Seligmann wrote: Unfortunately there are some significant challenges with 2.0+. The primary issue is the dependency on tlslite, which was removed from Debian previously due to being insecure and unmaintained. In addition, quite a bit of the certificate handling

Bug#792231: This needs examined as soon as possible

1.9.8 is a year old. In addition, 2.4 is the current version. Failing to update breaks recovery of wallets from newer versions, and there are quite a lot of improvements in 2.4 over 1.9.8 that should be reviewed and included. Thomas -- To UNSUBSCRIBE, email to

  1   2   >