ectly contact IS on these major issues from
leadership councils, and this causes extra strain with the community and
Canonical when we can't get proper updates on what's going on.
Thomas Ward
Ubuntu Community Council Member
Ubuntu Technical Board Member
[1]:
https://discourse.ubuntu.com/
e or built.
Thomas
On 2025-04-09 21:54, Thomas Ward wrote:
The buildd logs indicate that a build dependency it needs is unavailable.
https://buildd.debian.org/status/package.php?p=ejabberd&suite=bookworm-backports
It's failing on erlang-redis-client (>= 1.2.0-8~) on every arch.
Thoma
The buildd logs indicate that a build dependency it needs is unavailable.
https://buildd.debian.org/status/package.php?p=ejabberd&suite=bookworm-backports
It's failing on erlang-redis-client (>= 1.2.0-8~) on every arch.
Thomas
On 2025-04-09 21:17, Mako N wrote:
Hello,
I found out on the sou
You okay there Bryce? I think the scripts are misbehaving :P
Sent from my Galaxy
Original message
From: Bryce Harrington
Date: 4/1/25 01:17 (GMT-05:00)
To: ubuntu-server
Cc: Bryce Harrington
Subject: Team subscriptions - 2025-03-31
Logging in to Launchpad...
Logging suc
I volunteer Robie. I have some wide regex catches that I put into place on
community council and lubuntu lists and it seems to be filtering a lot of the
junk out. Still some but not as much. That and we set some other restrictions
as well. Happy to apply those to the devel lists.
Thomas
Co
like a munmap patch has been provided but
it looks also that this may be one of multiple 'suspicious' commits on
the radar (if you read the issue thread).
Thomas Ward, CISSP
Thanks to Zixing Liu (liushuyu-011) for pinging me in Ubuntu Development
on Matrix yesterday to ask if they can pilot the patch upload, I have a
lot of things that piled onto my plate last minute that's eating ALL my
time right now (major critical-level non-Ubuntu stuff).
Because cockpit has the b
@mapreri: target Distribution is based on changelog entry I believe when
uploaded, even with `-d DIST` in `sbuild`. So that's something to
always check in changelog that it targets the correct pocket (jammy-
backports instead of jammy).
--
You received this bug notification because you are a mem
@mapreri: target Distribution is based on changelog entry I believe when
uploaded, even with `-d DIST` in `sbuild`. So that's something to
always check in changelog that it targets the correct pocket (jammy-
backports instead of jammy).
--
You received this bug notification because you are a mem
Thanks to Zixing Liu (liushuyu-011) for pinging me in Ubuntu Development
on Matrix yesterday to ask if they can pilot the patch upload, I have a
lot of things that piled onto my plate last minute that's eating ALL my
time right now (major critical-level non-Ubuntu stuff).
Because cockpit has the b
** Changed in: cockpit (Ubuntu Jammy)
Assignee: (unassigned) => Zixing Liu (liushuyu-011)
** Changed in: cockpit (Ubuntu Noble)
Assignee: (unassigned) => Zixing Liu (liushuyu-011)
** Changed in: cockpit (Ubuntu Oracular)
Assignee: (unassigned) => Zixing Liu (liushuyu-011)
** Chang
** Changed in: cockpit (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: cockpit (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: cockpit (Ubuntu Oracular)
Status: New => Fix Committed
** Changed in: cockpit (Ubuntu Jammy)
Assignee: Zixing Liu (liushu
** Changed in: cockpit (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: cockpit (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: cockpit (Ubuntu Oracular)
Status: New => Fix Committed
** Changed in: cockpit (Ubuntu Jammy)
Assignee: Zixing Liu (liushu
** Changed in: cockpit (Ubuntu Jammy)
Assignee: (unassigned) => Zixing Liu (liushuyu-011)
** Changed in: cockpit (Ubuntu Noble)
Assignee: (unassigned) => Zixing Liu (liushuyu-011)
** Changed in: cockpit (Ubuntu Oracular)
Assignee: (unassigned) => Zixing Liu (liushuyu-011)
** Chang
also Martin, yes, there is a new BPO template *AND* bug prefix to use.
I'll make an exception *this time* for it and just let it through once I
upload/sponsor (had some Major Level Crap to deal with that took
ultimate priority), but for *future* requests you should follow the
template that Andreas
also Martin, yes, there is a new BPO template *AND* bug prefix to use.
I'll make an exception *this time* for it and just let it through once I
upload/sponsor (had some Major Level Crap to deal with that took
ultimate priority), but for *future* requests you should follow the
template that Andreas
But I can.
Removed backporters.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083908
Title:
[SRU] pymodbus 3.6.9-1 from 24.10 (to 24.04)
To manage notifications about this bug go to:
https://bugs
juliak, since it sounds like Synaptic, which is still in Universe,
depends on this, perhaps synaptic should be in the target list because
this would be a 'critical' requirement in Synaptic, if I remember my
packaging right.
--
You received this bug notification because you are a member of Ubuntu
juliak, since it sounds like Synaptic, which is still in Universe,
depends on this, perhaps synaptic should be in the target list because
this would be a 'critical' requirement in Synaptic, if I remember my
packaging right.
--
You received this bug notification because you are a member of Ubuntu
Nope you did nothing bad, you were perfectly in the right. As I said,
unless another sponsor gets to it I'll sponsor your uploads, though that
kind of 'self-approves' which is fine since we have precedent to approve
cockpit due to quality of uploads and need of the package.
As for the developer u
Nope you did nothing bad, you were perfectly in the right. As I said,
unless another sponsor gets to it I'll sponsor your uploads, though that
kind of 'self-approves' which is fine since we have precedent to approve
cockpit due to quality of uploads and need of the package.
As for the developer u
> - I don't know if ~ubuntu-backporters is still a thing, but that wiki
page says they should be subscribed
Andreas, the Backporters team is the people who now approve backports in
the system. It is *no longer* the team that does uploads, testing, etc.
as the entire backports process changed durin
> I subscribed them. It looks like there isn't much of a backports team
left -- e.g. https://launchpad.net/lucid-backports still exists, but no
https://launchpad.net/noble-backports or https://launchpad.net/jammy-
backports
Martin,
Circa 2023, the Backports process was **redesigned entirely**, an
> I subscribed them. It looks like there isn't much of a backports team
left -- e.g. https://launchpad.net/lucid-backports still exists, but no
https://launchpad.net/noble-backports or https://launchpad.net/jammy-
backports
Martin,
Circa 2023, the Backports process was **redesigned entirely**, an
> - I don't know if ~ubuntu-backporters is still a thing, but that wiki
page says they should be subscribed
Andreas, the Backporters team is the people who now approve backports in
the system. It is *no longer* the team that does uploads, testing, etc.
as the entire backports process changed durin
Done.
FYI
https://salsa.debian.org/python-team/packages/pyinstaller-hooks-contrib/-/settings/repository#branch-defaults-settings
is where you can do that if you have permissions. I just did this for
you as a member of the Python team.
Thomas
On 2025-03-15 22:39, Soren Stoutner wrote:
Ca
In line with a recent nginx mailing list thread I had with a user about
how to properly secure a site with SSL/TLS Client Certificates, the user
indicated that "ssl_client_certificate" is a confusing misnomer. It
implies that the certificate(s) provided are a bundle of certs that are
*individu
I don't have the ESM licenses available at the moment to license a
trusty, xenial, or bionic container, as the ESM repos for trusty
(legacy), xenial, and bionic have what look like patched Python 2
versions of jinja2 which I cannot test.
I have confirmed this import error will happen on Ubuntu Foc
On 2025-03-10 14:36, Andrey Rakhmatullin wrote:
On Mon, Mar 10, 2025 at 07:06:57PM +0100, Christian BAYLE wrote:
I just encountered recently a few venv that require 3.10 to work in
at least 2 ai stable diffusion software, really difficult to package
right now.
Not sure what do you mean by v
This requires someone with upload privileges to upload but also requires
someone dedicated to maintain this in Backports. That includes
addressing bug reports and such in Backports.
There has been no movement since Michael Vogt replied, so this needs
someone with upload privileges willing to back
This requires someone with upload privileges to upload but also requires
someone dedicated to maintain this in Backports. That includes
addressing bug reports and such in Backports.
There has been no movement since Michael Vogt replied, so this needs
someone with upload privileges willing to back
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
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
ern because
we can adjust the snippets independent of src:nginx and we can also allow wider
suggestion of useful snippets without requiring them to be embedded in
src:nginx.
Thomas
Sent from my Galaxy
Original message
From: Tobias Frost
Date: 3/2/25 03:59 (GMT-05:00)
To: T
untu which sync from
Unstable.
If Unstable as a destination is not acceptable because of freezes, then I'll
accept this being in Experimental until post-freezes.
Thomas
________
From: Thomas Ward
Sent: Sunday, February 23, 2025 12:29 AM
To: submit
Subject
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
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-devel@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
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
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
Salsa bug for discussion on 1098477 is https://salsa.debian.org/nginx-
team/nginx/-/issues/23 - we usually do the team discussions on Salsa
there.
** Bug watch added: salsa.debian.org/nginx-team/nginx/-/issues #23
https://salsa.debian.org/nginx-team/nginx/-/issues/23
--
You received this bug
I think the peoblem is multifold and endemic to the Debian approach of
'flavor packages'. The problem is splitting out the nginx binary
components because there are still things that haooen between the
flavors with binary compile-level stuff because not every module is
dynamic.
Open the bug in De
Forwarded upstream as https://github.com/chris2511/xca/issues/633
Sent from my Galaxy
Debdiffs prepared for Security Team review / inclusion. Note that the
specific module is embedded in debian/modules/... so non-standard
patching (aka non-Quilt-patching) was utilized.
Upstream patches were {UPSTREAM_URL}.patch to get the patch files that
were applied.j
--
You received this bug
** Patch added: "debdiff for focal"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1977718/+attachment/5857604/+files/lp1977718-focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/197
** Patch added: "debdiff for jammy"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1977718/+attachment/5857605/+files/lp1977718-jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/197
** Summary changed:
- buffer overflow in nginx rtmp module
+ buffer overflow, null pointer deref in nginx rtmp module
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977718
Title:
buffer overflow, n
By installing the NGINX main repositories for NGINX, all bugs or issues
with the package need to be sent to NGINX upstream directly, as you are
using third-party repositories.
This is an Invalid bug against the Ubuntu packages of nginx.
** Changed in: nginx (Ubuntu)
Status: Incomplete => I
Additionally, the NGINX upstream repositories **will not** work with
third party modules in the repositories that only work with the older
NGINX that is in the Ubuntu repositories - this is due to version
mismatch, and NOT an Ubuntu issue.
--
You received this bug notification because you are a m
Timo: The bug was closed in Debian the old ways - by hand. Marked Fixed
and Done in Debian, so no the Debian bug isn't open anymore. ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081308
Title:
R
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2096808
Title:
Merge euslisp/jskeus from Debian unstable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/euslisp
Bécue
Sent: Tuesday, January 21, 2025 09:57
To: Thomas Ward
Cc: debian-python@lists.debian.org; Thomas Ward
Subject: Re: Request to Join Debian Python Team
Hi,
Thomas Ward wrote on 21/01/2025 at 00:32:07+0100:
> Hello, Python Team!
>
> My name is Thomas Ward, and I'm a Debian Mainta
Hello, Python Team!
My name is Thomas Ward, and I'm a Debian Maintainer on a few packages.
I'd like to join the Debian Python team.
My reasoning for joining is because I am in the process of working on an
ITP [1] for a Python library - repolib - that originates from Pop-OS but
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
Isn't this a serious divergence from Debian? Is there a reason this wasn't
discussed in debian-devel as well? It sounds like something that should also
be discussed upstream not just here in Ubuntu before it's accepted/merged.
Thomas
From: ubuntu-devel on beh
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
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
Package: wnpp
Severity: wishlist
Owner: Thomas Ward
X-Debbugs-Cc: debian-devel@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
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
Uploads for Noble and Oracular are pending approval from the SRU team.
** Changed in: ubuntustudio-default-settings (Ubuntu Oracular)
Status: Triaged => In Progress
** Changed in: ubuntustudio-default-settings (Ubuntu Noble)
Status: Triaged => In Progress
** Description changed:
+
** Changed in: ubuntustudio-default-settings (Ubuntu Plucky)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2087756
Title:
package ubuntustudio-default-set
** Changed in: ubuntustudio-default-settings (Ubuntu Noble)
Assignee: Erich Eickmeyer (eeickmeyer) => Thomas Ward (teward)
** Changed in: ubuntustudio-default-settings (Ubuntu Oracular)
Assignee: Erich Eickmeyer (eeickmeyer) => Thomas Ward (teward)
** Changed in: ubuntustudio-d
*** This bug is a duplicate of bug 2087756 ***
https://bugs.launchpad.net/bugs/2087756
I will note its the Studio flavor's policy/opinion that these setups are
unsupported. Going from vanilla Ubuntu Desktop and then installing
Studio on top of it is not a supported setup, hence the errors you
Public bug reported:
When installing `python3-binwalk` and the package reaches `Setting up`
in Ubuntu 24.04, we see this on-load SyntaxWarning:
/usr/lib/python3/dist-packages/binwalk/core/magic.py:431: SyntaxWarning: invalid
escape sequence '\.'
self.period = re.compile("\.")
This is fixable
This isn't an issue with NGINX, it's an issue with your configuration.
From the output of the journal for your NGINX runs:
dez 02 21:48:16 walter-ubuntu nginx[2210]: 2024/12/02 21:48:16 [emerg]
2210#2210: cannot load certificate
"/home/walter/zapstart/MultiPro02/backend/certs/cert.pem":
BIO_new_fi
I would like to note that adjusting the DlMaxRetries value was
substantially helpful.
To answer @melroyvandenberg:
Yes, apt-cacher-ng responds with a "503 Service Unavailable" along with
the additional notices when package download attempts by the caching
proxy from the actual package source is g
** Summary changed:
- package ubuntustudio-default-settings (not installed) failed to
install/upgrade: Versuch, »/etc/skel/.face« zu überschreiben, welches auch in
Paket desktop-base 12.0.6+nmu1ubuntu1 ist
+ package ubuntustudio-default-settings (not installed) failed to
install/upgrade: Trying
ntu Plucky)
Importance: High
Assignee: Thomas Ward (teward)
Status: Confirmed
** Changed in: filelight (Ubuntu Plucky)
Status: Confirmed => Invalid
** Changed in: filelight (Ubuntu Oracular)
Status: New => Confirmed
** Changed in: filelight (Ubuntu Oracular)
I
ntu Plucky)
Importance: High
Assignee: Thomas Ward (teward)
Status: Confirmed
** Changed in: filelight (Ubuntu Plucky)
Status: Confirmed => Invalid
** Changed in: filelight (Ubuntu Oracular)
Status: New => Confirmed
** Changed in: filelight (Ubuntu Oracular)
I
Running test builds on my cluster before sponsoring.
** Changed in: filelight (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084169
Ti
Running test builds on my cluster before sponsoring.
** Changed in: filelight (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to filelight in Ubuntu.
https://bugs.launchpad.net/b
On 10/16/24 13:52, Mark Sapiro wrote:
On 10/14/24 12:42, Greg Newby via Mailman-users wrote:
Here are the corresponding logfile entries from mailmanweb.log:
smtplib.SMTPRecipientsRefused: {'redac...@gmail.com': (504, b'5.5.2
:
Helo command rejected: need fully-qualified hostname')}
and from
I already committed to Debian Salsa an unreleased -3 of nginx that
resolves this dependency loop. I am going to unilaterally upload that as
an RC fix in Debian. From there we can sync to 25.04 and then SRU fix
this with high bugfix priority for 24.10 and 24.04.
--
You received this bug notificati
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
** Changed in: nginx (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081308
Title:
open() "/etc/nginx/nginx.conf" failed (2: No such file or directory)
To m
Bryce,
This was discussed when I wrote the hooks. Unfortunately we decided
that in itself is a privacy breach and decided to NOT do that. We also
decided that the user should upload that because it can contain
sensitive information.
--
You received this bug notification because you are a membe
To follow up on Sergio's message, please include your
`/etc/nginx/nginx.conf` file here if you believe this is a problem in
the package and not your specific configuration. It's more than likely
you have a `user test_domain;` option in your configuration, and that is
not a valid user, meaning you'
Fix added to Salsa repository for Unstable, pending tag added.
Thomas
: tew...@ubuntu.com, Backports Discussion
Subject: Re: Request for BPO Exception: XCA
On Mon, 8 Jul 2024, Thomas Ward wrote:
>
> Hello.
>
>
>
> The Universe package XCA is a tool for creating and managing X.509
> certificates, certificate requests, RSA/DSA/EC private keys, Smartcard
Seeing a lot of messages related to moving from mercurial to git here in the
mailing list. Are the nginx.org code repos shifting to Git instead of Mercurial?
Sent from my Galaxy
___
nginx-devel mailing list
nginx-devel@nginx.org
https://mailman.nginx
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.
This is easily fixed by using a dhparam that is 2048 or larger. The
underlying OpenSSL libraries no longer permit dhparam under 2048 bits in
size. This is the "failure" in the error logs and is fixable by end
user admins by simply using larger dhparams.
This is not an nginx package issue.
** Ch
@hloeung To get this in Jammy or such would be an extrwmely intrusive
change because we'd have to backport *all* nginx and nginx module source
packages. Just putting this there for the record. While this is fixed
for Mantic and Noble and later, it is too intrusive a fix to backport to
Jammy and s
To echo bryce, to backport this to older releases is nontrivial, as in
order to support a backport of the new reengineered packaging we also
have to backport all other nginx modules. This is a very intrusive
change on older releases.
--
You received this bug notification because you are a member
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
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
s that are beyond just bug
fixes, it is prudent to have the version in Devel match the version in stable
releases.
To that end, I'd like to request a backports exception for src:xca so that I
can continue to provide the backported versions regularly to current supported
LTS releases.
Tho
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
NOTE: I backported locally debootstrap 1.0.136ubuntu1 from Oracular to
Jammy, and **it resolved the issue**. As a result I am certain this is a
debootstrap issue.
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: New => Invalid
** Changed in: debootstrap (Ubuntu)
Importance: Undecided =>
mapreri: Tracked in Debian as https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1074383 - any comments we need to have can be
there instead of on this backport bug. (The backport is now Fix
Released in the system as it's published in the archives)
** Bug watch added: Debian Bug tracker #1074383
mapreri: Tracked in Debian as https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1074383 - any comments we need to have can be
there instead of on this backport bug. (The backport is now Fix
Released in the system as it's published in the archives)
** Bug watch added: Debian Bug tracker #1074383
1 - 100 of 17883 matches
Mail list logo
