** Changed in: debmirror (Ubuntu)
Assignee: (unassigned) => Valters Jansons (valterj)
** Patch added: "debdiff between Debian .dsc and my modified one"
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+attachment/5402653/+files/debmirror_2.33_2.33ubuntu1.deb
** Patch added: "debdiff between the old Ubuntu .dsc and my modified one"
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+attachment/5402654/+files/debmirror_2.27ubuntu1_2.33ubuntu1.debdiff
** Changed in: debmirror (Ubuntu)
Assignee: Valters Janson
Patch removed: "debdiff between the old Ubuntu .dsc and my modified one"
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+attachment/5402654/+files/debmirror_2.27ubuntu1_2.33ubuntu1.debdiff
** Changed in: debmirror (Ubuntu)
Assignee: (unassigned) => Valters Jansons (
Public bug reported:
MoM reports a conflict for debian/control and debian/rules files.
(debian/control) Upstream changed Priority from extra to optional:
-
https://salsa.debian.org/debian/debmirror/-/commit/b264963519c7528f74ec24d5b227b87578f745b3
(debian/control) Upstream switched from
** Patch added: "debdiff between the old Ubuntu .dsc and my modified one"
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+attachment/5402660/+files/debmirror_2.27ubuntu1_2.33ubuntu1.debdiff
** Changed in: debmirror (Ubuntu)
Assignee: Valters Janson
Adjusted the changelog for Groovy.
** Patch added: "debdiff between Debian .dsc and my modified one"
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+attachment/5402659/+files/debmirror_2.33_2.33ubuntu1.debdiff
--
You received this bug notification because you are a member
*** This bug is a duplicate of bug 1821251 ***
https://bugs.launchpad.net/bugs/1821251
** This bug has been marked a duplicate of bug 1821251
please add cnf support to debmirror
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "debdiff between the old Ubuntu .dsc and my modified one"
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110/+attachment/5403649/+files/debmirror_2.27ubuntu1_2.33ubuntu1.debdiff
** Patch removed: "debdiff between the old Ubuntu .dsc and my modified one"
Refreshed the existing patches properly to be based on updated upstream
source, without complaints about hunks having been shifted around.
** Patch added: "debdiff between Debian .dsc and my modified one"
No worries about the delay - happy it's being picked up!
If there is anything I can do/improve on my part, do let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892110
Title:
Please merge
This was handled as a merge in #1892110 and is being handled as an SRU
in #1906541 with the patch provided in that SRU ticket including further
upstream commits.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> The bug linked in the changelog of the SRU is this one, not bug
#1906541.
Indeed, I am not sure of the proper formatting rules, considering this
was my first merge request followed by SRU request of upstream changes.
The upstream changelog included the details of the original owner along
with
TEST CASE:
1. Installed current non-SRU package: apt install debmirror=1:2.27ubuntu1
2. Created a 20.04 Focal mirror: /usr/bin/debmirror -a amd64,i386 -d
focal,focal-security,focal-updates,focal-backports -s
main,universe,restricted,multiverse --nosource --passive --method=http -h
I see a SRU being worth it for upstream v2.32 changes. Without those
commits, the package produces a mirror that is unusable for Ubuntu 20.04
`apt` clients (and newer). For that reason, I am wondering if I should
just pick those commits out, and propose a 20.04+20.10 SRU exclusively
for that (as
The relevant upstream changes can be seen at:
-
https://salsa.debian.org/debian/debmirror/-/commit/292e9e9c999dbfa9cd0269c5b7c8f82af09300fc
-
https://salsa.debian.org/debian/debmirror/-/commit/39055366f9cd4f161e451cf0621d52f7dc0d5126
-
This SRU further applies to Groovy (20.10) in addition to Focal (20.04).
Hirsute (21.04) already has been pushed an upstream merge and is not a
concern.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This was resolved in upstream commit b50e8880
(https://salsa.debian.org/debian/debmirror/-/commit/b50e8880a187ee5b9e1507201c0815dcd4baf63f)
and released as part of version 1:2.28. This resolution is already
available as part of the 1:2.33 merge included in Ubuntu Hirsute
(21.04).
Considering this
Public bug reported:
[Impact]
* Starting with Ubuntu Focal (20.04), the APT client expects APT
sources to provide command-not-found (cnf) metadata files.
* This package provides package mirrors, however does not support
mirroring this cnf metadata up until upstream version 1:2.32, which is
Thank you for the information, as well as the
SecurityTeam/UpdatePreparation link. I will for sure keep that in mind
for potential future SRU requests.
And thank you for the handling the correction during sponsoring.
Let me know if there is anything else I can provide to assist in the
process!
Public bug reported:
[Impact]
* On Ubuntu (Focal) 20.04, SSSD 2.2.3-3, logs in Journald have invalid
(non-numeric) SYSLOG_PID. Any tooling collecting SYSLOG_PID further, or
attempting to work with syslog directly, fail to parse the PID as
number.
* Systemd does not validate, and simply
TEST CASE:
1. Deploy fresh (up-to-date) Ubuntu 20.10 (Groovy) machine.
2. apt install -qqy debmirror=1:2.27ubuntu1
3. debmirror -a amd64 -d groovy -s main --nosource --passive --method=http -h
archive.ubuntu.com -r ubuntu
--keyring=/usr/share/keyrings/ubuntu-archive-keyring.gpg --progress
This could also be something on systemd/journald side. Looking at the
source code, it seems SYSLOG_IDENTIFIER is the relevant part that gets
set, but then somehow ends up 'leaking' into SYSLOG_PID.
https://github.com/SSSD/sssd/blob/sssd-2_2_3/src/util/sss_log.c#L110
There is a further upstream
** Description changed:
[Impact]
- * On Ubuntu (Focal) 20.04, SSSD 2.2.3-3, logs in Journald have invalid
+ * On Ubuntu (Focal) 20.04, SSSD 2.2.3-3, logs in Journald have invalid
(non-numeric) SYSLOG_PID. Any tooling collecting SYSLOG_PID further, or
attempting to work with syslog
** Summary changed:
- Variable $buf not initialized on 2.7 version
+ Variable $buf not initialized on 2.27 version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899498
Title:
Variable $buf not
** Patch added: "upstream commit b50e8880a187ee5b9e1507201c0815dcd4baf63f"
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1899498/+attachment/5443821/+files/variable-buf-not-initialized.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
For completeness sake here, there is a merge request at
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1892110 which
rebases the Ubuntu changes on top of the latest upstream debmirror
version, in turn including the required `command-not-found` changes.
--
You received this bug
Is there any way to assist in moving this bug along?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908065
Title:
Invalid SYSLOG_PID for (systemd) journal messages
To manage notifications about
Sorry Dan, I did not initially grasp the full implication of your
message if it was intended that way. Thank you for the upstream commit
linked.
Will poke around a bit more and provide a proposed debdiff to be
sponspored then, but to summarize from SSSD side: indeed not
reproducible with a
** Patch added: "sssd_2.2.3-3ubuntu0.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5456023/+files/sssd_2.2.3-3ubuntu0.4.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Opened https://github.com/SSSD/sssd/pull/5477 proposing to replace
square brackets with parentheses.
I will wait for review there before proposing new debdiffs with the
change, in case either I missed something or upstream wants other tokens
than parentheses.
--
You received this bug
> Probably someone should explain the problem to upstream sssd and
suggest they use something other than brackets; literally anything else
should avoid this problem, e.g. parenthesis, curly brackets, etc.
This formatting with "[" in syslog TAG is already a concern on Groovy
and Hirsute even
It does not appear that systemd-journald is automatically parsing
SYSLOG_IDENTIFIER. The following sample program:
#include
int main(int argc, char *argv[]) {
sd_journal_send("MESSAGE=%s", "Hello world!",
"SYSLOG_IDENTIFIER=%s", "sssd[sudo]",
NULL);
}
Thank you for subscribing ubuntu-sponsors.
Feel free to handles this after 2.2.3-3ubuntu0.3 reaches focal-updates,
as that was published on focal-proposed yesterday (2021-01-22), and this
change is not necessarily of such high priority compared to it.
--
You received this bug notification
Sorry, in the last message I meant the Focal 20.04 debdiff includes
both.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908065
Title:
Invalid SYSLOG_PID for (systemd) journal messages
To manage
The Bionic 20.04 debdiff (as 2.2.3-3ubuntu0.4) does include both
referenced commits.
I will take a look and provide debdiffs for the other affected versions
- Bionic 18.04, Groovy 20.10, Hirsute 21.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: "sssd_1.16.1-1ubuntu1.8.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5456290/+files/sssd_1.16.1-1ubuntu1.8.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "sssd_2.3.1-3ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5456636/+files/sssd_2.3.1-3ubuntu4.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
New revision of sssd_2.3.1-3ubuntu4 debdiff with changes to the patch
description, clarifying that the previously referred commit is included
in an upstream release already and not a part of the patch series.
** Patch added: "sssd_2.3.1-3ubuntu4-2.debdiff"
** Patch added: "sssd_2.4.0-1ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5456639/+files/sssd_2.4.0-1ubuntu4.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For Bionic (18.04) sssd_1.16.1-1ubuntu1.8.debdiff contains rules change
(--with-syslog=journald) along with upstream commits 225fe99 and 647a130
(backports for 1.16).
For Focal (20.04) sssd_2.2.3-3ubuntu0.4.debdiff contains rules change
(--with-syslog=journald) along with upstream commits 00e7b1a
Bionic and Hirsute do not have anything in -proposed currently.
Focal and Groovy are waiting on LP: #1910611 to be released out from
-proposed, and still in need of verification.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
: #970435).
This conflicts and needs to be manually resolved.
** Affects: debmirror (Ubuntu)
Importance: Undecided
Assignee: Valters Jansons (sigv)
Status: In Progress
** Changed in: debmirror (Ubuntu)
Assignee: (unassigned) => Valters Jansons (sigv)
** Chan
h "impish".
The debmirror_2.33ubuntu1-2.34ubuntu1.debdiff highlights this difference
clearly.
** Changed in: debmirror (Ubuntu)
Assignee: Valters Jansons (sigv) => (unassigned)
** Changed in: debmirror (Ubuntu)
Status: In Progress => Confirmed
--
You received th
** Patch added: "debmirror_2.34-2.34ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1926120/+attachment/5492449/+files/debmirror_2.34-2.34ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "debmirror_2.33ubuntu1-2.34ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1926120/+attachment/5492450/+files/debmirror_2.33ubuntu1-2.34ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Patch added: "sssd_1.16.1-1ubuntu1.8-2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5460573/+files/sssd_1.16.1-1ubuntu1.8-2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Upstream developers/maintainers opted to remove custom SYSLOG_IDENTIFIER
entirely, allowing the program name to be used in place. This avoids
having unexpected "[]" in the TAG.
The change is pushed as:
- 01cc267 for main branch (upstream version 2.4.1);
- 360d8fc for version 1.16 backports.
I
** Patch added: "sssd_2.2.3-3ubuntu0.4-3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5460593/+files/sssd_2.2.3-3ubuntu0.4-3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908065
Title:
Invalid SYSLOG_PID for (systemd) journal messages
To manage notifications about this bug go to:
** Patch removed: "sssd_1.16.1-1ubuntu1.8-2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5460573/+files/sssd_1.16.1-1ubuntu1.8-2.debdiff
** Patch added: "sssd_1.16.1-1ubuntu1.8-3.debdiff"
** Patch removed: "sssd_2.3.1-3ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5456636/+files/sssd_2.3.1-3ubuntu4.debdiff
** Patch removed: "sssd_2.3.1-3ubuntu4-2.debdiff"
gin
NOT required.
(Sat Feb 27 14:23:49:076640 2021) [p11_child[4287]] [read_certs] (0x4000):
found cert[X.509 Certificate for PIV
Authentication][/DC=com/DC=example/OU=Struct/CN=Valters Jansons]
(Sat Feb 27 14:23:49:076706 2021) [p11_child[4287]] [do_verification] (0x0040):
X509_verify_cert failed
LP appears to have stripped spaces from the `grep` command.
There was filtering on output to reduce verbosity.
Instead of what is seen in previous comment:
# p11-kit list-modules | grep -Eve '^ '
The actual executed verification command there is:
# p11-kit list-modules | grep -Eve '^ {5}'
--
Performing verification on Groovy (20.10)
The case for Groovy was removal of multiple square brackets from syslog
output. rsyslog was working with identifiers output such as
`be[DOMAIN.COM][1234]:` which is expected to be seen as `sssd_be[1234]:`
following the change.
# # Install current SSSD
The description was updated to reflect changes in the test case for
Groovy verification, as the initial test case was valid for Bionic and
Focal (already mitigated on Groovy from upstream).
** Description changed:
[Impact]
* On Ubuntu (Focal) 20.04, SSSD 2.2.3-3, logs in journald have
** Patch removed: "sssd_2.4.0-1ubuntu4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1908065/+attachment/5456639/+files/sssd_2.4.0-1ubuntu4.debdiff
** Patch added: "sssd_2.4.0-1ubuntu4-2.debdiff"
These latest debdiffs should include all the necessary changes and
should be ready for verification, if there are no concerns about the
material changes.
To summarize the current proposed changes:
Hirsute (21.04) and Groovy (20.10) receive commmits 1823353 and 01cc267
- one to add "sssd[]" in
Thank you! Similarly as well - feel free to ping me on IRC in case
anything comes up.
@mhodson tagged this as affecting Bionic, so I provided the patch. It
has upstream commit tags, highlighting the upstream Git repository has a
maintenance branch for 1.16 at
The fix for Hirsute is in 2.4.0-1ubuntu4 which did not get pushed
further into -release. Currently Hirsute has 2.4.0-1ubuntu5 in -proposed
(since Feb 16) with the global archive ownership rebuild.
** Changed in: sssd (Ubuntu Hirsute)
Status: Fix Released => Fix Committed
--
You received
Performing verification on Focal (20.04)
# # Install current SSSD from focal-updates (2.2.3-3ubuntu0.3)
# apt install -y sssd/focal-updates
# apt policy sssd
sssd:
Installed: 2.2.3-3ubuntu0.3
Candidate: 2.2.3-3ubuntu0.3
Version table:
2.2.3-3ubuntu0.4 400
400
** Patch added: "debmirror_2.35_2.35ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1940419/+attachment/5518755/+files/debmirror_2.35_2.35ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "debmirror_2.34ubuntu1_2.35ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1940419/+attachment/5518756/+files/debmirror_2.34ubuntu1_2.35ubuntu1.debdiff
** Changed in: debmirror (Ubuntu)
Assignee: Valters Jansons (sigv) => (unassigned
Public bug reported:
Upstream has released debmirror 1:2.35:
[ Kees Cook ]
* Remove temporary files created while verifying InRelease (closes:
#961197).
** Affects: debmirror (Ubuntu)
Importance: Undecided
Assignee: Valters Jansons (sigv)
Status: In Progress
** Description changed:
- Please update the `gist` package to the latest version in the
- repositories for 18.04 and 20.04. The current versions in those releases
- have a `gist-paste` command that can no longer authenticate to GitHub,
- making the package useless.
+ [Impact]
- I believe
The patch for v5.0.0 (Focal) looks good to me, and test case passes
locally -- I can log in and upload a Gist as expected.
I am currently not planning on providing a patch for v4.6.1 (Bionic).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Fixed upstream in
https://github.com/defunkt/gist/commit/635b1437a513e9a13367827ee3f74fbbdaa54aa8
and included in v5.1.0, which is why the v6.0.0 release in Hirsute works
as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "2-2.35ubuntu1-2.36ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+attachment/5543375/+files/2-2.35ubuntu1-2.36ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Patch added: "2-2.36-2.36ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+attachment/5543374/+files/2-2.36-2.36ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Apologies - re-uploaded debdiff, as changelog contained LP bug number
for 1:2.35 merge and not this bug.
** Patch removed: "1-2.36-2.36ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+attachment/5543372/+files/1-2.36-2.36ubuntu1.debdiff
** Patch removed:
constraint on libwww-perl and perl in Depends.
** Affects: debmirror (Ubuntu)
Importance: Undecided
Status: Confirmed
** Changed in: debmirror (Ubuntu)
Status: New => In Progress
** Changed in: debmirror (Ubuntu)
Assignee: (unassigned) => Valters Jansons (sigv)
--
You re
The diff applies Depends and Build-Depends change from Debian upstream,
while retaining quilt on Build-Depends. All patches are refreshed to
apply cleanly. In d/patches/ubuntu-settings.patch, references to Impish
(21.10) are replaced with Jammy (22.04).
--
You received this bug notification
** Patch added: "1-2.36-2.36ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/debmirror/+bug/1952248/+attachment/5543372/+files/1-2.36-2.36ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
irror (Ubuntu)
Assignee: Valters Jansons (sigv) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952248
Title:
Please merge debmirror 1:2.36 (universe) from Debian testing (
Public bug reported:
[Impact]
This release contains both bug-fixes and new features and we would like to make
sure all of our supported customers have access to these improvements.
See the changelog entry below for a list of changes.
[Test Case]
The following development and SRU process was
74 matches
Mail list logo
