[Bug 2067480] Re: MRE updates 23.11.1(Noble)/22.11.5(Mantic)/21.11.7(Jammy)
** Summary changed: - MRE updates 23.11.1 (Noble)/22.11.5(Mantic)/21.11.7(Jammy)/ + MRE updates 23.11.1(Noble)/22.11.5(Mantic)/21.11.7(Jammy) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067480 Title: MRE updates 23.11.1(Noble)/22.11.5(Mantic)/21.11.7(Jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2067480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067480] Re: MRE updates 23.11.1 (Noble)/22.11.5(Mantic)/21.11.7(Jammy)/
** Tags added: needs-mre-backport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067480 Title: MRE updates 23.11.1(Noble)/22.11.5(Mantic)/21.11.7(Jammy) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2067480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067480] Re: MRE updates 23.11.1 (Noble)/22.11.5(Mantic)/21.11.7(Jammy)/
** Description changed: 23.11.1 for Oracular is in -proposed and nearly to be completed. Therefore the MREs for Noble, Mantic and Jammy can be handled now (Mantic EOL will occur at the end of July, so we're trying to update it before it happens, but it might be optional at the end). This bug tracks an update for the DPDK packages in: - Noble 23.11 -> 23.11.1 - Mantic 22.11.4 -> 22.11.5 - Jammy 21.11.6 -> 21.11.7 This update includes bugfixes only following the SRU policy exception defined at https://wiki.ubuntu.com/StableReleaseUpdates/DPDK. No new features added; a classic stable release with a bunch of fixes aggregated and enhanced testing by the companies being part of the DPDK community. [Impact] Stable release update so not directly applicable; see the exception policy document linked above. For Reference - former cases are here: - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1784816 - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1817675 - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1836365 - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1912464 - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1940913 - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2002404 - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2026351 [Major Changes] Listed by upstream in detail Noble - 23.11.1: https://doc.dpdk.org/guides-23.11/rel_notes/release_23_11.html#release-notes Mantic - 22.11.5: https://doc.dpdk.org/guides-22.11/rel_notes/release_22_11.html#id11 - Jammy - 21.11.6: - https://doc.dpdk.org/guides-21.11/rel_notes/release_21_11.html#id17 + Jammy - 21.11.7: + https://doc.dpdk.org/guides-21.11/rel_notes/release_21_11.html#id22 + [Test Plan] See https://wiki.ubuntu.com/StableReleaseUpdates/DPDK#SRU_TestVerify [Regression Potential] Upstream performs extensive testing before release, giving us a high degree of confidence in the general case. There problems are most likely to manifest in Ubuntu-specific integrations, such as in relation to the versions of dependencies available and other packaging-specific matters. Therefore that is what our verification focuses on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067480 Title: MRE updates 23.11.1 (Noble)/22.11.5(Mantic)/21.11.7(Jammy)/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2067480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2067480] [NEW] MRE updates 23.11.1 (Noble)/22.11.5(Mantic)/21.11.7(Jammy)/
Public bug reported: 23.11.1 for Oracular is in -proposed and nearly to be completed. Therefore the MREs for Noble, Mantic and Jammy can be handled now (Mantic EOL will occur at the end of July, so we're trying to update it before it happens, but it might be optional at the end). This bug tracks an update for the DPDK packages in: - Noble 23.11 -> 23.11.1 - Mantic 22.11.4 -> 22.11.5 - Jammy 21.11.6 -> 21.11.7 This update includes bugfixes only following the SRU policy exception defined at https://wiki.ubuntu.com/StableReleaseUpdates/DPDK. No new features added; a classic stable release with a bunch of fixes aggregated and enhanced testing by the companies being part of the DPDK community. [Impact] Stable release update so not directly applicable; see the exception policy document linked above. For Reference - former cases are here: - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1784816 - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1817675 - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1836365 - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1912464 - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1940913 - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2002404 - https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2026351 [Major Changes] Listed by upstream in detail Noble - 23.11.1: https://doc.dpdk.org/guides-23.11/rel_notes/release_23_11.html#release-notes Mantic - 22.11.5: https://doc.dpdk.org/guides-22.11/rel_notes/release_22_11.html#id11 Jammy - 21.11.6: https://doc.dpdk.org/guides-21.11/rel_notes/release_21_11.html#id17 [Test Plan] See https://wiki.ubuntu.com/StableReleaseUpdates/DPDK#SRU_TestVerify [Regression Potential] Upstream performs extensive testing before release, giving us a high degree of confidence in the general case. There problems are most likely to manifest in Ubuntu-specific integrations, such as in relation to the versions of dependencies available and other packaging-specific matters. Therefore that is what our verification focuses on. ** Affects: dpdk (Ubuntu) Importance: Undecided Assignee: Miriam España Acebal (mirespace) Status: New ** Affects: dpdk (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: dpdk (Ubuntu Mantic) Importance: Undecided Status: New ** Affects: dpdk (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: dpdk (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: dpdk (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: dpdk (Ubuntu Mantic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067480 Title: MRE updates 23.11.1 (Noble)/22.11.5(Mantic)/21.11.7(Jammy)/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2067480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064391] Re: Merge bridge-utils from Debian unstable for oracular
** Changed in: bridge-utils (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064391 Title: Merge bridge-utils from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/2064391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064391] Re: Merge bridge-utils from Debian unstable for oracular
** Merge proposal linked: https://code.launchpad.net/~mirespace/ubuntu/+source/bridge-utils/+git/bridge-utils/+merge/466451 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064391 Title: Merge bridge-utils from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/2064391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063046] Re: build-depends on obsolete python3-nose-timer
python3-nose-timer was added in 5685bc3b683473fd6a36e32a18b45c14e1b9ec6b by us (as Ubuntu developers) for making unittest work. Searching on upstream, from python 3.10, they use pytest instead of nose: WALinuxAgent: Run unit tests with pytest on Python >= 3.10 CLOSED [1] Therefore, we need to make changes as a consequence. [1] https://github.com/Azure/WALinuxAgent/pull/3081 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063046 Title: build-depends on obsolete python3-nose-timer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/2063046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061991] Re: FTBFS - FAIL: TestTimezoneAmericasCompileFileAndParse
telegraf package was finally removed from the Archive: please, see [1] for more info. [1] https://bugs.launchpad.net/ubuntu/+source/telegraf/+bug/2062013 ** Changed in: telegraf (Ubuntu) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061991 Title: FTBFS - FAIL: TestTimezoneAmericasCompileFileAndParse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegraf/+bug/2061991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2063046] Re: build-depends on obsolete python3-nose-timer
** Changed in: walinuxagent (Ubuntu) Assignee: (unassigned) => Miriam España Acebal (mirespace) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2063046 Title: build-depends on obsolete python3-nose-timer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/2063046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2064391] Re: Merge bridge-utils from Debian unstable for oracular
** Changed in: bridge-utils (Ubuntu) Assignee: (unassigned) => Miriam España Acebal (mirespace) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2064391 Title: Merge bridge-utils from Debian unstable for oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/2064391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2042356] Re: [SRU] wminput crashes with ImportError: ... undefined symbol: PyVarObject_CallFunction
Hi Sudip! I reviewed the patch, and I have a few questions: - The patch seems to be one of the commits of the MR accepted on Debian on 976439 (the last one in fact). Would the commit a7ac2dbdc122115b5603f595c56cc55a6f09dca3 "Also add libwiicd patches. " be needed? - The patch is for commit https://salsa.debian.org/georgesk/cwiid/-/blob/e7cebe40c94b05e97f07302c36e93f60482b0ae5/debian/patches/python3-build-azzra, but is not completely imported: - Makefile.in is not imported in the patch (maybe is this related to the commit a7ac2db (the one I pointed to in the previous question?) Why are some parts of the original commit (change comments, e.g.) not imported into the patch? Could you give us more information about this elections? I build the package with the patch (it builds OK) and I didn't test yet -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2042356 Title: [SRU] wminput crashes with ImportError: ... undefined symbol: PyVarObject_CallFunction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cwiid/+bug/2042356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061966] Re: FTBFS on armfh - error: too few arguments to function ‘gettimeofday’
I found a promising fix upstream for "update autoconfig files": https://github.com/backuppc/rsync- bpc/commit/ce3ce3061c2acc4c78693953d6a1a2cf50145fe2#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810L855 with a lot of changes of "main" by "int main(void)" as can be seen i.e. at: https://github.com/backuppc/rsync- bpc/commit/ce3ce3061c2acc4c78693953d6a1a2cf50145fe2#diff-49473dca262eeab3b4a43002adb08b4db31020d190caaad1594b47f1d5daa810L878 and with a later commit for one more missing: https://github.com/backuppc/rsync-bpc/pull/34/files The first commit is big: checking if all the changes are needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061966 Title: FTBFS on armfh - error: too few arguments to function ‘gettimeofday’ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc-rsync/+bug/2061966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061966] Re: FTBFS on armfh - error: too few arguments to function ‘gettimeofday’
** Changed in: backuppc-rsync (Ubuntu) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: backuppc-rsync (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061966 Title: FTBFS on armfh - error: too few arguments to function ‘gettimeofday’ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc-rsync/+bug/2061966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061991] Re: FTBFS - FAIL: TestTimezoneAmericasCompileFileAndParse
** Changed in: telegraf (Ubuntu) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: telegraf (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061991 Title: FTBFS - FAIL: TestTimezoneAmericasCompileFileAndParse To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegraf/+bug/2061991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061991] [NEW] FTBFS - FAIL: TestTimezoneAmericasCompileFileAndParse
Public bug reported:
In a recent rebuild on the server team, amd64 arm64 ppc64el s390x arch
builds were failing due to:
2024/04/16 20:54:12 E! [] Error parsing foobar to timestamp: strconv.ParseInt:
parsing "foobar": invalid syntax
2024/04/16 20:54:12 E! [] Error parsing foobar to int: strconv.ParseInt:
parsing "foobar": invalid syntax
2024/04/16 20:54:12 E! [] Error parsing timestamp [foobar], could not find any
suitable time layouts.
2024/04/16 20:54:12 D! [] Grok no match found for: "1.25 200 192.168.1.1
5.432µs"
2024/04/16 20:54:12 D! [] Grok no match found for: "[04/Jun/2016:12:41:45
+0100] notnumber 200 192.168.1.1 5.432µs 101"
2024/04/16 20:54:12 E! [] Error parsing notnumber to int: strconv.ParseInt:
parsing "notnumber": invalid syntax
2024/04/16 20:54:12 E! [] Error parsing notnumber to float: strconv.ParseFloat:
parsing "notnumber": invalid syntax
2024/04/16 20:54:12 E! [] Error parsing notnumber to duration: time: invalid
duration "notnumber"
2024/04/16 20:54:12 E! [] Error parsing notnumber to duration: time: invalid
duration "notnumber"
2024/04/16 20:54:12 W! [] Improper timezone supplied (Something/Weird), setting
loc to UTC
--- FAIL: TestTimezoneAmericasCompileFileAndParse (0.01s)
panic: runtime error: invalid memory address or nil pointer dereference
[recovered]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x50 pc=0x6b2066]
goroutine 82 [running]:
testing.tRunner.func1.2({0x6f49a0, 0x9ba620})
/usr/lib/go-1.22/src/testing/testing.go:1631 +0x24a
testing.tRunner.func1()
/usr/lib/go-1.22/src/testing/testing.go:1634 +0x377
panic({0x6f49a0?, 0x9ba620?})
/usr/lib/go-1.22/src/runtime/panic.go:770 +0x132
github.com/influxdata/telegraf/plugins/parsers/grok.(*Parser).Compile(0xc00013fe70)
/<>/plugins/parsers/grok/parser.go:184 +0x8a6
github.com/influxdata/telegraf/plugins/parsers/grok.TestTimezoneAmericasCompileFileAndParse(0xc000456820)
/<>/plugins/parsers/grok/parser_test.go:911 +0x10a
testing.tRunner(0xc000456820, 0x7722a0)
/usr/lib/go-1.22/src/testing/testing.go:1689 +0xfb
created by testing.(*T).Run in goroutine 1
A debugging session shows that the improper timezone supplied is
error(*errors.errorString) *{s: "unknown time zone Canada/Eastern"}
From
grok.(*Parser).Compile
(/media/miriam/extension/Code/packages/telegraf/telegraf-
gu/plugins/parsers/grok/parser.go:182)
it tries to load /usr/share/zoneinfo//Canada/Eastern which doesn't exist
, via time.LoadLocation -> loadTzinfo -> loadTzinfoFromDirOrZip
That file exists in tzdata-legacy package:
root@Ntzdata:~# apt-file search Canada/Eastern
Finding relevant cache files to search
tzdata-legacy: /usr/share/zoneinfo/Canada/Eastern
tzdata-legacy: /usr/share/zoneinfo/right/Canada/Eastern
It might be possible that we need to add tzdata-legacy as a dependency
** Affects: telegraf (Ubuntu)
Importance: Undecided
Assignee: Miriam España Acebal (mirespace)
Status: In Progress
** Tags: ftbfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061991
Title:
FTBFS - FAIL: TestTimezoneAmericasCompileFileAndParse
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telegraf/+bug/2061991/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061966] Re: FTBFS on armfh - error: too few arguments to function ‘gettimeofday’
** Changed in: backuppc-rsync (Ubuntu) Status: In Progress => New ** Changed in: backuppc-rsync (Ubuntu) Assignee: Miriam España Acebal (mirespace) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061966 Title: FTBFS on armfh - error: too few arguments to function ‘gettimeofday’ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc-rsync/+bug/2061966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061966] Re: FTBFS on armfh - error: too few arguments to function ‘gettimeofday’
** Bug watch added: Debian Bug tracker #1066438 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066438 ** Also affects: backuppc-rsync (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066438 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061966 Title: FTBFS on armfh - error: too few arguments to function ‘gettimeofday’ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc-rsync/+bug/2061966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061966] [NEW] FTBFS on armfh - error: too few arguments to function ‘gettimeofday’
Public bug reported: lib/compat.c:154:16: error: too few arguments to function ‘gettimeofday’ 154 | return gettimeofday(tv); |^~~~ In file included from /usr/include/features.h:502, from /usr/include/arm-linux-gnueabihf/bits/libc-header-start.h:33, from /usr/include/stdio.h:28, from ./rsync.h:318, from lib/compat.c:22: /usr/include/arm-linux-gnueabihf/sys/time.h:71:12: note: declared here 71 | extern int __REDIRECT_NTH (gettimeofday, (struct timeval *__restrict __tv, |^~ lib/compat.c:156:1: warning: control reaches end of non-void function [-Wreturn-type] 156 | } | ^ from armhf buildlog [1] [1] https://launchpadlibrarian.net/724113685/buildlog_ubuntu-noble- armhf.backuppc-rsync_3.1.3.0-3build2_BUILDING.txt.gz ** Affects: backuppc-rsync (Ubuntu) Importance: Undecided Assignee: Miriam España Acebal (mirespace) Status: In Progress ** Affects: backuppc-rsync (Debian) Importance: Unknown Status: Unknown ** Tags: ftbfs ** Changed in: backuppc-rsync (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061966 Title: FTBFS on armfh - error: too few arguments to function ‘gettimeofday’ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backuppc-rsync/+bug/2061966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061865] Re: [FFe] [24.04 FEAT] Upload libmail-dmarc-perl
Yes to all your questions Paride, thanks for your help on this! The MP corresponds to the package uploaded at https://launchpad.net/~mirespace/+archive/ubuntu/libmail-dmarc-perl- suggested I double checked in [1] that this package installs the packages in universe that were finally considered to be part of the MIR with the spamassassin package from LP:2061379 : libclass-inspector-perl universe libemail-simple-perl universe libfile-sharedir-perl universe libnet-ip-perl universe libregexp-common-perl universe libmail-dmarc-perl universe [1] https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971/comments/29 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061865 Title: [FFe] [24.04 FEAT] Upload libmail-dmarc-perl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2061865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061865] [NEW] [FFe] [24.04 FEAT] Upload libmail-dmarc-perl
Public bug reported: Feature Freeze Exception (FFe): --- I completely forgot to fill this counterpart of LP:2061379. A MIR process has been carried out to promote libmail-dmarc-perl to main (LP:2023971), which has been ack recently by MIR Team [3] and by Security Team [4]. I reproduce the rationale we gave there: tldr; DMARC support in SpamAssassin is important for stronger spam filtering. Spam email is an ever-present and ever-evolving presence in our online lives, and SpamAssassin is a key tool for end users and service providers to identify likely spam for filtering. SpamAssassin 4.0, introduced in Ubuntu "lunar" 22.10, introduced a number of major new features including three new plugins, the most significant of which is the DMARC policy checker. DMARC (or "Domain-based Message Authentication, Reporting & Conformance" https://dmarc.org/) is a new convention for email service providers to communicate to email recipient programs about how to handle authentication failures. It builds on prior protocols (namely, SPF and DKIM) to address their limitations. Essentially, DMARC protects against direct domain spoofing, such that when an email purports to be from a given domain (say, @gmail.com or @irs.gov) but fails proper authentication using the authentication methods published by that domain, it tells the email receiver whether to reject the email as spam, quarantine it for evaluation, or something else. DMARC also establishes a way for the email receiver to give feedback back to the sender about emails that failed to pass this check. libmail-dmarc-perl contains the official Perl implementation of DMARC support. SpamAssassin is the primary user of this package The new package should not break any other packages that depend on it. In the MIR bug for dmarc, the use of this feature with spamassassin has been tested [1] and dep-8 tests has been added to libmail-dmarc-perl too. Installation of the spamassassin package with dmarc to be promoted has been tested at [2]. Final review before the upload is taking place for polishment purposes (usual things like changelog, maintainer and commit ordering or squashing...I will ink the MP). The 'ubuntu-release' team could finally be subscribed to allow the promotion. [1] https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971/comments/26 [2] https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971/comments/29 [3] https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971/comments/18 [4] https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971/comments/24 - Please, allow the upload of the libmail-dmarc-perl package proposed here to be promoted to main following the MIR process ( it needs to be seen in the component mismatches graph before promotion). ** Affects: libmail-dmarc-perl (Ubuntu) Importance: Undecided Status: New ** Tags: ubuntu-release ** Merge proposal linked: https://code.launchpad.net/~mirespace/ubuntu/+source/libmail-dmarc-perl/+git/libmail-dmarc-perl/+merge/464196 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061865 Title: [FFe] [24.04 FEAT] Upload libmail-dmarc-perl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2061865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061833] Re: [FFe] FTBFS on armfh - error: #error ANSI C compiler without void or unsigned char or prototypes
** Description changed: + Feature Freeze Exception (FFe): + --- + + This ftbfs for this package on main has been fixed on Debian and new + version is in the publishing history of the package at + https://launchpad.net/debian/+source/uucp/1.07-29 + + I downloaded the source from Debian and I made a rebuild on a ppa: + + https://launchpad.net/~mirespace/+archive/ubuntu/fixing-general-noble- + packages/+sourcepub/15971907/+listing-archive-extra + + The new package should not break any other packages that depend on it. + Please, allow the sync. + + --- The relevant portion of the build log for armhf [1] is : make[4]: Entering directory '/<>/lib' gcc -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 -I.. -I./.. -W -Wall -Wstrict-prototypes -Wmissing-prototypes -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-stack-clash-protection -fdebug-prefix-map=/<>=/usr/src/uucp-1.07-28build1 -Wall -g -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 -O2 -MT buffer.o -MD -MP -MF .deps/buffer.Tpo -c -o buffer.o buffer.c In file included from buffer.c:25: ../uucp.h:103:3: error: #error ANSI C compiler withou-D_LARGEFILE_SOURCE-D_LARGEFILE_SOURCEt void or unsigned char or prototypes - 103 | #error ANSI C compiler without void or unsigned char or prototypes - | ^ + 103 | #error ANSI C compiler without void or unsigned char or prototypes + | ^ make[4]: *** [Makefile:355: buffer.o] Error 1 Previous successful build [2] for the same architecture has the following compiler command line: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I.. -I./.. -W -Wall -Wstrict-prototypes -Wmissing-prototypes -g -O2 -ffile- prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fdebug-prefix- map=/<>=/usr/src/uucp-1.07-28 -Wall -g -Wl,-Bsymbolic- functions -Wl,-z,relro -Wl,-z,now -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -MT buffer.o -MD -MP -MF .deps/buffer.Tpo -c -o buffer.o buffer.c So new flags added in current attempt to build are: -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -D_FORTIFY_SOURCE=3 -Werror=implicit-function-declaration -fno-stack-clash-protection [1] https://launchpadlibrarian.net/724114099/buildlog_ubuntu-noble-armhf.uucp_1.07-28build1_BUILDING.txt.gz [2] https://launchpadlibrarian.net/694347390/buildlog_ubuntu-noble-armhf.uucp_1.07-28_BUILDING.txt.gz ** Tags added: ubuntu-release ** Description changed: Feature Freeze Exception (FFe): --- This ftbfs for this package on main has been fixed on Debian and new version is in the publishing history of the package at https://launchpad.net/debian/+source/uucp/1.07-29 - I downloaded the source from Debian and I made a rebuild on a ppa: + I downloaded the source from Debian and I made a rebuild on a ppa to + check the build itself on our infra: https://launchpad.net/~mirespace/+archive/ubuntu/fixing-general-noble- packages/+sourcepub/15971907/+listing-archive-extra The new package should not break any other packages that depend on it. Please, allow the sync. --- The relevant portion of the build log for armhf [1] is : make[4]: Entering directory '/<>/lib' gcc -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 -I.. -I./.. -W -Wall -Wstrict-prototypes -Wmissing-prototypes -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-stack-clash-protection -fdebug-prefix-map=/<>=/usr/src/uucp-1.07-28build1 -Wall -g -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 -O2 -MT buffer.o -MD -MP -MF .deps/buffer.Tpo -c -o buffer.o buffer.c In file included from buffer.c:25: ../uucp.h:103:3: error: #error ANSI C compiler withou-D_LARGEFILE_SOURCE-D_LARGEFILE_SOURCEt void or unsigned char or prototypes 103 | #error ANSI C compiler without void or unsigned char or prototypes | ^ make[4]: *** [Makefile:355: buffer.o] Error 1 Previous successful build [2] for the same architecture has the following compiler command line: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I.. -I./.. -W -Wall -Wstrict-prototypes -Wmissing-prototypes -g -O2 -ffile- prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fdebug-prefix- map=/<>=/usr/src/uucp-1.07-28 -Wall -g -Wl,-Bsymbolic- functions -Wl,-z,relro -Wl,-z,now
[Bug 2061833] Re: [FFe] FTBFS on armfh - error: #error ANSI C compiler without void or unsigned char or prototypes
** Summary changed: - FTBFS on armfh - error: #error ANSI C compiler without void or unsigned char or prototypes + [FFe] FTBFS on armfh - error: #error ANSI C compiler without void or unsigned char or prototypes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061833 Title: [FFe] FTBFS on armfh - error: #error ANSI C compiler without void or unsigned char or prototypes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uucp/+bug/2061833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061833] Re: FTBFS on armfh - error: #error ANSI C compiler without void or unsigned char or prototypes
** Changed in: uucp (Ubuntu) Assignee: (unassigned) => Miriam España Acebal (mirespace) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061833 Title: [FFe] FTBFS on armfh - error: #error ANSI C compiler without void or unsigned char or prototypes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uucp/+bug/2061833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061833] [NEW] FTBFS on armfh - error: #error ANSI C compiler without void or unsigned char or prototypes
Public bug reported: The relevant portion of the build log for armhf [1] is : make[4]: Entering directory '/<>/lib' gcc -DHAVE_CONFIG_H -I. -I.. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 -I.. -I./.. -W -Wall -Wstrict-prototypes -Wmissing-prototypes -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fno-stack-clash-protection -fdebug-prefix-map=/<>=/usr/src/uucp-1.07-28build1 -Wall -g -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=3 -O2 -MT buffer.o -MD -MP -MF .deps/buffer.Tpo -c -o buffer.o buffer.c In file included from buffer.c:25: ../uucp.h:103:3: error: #error ANSI C compiler withou-D_LARGEFILE_SOURCE-D_LARGEFILE_SOURCEt void or unsigned char or prototypes 103 | #error ANSI C compiler without void or unsigned char or prototypes | ^ make[4]: *** [Makefile:355: buffer.o] Error 1 Previous successful build [2] for the same architecture has the following compiler command line: gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -I.. -I./.. -W -Wall -Wstrict-prototypes -Wmissing-prototypes -g -O2 -ffile- prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fdebug-prefix- map=/<>=/usr/src/uucp-1.07-28 -Wall -g -Wl,-Bsymbolic- functions -Wl,-z,relro -Wl,-z,now -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -MT buffer.o -MD -MP -MF .deps/buffer.Tpo -c -o buffer.o buffer.c So new flags added in current attempt to build are: -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -D_FORTIFY_SOURCE=3 -Werror=implicit-function-declaration -fno-stack-clash-protection [1] https://launchpadlibrarian.net/724114099/buildlog_ubuntu-noble-armhf.uucp_1.07-28build1_BUILDING.txt.gz [2] https://launchpadlibrarian.net/694347390/buildlog_ubuntu-noble-armhf.uucp_1.07-28_BUILDING.txt.gz ** Affects: uucp (Ubuntu) Importance: Undecided Status: New ** Affects: uucp (Debian) Importance: Unknown Status: Unknown ** Tags: ftbfs ** Bug watch added: Debian Bug tracker #1066434 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066434 ** Also affects: uucp (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066434 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061833 Title: FTBFS on armfh - error: #error ANSI C compiler without void or unsigned char or prototypes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uucp/+bug/2061833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061833] Re: FTBFS on armfh - error: #error ANSI C compiler without void or unsigned char or prototypes
Fixed on Debian: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1066434#10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061833 Title: FTBFS on armfh - error: #error ANSI C compiler without void or unsigned char or prototypes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uucp/+bug/2061833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023971] Re: [MIR] libmail-dmarc-perl
FFe granted at https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/2061379/comments/1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023971 Title: [MIR] libmail-dmarc-perl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061379] Re: [FFe] [24.04 FEAT] Allow dmarc features on spamassassin
** Tags added: ubuntu-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061379 Title: [FFe] [24.04 FEAT] Allow dmarc features on spamassassin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/2061379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061370] Re: FTBFS on armfh - implicit-function-declaration
** Merge proposal linked: https://code.launchpad.net/~mirespace/ubuntu/+source/radvd/+git/radvd/+merge/464328 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061370 Title: FTBFS on armfh - implicit-function-declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/radvd/+bug/2061370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061370] Re: FTBFS on armfh - implicit-function-declaration
** Changed in: radvd (Ubuntu) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: radvd (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061370 Title: FTBFS on armfh - implicit-function-declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/radvd/+bug/2061370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061379] Re: [FFe] [24.04 FEAT] Allow dmarc features on spamassassin
** Merge proposal linked: https://code.launchpad.net/~mirespace/ubuntu/+source/spamassassin/+git/spamassassin/+merge/464206 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061379 Title: [FFe] [24.04 FEAT] Allow dmarc features on spamassassin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/2061379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061379] [NEW] [FFe] [24.04 FEAT] Allow dmarc features on spamassassin
Public bug reported: Feature Freeze Exception (FFe): --- To avoid a component mismatched issue, libmail-dmarc-perl was demoted to Suggested from Recommends in spamassassin version 4.0.0-7ubuntu1 on mantic. A MIR process has been carried out to promote libmail-dmarc-perl to main (LP:2023971), which has been ack recently. I reproduce the rationale we gave there: tldr; DMARC support in SpamAssassin is important for stronger spam filtering. Spam email is an ever-present and ever-evolving presence in our online lives, and SpamAssassin is a key tool for end users and service providers to identify likely spam for filtering. SpamAssassin 4.0, introduced in Ubuntu "lunar" 22.10, introduced a number of major new features including three new plugins, the most significant of which is the DMARC policy checker. DMARC (or "Domain-based Message Authentication, Reporting & Conformance" https://dmarc.org/) is a new convention for email service providers to communicate to email recipient programs about how to handle authentication failures. It builds on prior protocols (namely, SPF and DKIM) to address their limitations. Essentially, DMARC protects against direct domain spoofing, such that when an email purports to be from a given domain (say, @gmail.com or @irs.gov) but fails proper authentication using the authentication methods published by that domain, it tells the email receiver whether to reject the email as spam, quarantine it for evaluation, or something else. DMARC also establishes a way for the email receiver to give feedback back to the sender about emails that failed to pass this check. libmail-dmarc-perl contains the official Perl implementation of DMARC support. SpamAssassin is the primary user of this package The new package should not break any other packages that depend on it. In the MIR bug for dmarc, the use of this feature with spamassassin has been tested [1] and dep-8 tests has been added to libmail-dmarc-perl too. Installation of the spamassassin package with dmarc to be promoted has been tested at [2]. The 'ubuntu-release' team could finally be subscribed to allow the promotion. [1] https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971/comments/26 [2] https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971/comments/29 - Move back libmail-dmarc-perl as a Recommends dependency from Suggested. ** Affects: spamassassin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061379 Title: [FFe] [24.04 FEAT] Allow dmarc features on spamassassin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/2061379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023971] Re: [MIR] libmail-dmarc-perl
Version of spamassassin using dmarc has been uploaded to [1] . I'm
opening a FFe for spamassassin for this.
Using the libmail-dmarc-perl package that has been ack to be MIRed that
is at [2], we can confirm the installation of both and the packages to
finally be promoted (that coincides with the summary at the beginning of
the description):
#1 Checking smapassassin and libmail-dmarc-perl version to be installed
if we do am 'apt install spamassassin' in Noble with the spamassassin
package in PPA for FFe.
root@Ndmarc-final:~# apt-cache policy libmail-dmarc-perl
libmail-dmarc-perl:
Installed: (none)
Candidate: 1.20230215-1ubuntu1~mirespace10
Version table:
1.20230215-1ubuntu1~mirespace10 500
500
https://ppa.launchpadcontent.net/mirespace/libmail-dmarc-perl-suggested/ubuntu
noble/main amd64 Packages
1.20230215-1 500
500 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages
root@Ndmarc-final:~# apt-cache policy spamassassin
spamassassin:
Installed: (none)
Candidate: 4.0.0-8ubuntu5
Version table:
4.0.0-8ubuntu5 500
500
https://ppa.launchpadcontent.net/mirespace/spamassassin-dmarc-mir/ubuntu
noble/main amd64 Packages
4.0.0-8ubuntu4 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
#2 Checking packages in universe for this, to get the list to be
promoted finally:
root@Ndmarc-final:~# for p in $(apt install -s spamassassin | grep Inst
| cut -d' ' -f2); do echo -n ${p} && echo -n " " && apt-cache policy
${p} | grep archive.ubuntu | cut -d'/' -f5 | cut -d' ' -f1 ; done |
grep universe
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
libclass-inspector-perl universe
libemail-simple-perl universe
libfile-sharedir-perl universe
libnet-ip-perl universe
libregexp-common-perl universe
libmail-dmarc-perl universe
[1] https://launchpad.net/~mirespace/+archive/ubuntu/spamassassin-dmarc-mir
[2]
https://launchpad.net/~mirespace/+archive/ubuntu/libmail-dmarc-perl-suggested
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2023971
Title:
[MIR] libmail-dmarc-perl
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061370] [NEW] FTBFS on armfh - implicit-function-declaration
Public bug reported: gram.c: In function ‘yyparse’: gram.c:1531:16: error: implicit declaration of function ‘yylex’ [-Werror=implicit-function-declaration] 1531 | yychar = yylex (); |^ gram.y: In function ‘readin_config’: gram.y:957:17: error: implicit declaration of function ‘yyset_in’ [-Werror=implicit-function-declaration] 957 | yyset_in(in); | ^~~~ gram.y:965:17: error: implicit declaration of function ‘yylex_destroy’ [-Werror=implicit-function-declaration] 965 | yylex_destroy(); | ^ from Buildlog armhf [1]. Upstream's fix is at [2]. [1] https://launchpadlibrarian.net/724114432/buildlog_ubuntu-noble-armhf.radvd_1%3A2.19-1build1_BUILDING.txt.gz [2] https://github.com/radvd-project/radvd/pull/196/commits ** Affects: radvd (Ubuntu) Importance: Undecided Status: New ** Affects: radvd (Debian) Importance: Unknown Status: Unknown ** Tags: ftbfs ** Bug watch added: Debian Bug tracker #1066224 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066224 ** Also affects: radvd (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066224 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061370 Title: FTBFS on armfh - implicit-function-declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/radvd/+bug/2061370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040463] Re: MRE updates of dpdk in the 24.04 cycle
On Jammy, testing upgrading path, removing : All OK. (Installation was tested with the internal tests). ## Upgrading #Installing previous version: root@Mdpdk:~# apt install dpdk [...] root@Jdpdk:~# dpkg -l dpdk | grep ii ii dpdk 21.11.4-0ubuntu0.22.04.1 amd64Data Plane Development Kit (runtime) #Upgrading root@Jdpdk:~# apt list --upgradable | grep dpdk dpdk/jammy-proposed 21.11.6-0ubuntu0.22.04.1 amd64 [upgradable from: 21.11.4-0ubuntu0.22.04.1] root@Jdpdk:~# apt upgrade dpdk root@Jdpdk:~# apt upgrade dpdk Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: apparmor dpdk initramfs-tools initramfs-tools-bin initramfs-tools-core landscape-common libapparmor1 libgcrypt20 libicu70 librte-bus-auxiliary22 librte-bus-pci22 librte-bus-vdev22 librte-bus-vmbus22 librte-common-mlx5-22 librte-cryptodev22 librte-eal22 librte-ethdev22 librte-gso22 librte-hash22 librte-ip-frag22 librte-kni22 librte-kvargs22 librte-mbuf22 librte-mempool-ring22 librte-mempool22 librte-meter22 librte-net-af-packet22 librte-net-bond22 librte-net-e1000-22 librte-net-fm10k22 librte-net-i40e22 librte-net-ixgbe22 librte-net-kni22 librte-net-mlx4-22 librte-net-mlx5-22 librte-net-netvsc22 librte-net-pcap22 librte-net-tap22 librte-net-thunderx22 librte-net-vdev-netvsc22 librte-net-vhost22 librte-net-virtio22 librte-net-vmxnet3-22 librte-net22 librte-pci22 librte-rcu22 librte-ring22 librte-sched22 librte-security22 librte-telemetry22 librte-vhost22 libxmlb2 openssh-client openssh-server openssh-sftp-server ubuntu-advantage-tools ubuntu-minimal ubuntu-pro-client ubuntu-pro-client-l10n ubuntu-server ubuntu-standard 61 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 15.8 MB of archives. After this operation, 59.4 kB of additional disk space will be used. Do you want to continue? [Y/n] root@Jdpdk:~# apt-cache policy dpdk dpdk: Installed: 21.11.6-0ubuntu0.22.04.1 Candidate: 21.11.6-0ubuntu0.22.04.1 Version table: *** 21.11.6-0ubuntu0.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 21.11.4-0ubuntu0.22.04.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 21.11.2-0ubuntu0.22.04.1 500 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 21.11-1build1 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages #Removing after upgrade root@Jdpdk:~# apt remove --purge dpdk Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: ibverbs-providers libfdt1 libibverbs1 libnl-route-3-200 librte-bus-auxiliary22 librte-bus-pci22 librte-bus-vdev22 librte-bus-vmbus22 librte-common-mlx5-22 librte-cryptodev22 librte-eal22 librte-ethdev22 librte-gso22 librte-hash22 librte-ip-frag22 librte-kni22 librte-kvargs22 librte-mbuf22 librte-mempool-ring22 librte-mempool22 librte-meter22 librte-net-af-packet22 librte-net-bond22 librte-net-e1000-22 librte-net-fm10k22 librte-net-i40e22 librte-net-ixgbe22 librte-net-kni22 librte-net-mlx4-22 librte-net-mlx5-22 librte-net-netvsc22 librte-net-pcap22 librte-net-tap22 librte-net-thunderx22 librte-net-vdev-netvsc22 librte-net-vhost22 librte-net-virtio22 librte-net-vmxnet3-22 librte-net22 librte-pci22 librte-rcu22 librte-ring22 librte-sched22 librte-security22 librte-telemetry22 librte-vhost22 python3-pyelftools rdma-core Use 'apt autoremove' to remove them. The following packages will be REMOVED: dpdk* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 133 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 79253 files and directories currently installed.) Removing dpdk (21.11.6-0ubuntu0.22.04.1) ... (Reading database ... 79242 files and directories currently installed.) Purging configuration files for dpdk (21.11.6-0ubuntu0.22.04.1) ... ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040463 Title: MRE updates of dpdk in the 24.04 cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040463] Re: MRE updates of dpdk in the 24.04 cycle
Jammy proposed internal tests passed OK: ubuntu@node-horsea:~/dpdk-testing$ cat dpdk-test.status PHYS_TESTPMD VIRT_SPAWNGUESTS VIRT_TESTPMD VIRT_L2FWD BENCH_OVS VUC_BENCH_OVSDPDK VUC_ENDURANCE_STARTSTOP VUC_ENDURANCE_ADDREMOVEPORT 1.0.0 (20:30:52): phys (BM) tests 1.1.0 (20:30:52): initialize environment 1.1.1 (20:34:18): testpmd => Pass 1.1.2 (20:35:35): check testpmd output => Pass 2.0.0 (20:35:35): prep virtual test environment 1.0.0 (20:38:46): virt tests 1.1.0 (20:38:46): initialize environment 3.0.0 (20:39:34): performance tests 3.1.0 (20:39:34): prep benchmarks 3.2.0 (20:40:58): performance tests 3.2.1 (20:41:06): test guest-openvswitch for OVS-5CPU => Pass 3.2.2 (21:00:31): test guest-dpdk-vhost-user-client-multiq for OVSDPDK-VUC => Pass 4.0.0 (21:20:13): VUC endurance checks 4.1.0 (21:20:13): prep VUC endurance tests 4.1.1 (21:34:44): start stop guests (client) => Pass 4.1.2 (22:39:04): add/remove ports (client) => Pass 4.2.0 (22:48:37): Final cleanup ubuntu@node-horsea:~/dpdk-testing$ dpkg -l dpdk Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==--- ii dpdk 21.11.6-0ubuntu0.22.04.1 amd64Data Plane Development Kit (runtime) ** Attachment added: "output.log" https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040463/+attachment/5763983/+files/output.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040463 Title: MRE updates of dpdk in the 24.04 cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061039] [NEW] FTBFS on armhf (implicit-function-declaration) and riscv64 (error: expected ‘)’ before ‘CPUINFO’ )
Public bug reported:
For armhf [1]:
/<>/src/tools/adcclient.c:178:33: error: implicit declaration of
function ‘ADC_client_connect_internal’; did you mean ‘ADC_client_connect’?
[-Werror=implicit-function-declaration]
178 | ADC_client_connect_internal(client);
| ^~~
| ADC_client_connect
For riscv64 [2]:
/<>/src/core/commands.c:395:86: error: expected ‘)’ before
‘CPUINFO’
395 | buf = cbuf_create_const("Powered by " PRODUCT_STRING "
on " OPSYS "/" CPUINFO);
|~
^~~~
|
[...]
/<>/src/core/commands.c:395:86: error: expected ‘)’ before
‘CPUINFO’
395 | buf = cbuf_create_const("Powered by " PRODUCT_STRING "
on " OPSYS "/" CPUINFO);
|~
^~~~
|
[1]
https://launchpadlibrarian.net/724118191/buildlog_ubuntu-noble-armhf.uhub_0.4.1-3.2build2_BUILDING.txt.gz
[2]
https://launchpadlibrarian.net/724118080/buildlog_ubuntu-noble-riscv64.uhub_0.4.1-3.2build2_BUILDING.txt.gz
** Affects: uhub (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061039
Title:
FTBFS on armhf (implicit-function-declaration) and riscv64 (error:
expected ‘)’ before ‘CPUINFO’ )
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/uhub/+bug/2061039/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061038] Re: FTBFS on armfh - implicit-function-declaration
Upstream's repo might be the one with this issue https://github.com/mufti11/white_dune/issues/3# . Repo in the control file doesn't exist. There is also https://bugs.launchpad.net/ubuntu/+source/whitedune/+bug/1828832 for upgrading to a major and supposed continued version, but Debian is not there yet. ** Bug watch added: github.com/mufti11/white_dune/issues #3 https://github.com/mufti11/white_dune/issues/3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061038 Title: FTBFS on armfh - implicit-function-declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whitedune/+bug/2061038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061038] [NEW] FTBFS on armfh - implicit-function-declaration
Public bug reported: y.tab.c:2666:7: error: implicit declaration of function 'yyerror'; did you mean 'yyerrok'? [-Werror=implicit-function-declaration] rcparse.y: In function 'newBitmap': rcparse.y:737:9: warning: ignoring return value of 'fread' declared with attribute 'warn_unused_result' [-Wunused-result] 737 | fread(bitmap->data + (bitmap->height - 1 - y) * width_in_bytes, | ^~~ 738 | 1, width_in_bytes, f); | ~ [...] linux/SDL_sysjoystick.c:525:9: error: implicit declaration of function ‘SDL_PrivateJoystickHat’ [-Werror=implicit-function-declaration] 525 | SDL_PrivateJoystickHat(stick, hat, | ^~ linux/SDL_sysjoystick.c: In function ‘JS_HandleEvents’: linux/SDL_sysjoystick.c:567:21: error: implicit declaration of function ‘SDL_PrivateJoystickAxis’ [-Werror=implicit-function-declaration] 567 | SDL_PrivateJoystickAxis(joystick, | ^~~ linux/SDL_sysjoystick.c:598:17: error: implicit declaration of function ‘SDL_PrivateJoystickButton’ [-Werror=implicit-function-declaration] 598 | SDL_PrivateJoystickButton(joystick, | ^ linux/SDL_sysjoystick.c: In function ‘SDL_SYS_JoystickUpdate’: linux/SDL_sysjoystick.c:717:13: error: implicit declaration of function ‘SDL_PrivateJoystickBall’ [-Werror=implicit-function-declaration] 717 | SDL_PrivateJoystickBall(joystick, (Uint8)i, xrel, yrel); | ^~~ from https://launchpadlibrarian.net/724118904/buildlog_ubuntu-noble- armhf.whitedune_0.30.10-2.2build4_BUILDING.txt.gz ** Affects: whitedune (Ubuntu) Importance: Undecided Status: New ** Affects: whitedune (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1067618 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067618 ** Also affects: whitedune (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067618 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061038 Title: FTBFS on armfh - implicit-function-declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whitedune/+bug/2061038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061033] [NEW] FTBFS on armfh - implicit-function-declaration
Public bug reported:
sn_generation.c:66:1: error: implicit declaration of function ‘input_field’
[-Werror=implicit-function-declaration]
66 | input_field(msg,NULL,0);
| ^~~
sn_generation.c:67:1: error: implicit declaration of function ‘forced_refresh’
[-Werror=implicit-function-declaration]
67 | forced_refresh();
| ^~
sn_generation.c: In function ‘sp_fix_IP_packet’:
sn_generation.c:205:22: error: implicit declaration of function ‘in_cksum’
[-Werror=implicit-function-declaration]
205 | sp_help_ip->checksum=in_cksum((unsigned short *) (sp->buffer),
| ^~~~
sn_interface.c: In function ‘mask_status’:
sn_interface.c:195:3: warning: assignment to ‘unsigned char *’ from
incompatible pointer type ‘_32_bit *’ {aka ‘unsigned int *’}
[-Wincompatible-pointer-types]
195 | ad=&(mask->source_ip);
| ^
sn_interface.c:201:3: warning: assignment to ‘unsigned char *’ from
incompatible pointer type ‘_32_bit *’ {aka ‘unsigned int *’}
[-Wincompatible-pointer-types]
201 | ad=&(mask->destination_ip);
| ^
sn_cfgfile.c: In function ‘clean_string’:
sn_cfgfile.c:131:14: error: implicit declaration of function ‘isalnum’
[-Werror=implicit-function-declaration]
131 | if( (isalnum(string[i]))||(string[i]=='.') )
| ^~~
sn_cfgfile.c:17:1: note: include ‘’ or provide a declaration of
‘isalnum’
16 | #include "sniffit.h"
+++ |+#include
17 | /* #include "sn_generation.h" */
sn_cfgfile.c: In function ‘clean_filename’:
sn_cfgfile.c:155:15: error: implicit declaration of function ‘iscntrl’
[-Werror=implicit-function-declaration]
155 | if( !(iscntrl(string[i])) && !(isspace(string[i])) )
| ^~~
sn_cfgfile.c:155:15: note: include ‘’ or provide a declaration of
‘iscntrl’
sn_cfgfile.c:155:40: error: implicit declaration of function ‘isspace’
[-Werror=implicit-function-declaration]
155 | if( !(iscntrl(string[i])) && !(isspace(string[i])) )
|^~~
sn_cfgfile.c:155:40: note: include ‘’ or provide a declaration of
‘isspace’
sn_interface.c: In function ‘interaction’:
sn_interface.c:470:25: error: implicit declaration of function ‘isprint’
[-Werror=implicit-function-declaration]
470 | isprint(*(connection_data+i))?
| ^~~
from https://launchpadlibrarian.net/724117947/buildlog_ubuntu-noble-
armhf.sniffit_0.5-3build2_BUILDING.txt.gz
** Affects: sniffit (Ubuntu)
Importance: Undecided
Status: New
** Affects: sniffit (Debian)
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #1066536
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066536
** Also affects: sniffit (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066536
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061033
Title:
FTBFS on armfh - implicit-function-declaration
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sniffit/+bug/2061033/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061030] Re: FTBFS on armfh - implicit-function-declaration
** Changed in: slrn (Ubuntu) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: slrn (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061030 Title: FTBFS on armfh - implicit-function-declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slrn/+bug/2061030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061030] Re: FTBFS on armfh - implicit-function-declaration
Upstream's fix for this: https://github.com/jedsoft/slrn/pull/1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061030 Title: FTBFS on armfh - implicit-function-declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slrn/+bug/2061030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061030] [NEW] FTBFS on armfh - implicit-function-declaration
Public bug reported: /<>/src/misc.c: In function ‘slrn_verror’: /<>/src/misc.c:376:4: error: implicit declaration of function ‘VA_COPY’ [-Werror=implicit-function-declaration] 376 |VA_COPY(ap1, ap); |^~~ from https://launchpadlibrarian.net/724118840/buildlog_ubuntu-noble- armhf.slrn_1.0.3+dfsg-6build2_BUILDING.txt.gz ** Affects: slrn (Ubuntu) Importance: Undecided Status: New ** Affects: slrn (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1066213 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066213 ** Also affects: slrn (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066213 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061030 Title: FTBFS on armfh - implicit-function-declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slrn/+bug/2061030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061028] [NEW] FTBFS on armfh - implicit-function-declaration
Public bug reported:
vncconnect.c:17:5: error: implicit declaration of function ‘exit’
[-Werror=implicit-function-declaration]
17 | exit(1);
| ^~~~
vncconnect.c:8:1: note: include ‘’ or provide a declaration of ‘exit’
7 | #include
+++ |+#include
8 |
vncconnect.c:17:5: warning: incompatible implicit declaration of built-in
function ‘exit’ [-Wbuiltin-declaration-mismatch]
17 | exit(1);
| ^~~~
vncconnect.c:17:5: note: include ‘’ or provide a declaration of ‘exit’
vncconnect.c: In function ‘main’:
vncconnect.c:51:9: warning: incompatible implicit declaration of built-in
function ‘exit’ [-Wbuiltin-declaration-mismatch]
51 | exit(1);
| ^~~~
vncconnect.c:51:9: note: include ‘’ or provide a declaration of ‘exit’
vncconnect.c:58:21: error: implicit declaration of function ‘strlen’
[-Werror=implicit-function-declaration]
58 | strlen(argv[i]));
| ^~
vncconnect.c:8:1: note: include ‘’ or provide a declaration of
‘strlen’
7 | #include
+++ |+#include
8 |
vncconnect.c:58:21: warning: incompatible implicit declaration of built-in
function ‘strlen’ [-Wbuiltin-declaration-mismatch]
58 | strlen(argv[i]));
| ^~
vncconnect.c:58:21: note: include ‘’ or provide a declaration of
‘strlen’
cc1: some warnings being treated as errors
[...]
vncauth.c:60:13: error: implicit declaration of function
‘vncEncryptAndStorePasswd2’; did you mean ‘vncEncryptAndStorePasswd’?
[-Werror=implicit-function-declaration]
60 | return (vncEncryptAndStorePasswd2(passwd, NULL, fname) == 0);
| ^
| vncEncryptAndStorePasswd
vncauth.c: In function ‘vncDecryptPasswdFromFile’:
vncauth.c:131:13: error: implicit declaration of function
‘vncDecryptPasswdFromFile2’; did you mean ‘vncDecryptPasswdFromFile’?
[-Werror=implicit-function-declaration]
131 | if (vncDecryptPasswdFromFile2(fname, passwd, NULL) == 0) {
| ^
| vncDecryptPasswdFromFile
vncauth.c: In function ‘vncRandomBytes’:
vncauth.c:211:28: error: implicit declaration of function ‘time’
[-Werror=implicit-function-declaration]
211 | seed = (unsigned int)time(0) ^ (unsigned int)getpid();
|^~~~
from https://launchpadlibrarian.net/724118029/buildlog_ubuntu-noble-
armhf.tightvnc_1%3A1.3.10-7build2_BUILDING.txt.gz
** Affects: tightvnc (Ubuntu)
Importance: Undecided
Status: New
** Affects: tightvnc (Debian)
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #1066337
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066337
** Also affects: tightvnc (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066337
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061028
Title:
FTBFS on armfh - implicit-function-declaration
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tightvnc/+bug/2061028/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061027] Re: FTBFS on armfh - implicit-function-declaration
For yyparse function, upstream patch is: https://sourceforge.net/p/tcpxtract/patches/6/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061027 Title: FTBFS on armfh - implicit-function-declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tcpxtract/+bug/2061027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061027] [NEW] FTBFS on armfh - implicit-function-declaration
Public bug reported:
confy.c: In function ‘yyparse’:
confy.c:494:16: error: implicit declaration of function ‘yylex’
[-Werror=implicit-function-declaration]
494 | # define YYLEX yylex ()
|^
confy.c:950:16: note: in expansion of macro ‘YYLEX’
950 | yychar = YYLEX;
|^
confy.c:1188:9: error: implicit declaration of function ‘yyerror’; did you mean
‘yyerrok’? [-Werror=implicit-function-declaration]
1188 | yyerror ("syntax error");
| ^~~
| yyerrok
confy.y: At top level:
confy.y:58:1: warning: return type defaults to ‘int’ [-Wimplicit-int]
58 | yyerror(char *s)
| ^~~
tcpxtract.c: In function ‘main’:
tcpxtract.c:312:5: error: implicit declaration of function ‘yyparse’
[-Werror=implicit-function-declaration]
312 | yyparse();
| ^~~
[...]
confl.l: In function ‘yylex’:
confl.l:28:47: error: implicit declaration of function ‘strdup’
[-Werror=implicit-function-declaration]
28 | [0-9]+ {yylval.string =
strdup(yytext); return NUMBER;}
| ^~
from https://launchpadlibrarian.net/724118034/buildlog_ubuntu-noble-
armhf.tcpxtract_1.0.1-17build2_BUILDING.txt.gz
** Affects: tcpxtract (Ubuntu)
Importance: Undecided
Status: New
** Affects: tcpxtract (Debian)
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #1066484
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066484
** Also affects: tcpxtract (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066484
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061027
Title:
FTBFS on armfh - implicit-function-declaration
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tcpxtract/+bug/2061027/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061024] [NEW] FTBFS on armfh - implicit-function-declaration
Public bug reported:
src/main.c:164:17: error: implicit declaration of function ‘LOG’
[-Werror=implicit-function-declaration]
164 | LOG( RAMOND_CRITICAL "! socket recvmsg error: '%s'\n",
| ^~~
src/main.c: In function ‘executeActions’:
src/main.c:570:17: warning: argument 2 null where non-null expected [-Wnonnull]
570 | setenv("PREFIX", NULL, 1);
| ^~
In file included from src/main.h:1,
from src/main.c:1:
/usr/include/stdlib.h:792:12: note: in a call to function ‘setenv’ declared
‘nonnull’
792 | extern int setenv (const char *__name, const char *__value, int
__replace)
|^~
src/main.c:571:17: warning: argument 2 null where non-null expected [-Wnonnull]
571 | setenv("PREFIX_LEN", NULL, 1);
| ^~
/usr/include/stdlib.h:792:12: note: in a call to function ‘setenv’ declared
‘nonnull’
792 | extern int setenv (const char *__name, const char *__value, int
__replace)
|^~
src/main.c: In function ‘daemonize’:
src/main.c:844:9: error: implicit declaration of function ‘umask’
[-Werror=implicit-function-declaration]
844 | umask(027);
| ^
src/main.c:874:12: error: implicit declaration of function ‘flock’; did you
mean ‘clock’? [-Werror=implicit-function-declaration]
874 | if(flock(pidfile, F_TLOCK, 0) < 0)
|^
|clock
cc1: some warnings being treated as errors
from https://launchpadlibrarian.net/724118903/buildlog_ubuntu-noble-
armhf.ramond_0.5-4.2build2_BUILDING.txt.gz
** Affects: ramond (Ubuntu)
Importance: Undecided
Status: New
** Affects: ramond (Debian)
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #1066551
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066551
** Also affects: ramond (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066551
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061024
Title:
FTBFS on armfh - implicit-function-declaration
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ramond/+bug/2061024/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040463] Re: MRE updates of dpdk in the 24.04 cycle
On Mantic, testing upgrading path, removing and installation : All OK. ## Upgrading #Installing previous version: root@Mdpdk:~# apt install dpdk Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: ibverbs-providers libfdt1 libibverbs1 libnl-route-3-200 librte-bus-auxiliary23 librte-bus-pci23 librte-bus-vdev23 librte-bus-vmbus23 librte-common-mlx5-23 librte-cryptodev23 librte-dmadev23 librte-eal23 librte-ethdev23 librte-gso23 librte-hash23 librte-ip-frag23 librte-kvargs23 librte-mbuf23 librte-mempool-ring23 librte-mempool23 librte-meter23 librte-net-af-packet23 librte-net-bond23 librte-net-e1000-23 librte-net-fm10k23 librte-net-i40e23 librte-net-ixgbe23 librte-net-mlx4-23 librte-net-mlx5-23 librte-net-netvsc23 librte-net-pcap23 librte-net-tap23 librte-net-thunderx23 librte-net-vdev-netvsc23 librte-net-vhost23 librte-net-virtio23 librte-net-vmxnet3-23 librte-net23 librte-pci23 librte-rcu23 librte-ring23 librte-sched23 librte-security23 librte-telemetry23 librte-vhost23 python3-pyelftools rdma-core Suggested packages: dpdk-doc dpdk-kmods-dkms librte-meta-baseband librte-meta-bus librte-meta-common librte-meta-compress librte-meta-crypto librte-meta-dma librte-meta-event librte-meta-mempool librte-meta-net librte-meta-raw librte-meta-allpmds The following NEW packages will be installed: dpdk ibverbs-providers libfdt1 libibverbs1 libnl-route-3-200 librte-bus-auxiliary23 librte-bus-pci23 librte-bus-vdev23 librte-bus-vmbus23 librte-common-mlx5-23 librte-cryptodev23 librte-dmadev23 librte-eal23 librte-ethdev23 librte-gso23 librte-hash23 librte-ip-frag23 librte-kvargs23 librte-mbuf23 librte-mempool-ring23 librte-mempool23 librte-meter23 librte-net-af-packet23 librte-net-bond23 librte-net-e1000-23 librte-net-fm10k23 librte-net-i40e23 librte-net-ixgbe23 librte-net-mlx4-23 librte-net-mlx5-23 librte-net-netvsc23 librte-net-pcap23 librte-net-tap23 librte-net-thunderx23 librte-net-vdev-netvsc23 librte-net-vhost23 librte-net-virtio23 librte-net-vmxnet3-23 librte-net23 librte-pci23 librte-rcu23 librte-ring23 librte-sched23 librte-security23 librte-telemetry23 librte-vhost23 python3-pyelftools rdma-core 0 upgraded, 48 newly installed, 0 to remove and 0 not upgraded. Need to get 3299 kB of archives. After this operation, 11.6 MB of additional disk space will be used. Do you want to continue? [Y/n] [...] Setting up dpdk (22.11.3-1) ... [...] #Upgrading root@Mdpdk:~# apt upgrade -t mantic-proposed dpdk Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: linux-headers-6.5.0-33 linux-headers-6.5.0-33-generic linux-image-6.5.0-33-generic linux-modules-6.5.0-33-generic The following packages will be upgraded: dpdk grub-common grub-efi-amd64-bin grub-efi-amd64-signed grub-pc grub-pc-bin grub2-common landscape-common librte-bus-auxiliary23 librte-bus-pci23 librte-bus-vdev23 librte-bus-vmbus23 librte-common-mlx5-23 librte-cryptodev23 librte-dmadev23 librte-eal23 librte-ethdev23 librte-gso23 librte-hash23 librte-ip-frag23 librte-kvargs23 librte-mbuf23 librte-mempool-ring23 librte-mempool23 librte-meter23 librte-net-af-packet23 librte-net-bond23 librte-net-e1000-23 librte-net-fm10k23 librte-net-i40e23 librte-net-ixgbe23 librte-net-mlx4-23 librte-net-mlx5-23 librte-net-netvsc23 librte-net-pcap23 librte-net-tap23 librte-net-thunderx23 librte-net-vdev-netvsc23 librte-net-vhost23 librte-net-virtio23 librte-net-vmxnet3-23 librte-net23 librte-pci23 librte-rcu23 librte-ring23 librte-sched23 librte-security23 librte-telemetry23 librte-vhost23 linux-headers-generic linux-headers-virtual linux-image-virtual linux-virtual openssh-client openssh-server openssh-sftp-server ubuntu-advantage-tools ubuntu-pro-client ubuntu-pro-client-l10n 59 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 80.7 MB of archives. After this operation, 166 MB of additional disk space will be used. Do you want to continue? [Y/n] [...] root@Mdpdk:~# dpkg -l dpdk | grep dpdk ii dpdk 22.11.4-0ubuntu0.23.10.1 amd64Data Plane Development Kit (runtime) #Removing after upgrade root@Mdpdk:~# apt remove --purge dpdk Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: ibverbs-providers libfdt1 libibverbs1 libnl-route-3-200 librte-bus-auxiliary23 librte-bus-pci23 librte-bus-vdev23 librte-bus-vmbus23 librte-common-mlx5-23 librte-cryptodev23 librte-dmadev23 librte-eal23 librte-ethdev23 librte-gso23 librte-hash23 librte-ip-frag23 librte-kvargs23 librte-mbuf23 librte-mempool-ring23 librte-mempool23 librte-meter23 librte-net-af-packet23 librte-net-bond23 librte-net-e1000-23
[Bug 2060959] Re: FTBFS on armfh - implicit-function-declaration - qsort
** Merge proposal linked: https://code.launchpad.net/~mirespace/ubuntu/+source/stellarsolver/+git/stellarsolver/+merge/464130 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060959 Title: FTBFS on armfh - implicit-function-declaration - qsort To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stellarsolver/+bug/2060959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060959] [NEW] FTBFS on armfh - implicit-function-declaration - qsort
Public bug reported:
/<>/stellarsolver/astrometry/os-features.h:123:17: error: implicit
declaration of function ‘qsort_r’; did you mean ‘qsort’?
[-Werror=implicit-function-declaration]
123 | #define QSORT_R qsort_r
| ^~~
/<>/stellarsolver/astrometry/util/bl-sort.c:68:9: note: in
expansion of macro ‘QSORT_R’
68 | QSORT_R(NODE_DATA(node), node->N, list->datasize, ,
qcompare);
| ^~~
https://launchpadlibrarian.net/724118070/buildlog_ubuntu-noble-armhf.stellarsolver_2.5-1build2_BUILDING.txt.gz
It seems to be fixed on upstream:
https://github.com/rlancaste/stellarsolver/pull/139
** Affects: stellarsolver (Ubuntu)
Importance: Undecided
Assignee: Miriam España Acebal (mirespace)
Status: In Progress
** Affects: stellarsolver (Debian)
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #1066275
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066275
** Also affects: stellarsolver (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066275
Importance: Unknown
Status: Unknown
** Changed in: stellarsolver (Ubuntu)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
** Changed in: stellarsolver (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060959
Title:
FTBFS on armfh - implicit-function-declaration - qsort
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stellarsolver/+bug/2060959/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2040463] Re: MRE updates of dpdk in the 24.04 cycle
Internal test for Mantic proposed passed OK. Result of doing sudo ./test.sh -P -r mantic -R mantic 2>&1 | tee output.log on Mantic: Status log and log of testing dpdk standalone and in- conjunction with Open vSwitch (internal tests) Finished, overall status: + cat dpdk-test.status PHYS_TESTPMD VIRT_SPAWNGUESTS VIRT_TESTPMD VIRT_L2FWD BENCH_OVS VUC_BENCH_OVSDPDK VUC_ENDURANCE_STARTSTOP VUC_ENDURANCE_ADDREMOVEPORT 1.0.0 (09:54:01): phys (BM) tests 1.1.0 (09:54:01): initialize environment 1.1.1 (09:56:56): testpmd => Pass 1.1.2 (09:58:20): check testpmd output => Pass 2.0.0 (09:58:20): prep virtual test environment 1.0.0 (10:26:15): virt tests 1.1.0 (10:26:15): initialize environment 3.0.0 (10:26:59): performance tests 3.1.0 (10:26:59): prep benchmarks 3.2.0 (10:27:58): performance tests 3.2.1 (10:28:08): test guest-openvswitch for OVS-5CPU => Pass 3.2.2 (10:47:52): test guest-dpdk-vhost-user-client-multiq for OVSDPDK-VUC => Pass 4.0.0 (11:08:21): VUC endurance checks 4.1.0 (11:08:21): prep VUC endurance tests 4.1.1 (11:22:32): start stop guests (client) => Pass 4.1.2 (12:24:19): add/remove ports (client) => Pass 4.2.0 (12:34:03): Final cleanup+ echo '' + exit 100 ** Attachment added: "output-Mantic-proposed.log" https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040463/+attachment/5763652/+files/output-Mantic-proposed.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040463 Title: MRE updates of dpdk in the 24.04 cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060784] Re: FTBFS on armfh - implicit-function-declaration
Patch forwarded to Debian. ** Bug watch added: Debian Bug tracker #1066243 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066243 ** Also affects: bristol (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066243 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060784 Title: FTBFS on armfh - implicit-function-declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bristol/+bug/2060784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060784] Re: FTBFS on armfh - implicit-function-declaration
** Merge proposal linked: https://code.launchpad.net/~mirespace/ubuntu/+source/bristol/+git/bristol/+merge/464004 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060784 Title: FTBFS on armfh - implicit-function-declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bristol/+bug/2060784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060784] Re: FTBFS on armfh - implicit-function-declaration
** Changed in: bristol (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060784 Title: FTBFS on armfh - implicit-function-declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bristol/+bug/2060784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060784] Re: FTBFS on armfh - implicit-function-declaration
I found an upstream's patch that deals with this and other implicit warnings like : audioEngine.c:85:1: warning: type of ‘fragSize’ defaults to ‘int’ [-Wimplicit-int] 85 | initAudioDevice2(audioDev, devID, fragSize) https://sourceforge.net/p/bristol/patches/3/ ** Changed in: bristol (Ubuntu) Assignee: (unassigned) => Miriam España Acebal (mirespace) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060784 Title: FTBFS on armfh - implicit-function-declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bristol/+bug/2060784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060784] [NEW] FTBFS on armfh - implicit-function-declaration
Public bug reported: bristolmemorymoog.c:280:25: error: implicit declaration of function ‘doPitchWheel’ [-Werror=implicit-function-declaration] 280 | doPitchWheel(baudio); | ^~~~ https://launchpadlibrarian.net/723978750/buildlog_ubuntu-noble-armhf.bristol_0.60.11-4build2_BUILDING.txt.gz ** Affects: bristol (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060784 Title: FTBFS on armfh - implicit-function-declaration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bristol/+bug/2060784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023971] Re: [MIR] libmail-dmarc-perl
Regarding the debate about libmime-tools-perl vs libemail-mime-perl, I checked that libemail-mime-perl is not being used in the last version of spamassassin directly: https://salsa.debian.org/debian/spamassassin/-/blob/master/debian/control?ref_type=heads -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023971 Title: [MIR] libmail-dmarc-perl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023971] Re: [MIR] libmail-dmarc-perl
After Miha did the security review, he found that dmarc_receive was
failing. It wasn't covered here as dmarc's binary scripts are not used
by spamassassin, but I thought it was worth checking.
The steps to reproduce (thanks Miha!) were:
1) Create dmarc xml based on google's example
2) Convert to gzipped base64
$ cat dmarc_example.xml | gzip | base64 > dmarc_example.xml.gz.base64
3) Copy base64 into example email (test_email.eml) from
https://datatracker.ietf.org/doc/html/rfc7489#appendix-B.5
4) Run dmarc_receive
$ dmarc_receive --file test_mail.eml &> out.txt
The bad output contains "Can't locate object method "getline" via
package "From: dmarc-reporting@mail.receiver.example ..."
I caught the bug and amended it:
diff -Nru
libmail-dmarc-perl-1.20230215/debian/patches/use-MIME-Entity-and-MIME-Parser-from-libmime-tools-p.patch
libmail-dmarc-perl-1.20230215/debian/patches/use-MIME-Entity-and-MIME-Parser-from-libmime-tools-p.patch
---
libmail-dmarc-perl-1.20230215/debian/patches/use-MIME-Entity-and-MIME-Parser-from-libmime-tools-p.patch
2023-12-11 14:43:31.0 +
+++
libmail-dmarc-perl-1.20230215/debian/patches/use-MIME-Entity-and-MIME-Parser-from-libmime-tools-p.patch
2023-12-11 14:43:31.0 +
@@ -125,7 +125,7 @@
-foreach my $part ( Email::MIME->new( $email->as_string )->parts ) {
-my ($c_type) = split /;/, $part->content_type || '';
+my $parser = MIME::Parser->new;
-+foreach my $part ( $parser->parse( $email->as_string )->parts_DFS ) {
++foreach my $part ( $parser->parse_data( $email->as_string )->parts_DFS ) {
+next if defined(!$part->bodyhandle); # something to process
+my ($c_type) = split /;/, $part->effective_type || '';
next if $c_type eq 'text/plain';
dmarc building tests are passing [1] and also autopkgtests that cover
the splitting:
autopkgtest [14:02:18]: test splitting-check: [---
autopkgtest [14:03:08]: test splitting-check: ---]
autopkgtest [14:03:09]: test splitting-check: - - - - - - - - - - results - -
- - - - - - - -
splitting-check PASS
autopkgtest [14:03:10]: summary
splitting-check PASS
Spamassassin test for dmarc also passes:
root@NDmarc-spamassassin-tests:~/spamassassin# make test TEST_FILES="t/dmarc.t"
"/usr/bin/perl" build/mkrules --exit_on_no_src --src rulesrc --out rules
--manifest MANIFEST --manifestskip MANIFEST.SKIP
mkrules: no rules updated
"/usr/bin/perl" build/preprocessor -Mvars -DVERSION="4.00"
-DPREFIX="/usr/local" -DDEF_RULES_DIR="/usr/local/share/spamassassin"
-DLOCAL_RULES_DIR="/etc/mail/spamassassin"
-DLOCAL_STATE_DIR="/var/lib/spamassassin"
-DINSTALLSITELIB="/usr/local/share/perl/5.38.2" -DCONTACT_ADDRESS="the
administrator of that system" -DRE2C_BIN="re2c" -Msharpbang -Mconditional
-DPERL_BIN=""/usr/bin/perl"" -DPERL_WARN="" -DPERL_TAINT="" -m755
-isa-update.raw -osa-update
cp sa-update blib/script/sa-update
"/usr/bin/perl" -MExtUtils::MY -e 'MY->fixin(shift)' -- blib/script/sa-update
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness"
"-e" "undef *Test::Harness::Switches; test_harness(0, 'blib/lib', 'blib/arch')"
t/dmarc.t
t/dmarc.t .. Apr 9 12:29:54.780 [9230] warn: deprecated method; size() is an
alias of "UDPsize()" at ../blib/lib/Mail/SpamAssassin/DnsResolver.pm line 602.
t/dmarc.t .. 1/18 Apr 9 12:29:59.035 [9232] warn: deprecated method; size() is
an alias of "UDPsize()" at ../blib/lib/Mail/SpamAssassin/DnsResolver.pm line
602.
t/dmarc.t .. 3/18 Apr 9 12:30:03.208 [9234] warn: deprecated method; size() is
an alias of "UDPsize()" at ../blib/lib/Mail/SpamAssassin/DnsResolver.pm line
602.
t/dmarc.t .. 5/18 Apr 9 12:30:06.210 [9236] warn: deprecated method; size() is
an alias of "UDPsize()" at ../blib/lib/Mail/SpamAssassin/DnsResolver.pm line
602.
t/dmarc.t .. 7/18 Apr 9 12:30:09.197 [9238] warn: deprecated method; size() is
an alias of "UDPsize()" at ../blib/lib/Mail/SpamAssassin/DnsResolver.pm line
602.
t/dmarc.t .. 9/18 Apr 9 12:30:12.643 [9240] warn: deprecated method; size() is
an alias of "UDPsize()" at ../blib/lib/Mail/SpamAssassin/DnsResolver.pm line
602.
t/dmarc.t .. 11/18 Apr 9 12:30:17.225 [9242] warn: deprecated method; size()
is an alias of "UDPsize()" at ../blib/lib/Mail/SpamAssassin/DnsResolver.pm line
602.
t/dmarc.t .. 13/18 Apr 9 12:30:21.491 [9244] warn: deprecated method; size()
is an alias of "UDPsize()" at ../blib/lib/Mail/SpamAssassin/DnsResolver.pm line
602.
t/dmarc.t .. 15/18 Apr 9 12:30:25.294 [9246] warn: deprecated method; size()
is an alias of "UDPsize()" at ../blib/lib/Mail/SpamAssassin/DnsResolver.pm line
602.
t/dmarc.t .. ok
All tests successful.
Files=1, Tests=18, 34 wallclock secs ( 0.02 usr 0.00 sys + 12.72 cusr 1.55
csys = 14.29 CPU)
Result: PASS
I upload the fixed package at
https://launchpad.net/~mirespace/+archive/ubuntu/libmail-dmarc-perl-
suggested/ as I've been doing (fixed
[Bug 2040463] Re: MRE updates of dpdk in the 24.04 cycle
* For Mantic arm64 [1], going deeper into this tests failures 6655s 157: conntrack - floating IP FAILED (ovs- macros.at:247) for kmod test. For s390x [2], kmod test suite is also failing, slightly different: 1317s 69: conntrack - zones from other field, more tests FAILED (system-traffic.at:3374) [1] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- mantic/mantic/arm64/o/openvswitch/20240322_201709_e53bb@/log.gz [2] https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- mantic/mantic/s390x/o/openvswitch/20240322_134250_a9b5b@/log.gz * For Jammy, it's blocked (BLOCKED: Needs an approval (either due to a freeze, the source suite or a manual hint)). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2040463 Title: MRE updates of dpdk in the 24.04 cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/2040463/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2023971] Re: [MIR] libmail-dmarc-perl
Hi Miha, First of all, thanks for your work on this Miha. You've summarized it very well and you're right that moving in a different direction than upstream always involves more delicate work in the future. Upstream's discussion is ongoing [1], and we don't know the decision they could make even if we (I) provide as fast as possible what they need to take it: - specific tests - data (that we have from this MIR study already) - Extending the patch: completely switching even from libemail-simple-perl for general email handling. - and as extra and beyond: making/checking it is compliant with latest RFC DMARC/DMARCbisfor, making our proposal more robust (although it is out-of-scope of the original PR) [1.1] since for the moment they don't find a compelling reason to change the dependency [1.2] because: - the security issue is solved [2] (as you rightly point out too) - they are perfectly within their rights that our main/universe distinctions are not a priority for them. Coming back to the Requires TODO for ACK in the MIR review of libemail- mime-perl [3], the #0 is that libemail-mime-perl passes the security review: Would that package be reviewed by security to see if we can go back to it? The security review (SEC-2671) was blocked and later rejected due to the switching to libmime-tools-perl. I have no objection to reverting back to libemail-mime-perl if: - The libemail-mime-perl security review (SEC-2671) passes with an ACK/OK. - TODO #2 (duplicity) can be overcome. Thank you in advance! [1] https://github.com/msimerson/mail-dmarc/pull/217 [1.1] https://github.com/msimerson/mail-dmarc/pull/217#issuecomment-2010843067 [1.2] https://github.com/msimerson/mail-dmarc/pull/217#issuecomment-2010862484 [2] https://github.com/msimerson/mail-dmarc/issues/216#issuecomment-1945033737 [3] https://bugs.launchpad.net/ubuntu/+source/libemail-mime-perl/+bug/2030880/comments/1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2023971 Title: [MIR] libmail-dmarc-perl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmail-dmarc-perl/+bug/2023971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2046154] Re: [MIR] libcryptx-perl (libmail-dkim-perl dependency)
** Merge proposal linked: https://code.launchpad.net/~mirespace/ubuntu/+source/libmail-dkim-perl/+git/libmail-dkim-perl/+merge/461344 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046154 Title: [MIR] libcryptx-perl (libmail-dkim-perl dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcryptx-perl/+bug/2046154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882272] Re: fancontrol does not work after sleep/wakeup
Verification done in Focal. All scenarios OK: ❯ cat /etc/fancontrol # Configuration file generated by pwmconfig, changes will be lost INTERVAL=10 DEVPATH=hwmon5=devices/platform/qc71_laptop hwmon6=devices/platform/qc71_laptop DEVNAME=hwmon5=qc71_laptop.hwmon.fan hwmon6=qc71_laptop.hwmon.pwm FCTEMPS=hwmon6/pwm2=hwmon5/temp2_input FCFANS= hwmon6/pwm2=hwmon5/fan2_input MINTEMP=hwmon6/pwm2=20 MAXTEMP=hwmon6/pwm2=60 MINSTART=hwmon6/pwm2=150 MINSTOP=hwmon6/pwm2=100 * Scenario 1: Service is enabled and active --> is restarted ❯ systemctl status -l fancontrol ● fancontrol.service - fan speed regulator Loaded: loaded (/lib/systemd/system/fancontrol.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2022-04-20 18:38:51 CEST; 1min 9s ago Docs: man:fancontrol(8) man:pwmconfig(8) Process: 60255 ExecStartPre=/usr/sbin/fancontrol --check (code=exited, status=0/SUCCESS) Main PID: 60352 (fancontrol) Tasks: 2 (limit: 76978) Memory: 1.3M CGroup: /system.slice/fancontrol.service ├─60352 /bin/bash /usr/sbin/fancontrol └─61653 sleep 10 abr 20 18:38:51 Camelot-TITAN fancontrol[60352]: Controls hwmon5/fan2_input abr 20 18:38:51 Camelot-TITAN fancontrol[60352]: MINTEMP=20 abr 20 18:38:51 Camelot-TITAN fancontrol[60352]: MAXTEMP=60 abr 20 18:38:51 Camelot-TITAN fancontrol[60352]: MINSTART=150 abr 20 18:38:51 Camelot-TITAN fancontrol[60352]: MINSTOP=100 abr 20 18:38:51 Camelot-TITAN fancontrol[60352]: MINPWM=0 abr 20 18:38:51 Camelot-TITAN fancontrol[60352]: MAXPWM=255 abr 20 18:38:51 Camelot-TITAN fancontrol[60352]: AVERAGE=1 abr 20 18:38:52 Camelot-TITAN fancontrol[60352]: Enabling PWM on fans... abr 20 18:38:52 Camelot-TITAN fancontrol[60352]: Starting automatic fan control... [Suspend] abr 20 18:42:44 Camelot-TITAN fancontrol[60352]: Aborting, restoring fans... abr 20 18:42:44 Camelot-TITAN systemd[1]: Stopping fan speed regulator... abr 20 18:42:44 Camelot-TITAN fancontrol[60352]: Verify fans have returned to full speed abr 20 18:42:44 Camelot-TITAN systemd[1]: fancontrol.service: Succeeded. abr 20 18:42:44 Camelot-TITAN systemd[1]: Stopped fan speed regulator. abr 20 18:42:44 Camelot-TITAN systemd[1]: Starting fan speed regulator... abr 20 18:42:44 Camelot-TITAN fancontrol[62467]: Loading configuration from /etc/fancontrol ... abr 20 18:42:44 Camelot-TITAN fancontrol[62467]: Common settings: abr 20 18:42:44 Camelot-TITAN fancontrol[62467]: INTERVAL=10 abr 20 18:42:44 Camelot-TITAN fancontrol[62467]: Settings for hwmon6/pwm2: abr 20 18:42:44 Camelot-TITAN fancontrol[62467]: Depends on hwmon5/temp2_input abr 20 18:42:44 Camelot-TITAN fancontrol[62467]: Controls hwmon5/fan2_input abr 20 18:42:44 Camelot-TITAN fancontrol[62467]: MINTEMP=20 abr 20 18:42:44 Camelot-TITAN fancontrol[62467]: MAXTEMP=60 abr 20 18:42:44 Camelot-TITAN fancontrol[62467]: MINSTART=150 abr 20 18:42:44 Camelot-TITAN fancontrol[62467]: MINSTOP=100 abr 20 18:42:44 Camelot-TITAN fancontrol[62467]: MINPWM=0 abr 20 18:42:44 Camelot-TITAN fancontrol[62467]: MAXPWM=255 abr 20 18:42:44 Camelot-TITAN fancontrol[62467]: AVERAGE=1 abr 20 18:42:44 Camelot-TITAN systemd[1]: Started fan speed regulator. * Scenario 2: Service is disabled and active --> is restarted ❯ sudo systemctl disable fancontrol Synchronizing state of fancontrol.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install disable fancontrol Removed /etc/systemd/system/multi-user.target.wants/fancontrol.service. [Suspend] ❯ systemctl --type=service | grep fancontrol fancontrol.serviceloaded active running fan speed regulator ❯ sudo systemctl status -l fancontrol ● fancontrol.service - fan speed regulator Loaded: loaded (/lib/systemd/system/fancontrol.service; disabled; vendor preset: enabled) Active: active (running) since Wed 2022-04-20 18:59:16 CEST; 17s ago Docs: man:fancontrol(8) man:pwmconfig(8) Process: 72652 ExecStartPre=/usr/sbin/fancontrol --check (code=exited, status=0/SUCCESS) Main PID: 72741 (fancontrol) Tasks: 2 (limit: 76978) Memory: 896.0K CGroup: /system.slice/fancontrol.service ├─72741 /bin/bash /usr/sbin/fancontrol └─73034 sleep 10 abr 20 18:59:16 Camelot-TITAN fancontrol[72741]: Controls hwmon5/fan2_input abr 20 18:59:16 Camelot-TITAN fancontrol[72741]: MINTEMP=20 abr 20 18:59:16 Camelot-TITAN fancontrol[72741]: MAXTEMP=60 abr 20 18:59:16 Camelot-TITAN fancontrol[72741]: MINSTART=150 abr 20 18:59:16 Camelot-TITAN fancontrol[72741]: MINSTOP=100 abr 20 18:59:16 Camelot-TITAN fancontrol[72741]: MINPWM=0 abr 20 18:59:16 Camelot-TITAN fancontrol[72741]: MAXPWM=255 abr 20 18:59:16 Camelot-TITAN fancontrol[72741]: AVERAGE=1 abr 20 18:59:16 Camelot-TITAN fancontrol[72741]: Enabling PWM on fans... abr 20 18:59:17 Camelot-TITAN fancontrol[72741]: Starting automatic fan control... * Scenario 3: Service is enabled and inactive --> is not restarted ❯ systemctl --type=service | grep fancontrol ❯
[Bug 1847377] Re: snmptrapd.service uses MIBSDIR instead of MIBDIRS
** Tags added: bitesize -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847377 Title: snmptrapd.service uses MIBSDIR instead of MIBDIRS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1847377/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961901] Re: 3.6.2-1 FTBFS in Jammy on s390x
** Changed in: wireshark (Ubuntu) Status: New => Fix Released ** Changed in: wireshark (Ubuntu) Assignee: Miriam España Acebal (mirespace) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961901 Title: 3.6.2-1 FTBFS in Jammy on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1961901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961901] Re: 3.6.2-1 FTBFS in Jammy on s390x
There is a typo in the debian/rules affecting s390x arch (thanks a lot to @mwhudson for the catch). @Doko already made the change and the build was successful [1]. [1] (https://launchpad.net/ubuntu/+source/wireshark/3.6.2-1ubuntu1/+build/23210749) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961901 Title: 3.6.2-1 FTBFS in Jammy on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1961901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961901] Re: 3.6.2-1 FTBFS in Jammy on x86/s390x
Thank you Christian for the sponsorship, the test environment and the
commands.
The first test that is failing looks for a string phrase
(test/suite_decryption.py @ line 271
self.assertTrue(self.grepOutput('Who has 192.168.1.1')) ). I put a line
of debug in the countOutput function (test/subprocesstest.py) to check
what was the output from the tshark command executed before... it shows
192.168.5.1 (among others, but always 192.168.5.*):
line is -- 38 12.586605105 02:00:00:00:00:00 → ff:ff:ff:ff:ff:ff ARP 110 Who
has 192.168.
5.5? Tell 192.168.5.1--
line is -- 25 10.547097155 02:00:00:00:00:00 → ff:ff:ff:ff:ff:ff ARP 110 Who
has 192.168.
5.5? Tell 192.168.5.1--
line is -- 32 11.562579505 02:00:00:00:00:00 → ff:ff:ff:ff:ff:ff ARP 110 Who
has 192.168.
5.5? Tell 192.168.5.1--
line is -- 38 12.586605105 02:00:00:00:00:00 → ff:ff:ff:ff:ff:ff ARP 110 Who
has 192.168.
5.5? Tell 192.168.5.1--
line is -- 21 15.399324999 02:00:00:00:00:00 → ff:ff:ff:ff:ff:ff ARP 110 Who
has 192.168.
5.5? Tell 192.168.5.1--
line is -- 32 16.402513535 02:00:00:00:00:00 → ff:ff:ff:ff:ff:ff ARP 110 Who
has 192.168.
5.5? Tell 192.168.5.1--
line is -- 50 17.426588527 02:00:00:00:00:00 → ff:ff:ff:ff:ff:ff ARP 110 Who
has 192.168.
5.5? Tell 192.168.5.1--
root@j-wireshark1:~/wireshark-3.6.2/obj-s390x-linux-gnu#
root@j-wireshark1:~/wireshark-3.6.2/obj-s390x-linux-gnu#
root@j-wireshark1:~/wireshark-3.6.2/obj-s390x-linux-gnu#
root@j-wireshark1:~/wireshark-3.6.2/obj-s390x-linux-gnu#
root@j-wireshark1:~/wireshark-3.6.2/obj-s390x-linux-gnu# grep Who miriam.log |
wc -l
72
root@j-wireshark1:~/wireshark-3.6.2/obj-s390x-linux-gnu# grep Who miriam.log |
grep 192.168.5 | wc -l
72
I checked that, in that entire test/suite_decryption.py file, all the
asserts checking for verification of the GTK are with addresses
192.168.5.* except this. I'm wondering if this is intentional or not in
the middle of my no-knowledge and inexpertise in tshark, although, on
the other hand, the test passes in arm64 (I didn't see it neither the
suite launched for other architectures)...
Any ideas from anyone on why the command
tshark -o "wlan.enable_decryption: TRUE" -r
wireshark-3.6.2/test/captures/wpa2-ft-eap.pcapng.gz -Y 'wlan.analysis.tk
== 65471b64605bf2a04af296284cb4ae2a || wlan.analysis.gtk ==
1783a5c28e046df6fb58cf4406c4b22c'
throws 192.168.5.* instead of 192.168.1.* are very welcome (or if you
have concerns/suspicious about why this particular case is looking for
the 192.168.1.1).
Thanks!
P.S. In the meantime, reviewing the
https://www.wireshark.org/docs/wsdg_html_chunked/ChapterTests.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961901
Title:
3.6.2-1 FTBFS in Jammy on x86/s390x
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1961901/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961901] Re: 3.6.2-1 FTBFS in Jammy on x86/s390x
** Changed in: lto-disabled-list (Ubuntu) Assignee: (unassigned) => Miriam España Acebal (mirespace) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961901 Title: 3.6.2-1 FTBFS in Jammy on x86/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1961901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961901] Re: 3.6.2-1 FTBFS in Jammy on x86/s390x
Hi!
I made several buildings in a ppa (arm64,s 390x and proposed pocket)
here [1], with three scenarios:
1) the optimization moutline-atomics (sorry for the misunderstanding) plus
disabling Bsymbolic-functions -> doesn't work
2) only disabling Bsymbolic-functions (in a bad attempt to restrict the
disabling of lto for arm64 and s390x... but, happy that this can confirm
scenario 3 :) ) -> doesn't work
3) disabling lto and Bsymbolic-functions -> it works.
Therefore, what works for arm64 building is disabling lto. I'll add the
package to the lto-disabled-list package for this (adding a related task
here).
Continue checking what is happening on the decryption testsuite. We can
see in the log the following:
FAIL: test_80211_wpa2_ft_eap (suite_decryption.case_decrypt_80211)
IEEE 802.11 decode WPA2 FT EAP
--
Traceback (most recent call last):
File "/<>/test/fixtures.py", line 54, in wrapped
test_fn(self, *fixtures)
File "/<>/test/suite_decryption.py", line 271, in
test_80211_wpa2_ft_eap
self.assertTrue(self.grepOutput('Who has 192.168.1.1'))# Verifies GTK
decryption
AssertionError: False is not true
==
FAIL: test_80211_wpa2_ft_psk_no_roam (suite_decryption.case_decrypt_80211)
IEEE 802.11 decode WPA2 FT PSK (without roam verification)
--
Traceback (most recent call last):
File "/<>/test/fixtures.py", line 54, in wrapped
test_fn(self, *fixtures)
File "/<>/test/suite_decryption.py", line 235, in
test_80211_wpa2_ft_psk_no_roam
self.assertEqual(self.countOutput('DHCP Discover'), 2)
AssertionError: 0 != 2
==
FAIL: test_80211_wpa2_ft_psk_roam (suite_decryption.case_decrypt_80211)
IEEE 802.11 decode WPA2 FT PSK
--
Traceback (most recent call last):
File "/<>/test/fixtures.py", line 54, in wrapped
test_fn(self, *fixtures)
File "/<>/test/suite_decryption.py", line 255, in
test_80211_wpa2_ft_psk_roam
self.assertEqual(self.countOutput('DHCP Discover'), 2)
AssertionError: 0 != 2
[1] https://launchpad.net/~mirespace/+archive/ubuntu/wireshark-
arm64-jammy/+builds?build_text=_state=all
** Also affects: lto-disabled-list (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961901
Title:
3.6.2-1 FTBFS in Jammy on x86/s390x
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1961901/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961901] Re: 3.6.2-1 FTBFS in Jammy on x86/s390x
For arm64, the execution of test 15 (/wmem/datastruct/tree) of 37 - suite_unittests ends in SIGSEGV. Adding the compilation flag "-moutline-atomics" didn't work... I'm still investigating. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961901 Title: 3.6.2-1 FTBFS in Jammy on x86/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/1961901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961901] Re: 3.6.2-1 FTBFS in Jammy on x86/s390x
** Changed in: wireshark (Ubuntu) Assignee: (unassigned) => Miriam España Acebal (mirespace) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961901 Title: 3.6.2-1 FTBFS in Jammy on x86/s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireshark/+bug/1961901/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576041] Re: Spams "Please run this cronjob as user amavis" from cron after upgrading 12.04 -> 14.04
Hi, I came across this error while performing upgrade work on this package in Ubuntu. Sorry for the long delay in responding and thank you for taking the time to file a bug report. The scenario described by you is confirmed and the bug was reported also to Debian here [1], but it seems to be a decision of the maintainer not to remove the script on etc/cron.daily/ , leaving this task to the user as can be seen in the file NEWS.DEBIAN in the source package: amavisd-new (1:2.7.0-2) unstable; urgency=low /etc/cron.daily/amavisd-new moved to /etc/cron.d/amavisd-new. If you don't need the file /etc/cron.daily/amavisd-new anymore, please remove it. -- Alexander Wirt Thu, 19 Apr 2012 08:51:18 +0200 This entry is missing in the binary package [2]. Therefore, please, follow the maintainer's recommendation to avoid unwanted messages. For this reason, I'll mark this as "Opinion" and "WishList". If you or anyone consider this to have a major impact, I suggest you continue the discussion on Debian, so if there is a change of mind on this and a fix is released there, we can pick that fix to avoid increasing our Ubuntu delta. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671450 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671450#79 ** Changed in: amavisd-new (Ubuntu) Status: Confirmed => Opinion ** Changed in: amavisd-new (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576041 Title: Spams "Please run this cronjob as user amavis" from cron after upgrading 12.04 -> 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1576041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576041] Re: Spams "Please run this cronjob as user amavis" from cron after upgrading 12.04 -> 14.04
** Bug watch added: Debian Bug tracker #671450 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671450 ** Also affects: amavisd-new (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671450 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576041 Title: Spams "Please run this cronjob as user amavis" from cron after upgrading 12.04 -> 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1576041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946841] Re: Merge amavisd-new from Debian unstable for 22.04
** Changed in: amavisd-new (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946841 Title: Merge amavisd-new from Debian unstable for 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amavisd-new/+bug/1946841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893202] Re: update-smart-drivedb overwrites package installed file
** Tags removed: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893202 Title: update-smart-drivedb overwrites package installed file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1893202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893202] Re: update-smart-drivedb overwrites package installed file
** Description changed: + [SRU] + [Impact] + + The "drivedb.h" file is the smartmontools drive database file used to + perform the scan actions. This file can be updated through update-smart- + drivedb command, but debsums may complain about drive.h in the form of a + false negative verification of the smartmontool packae being raised. In + addition, if the smartmontool package is upgraded, the "drivedb.h" file + is overwritten, therefore data will be lost. + + The worst scenario would be that a drive model is included in a + "drivedb.h" update at some point, and later the smartmontool package + update downgrades the drive.h version, making smartmontools scans + unavailable. It's true that it can be recovered through an update-smart- + drivedb action, but the user might not be aware of it. + + The fix applied here is picked up from upstream and it is present since + version 7.2-1, therefore Ubuntu series starting at Impish and later are + not affected. What this fix does is that it corrects the current + shipping system of "drivedb.h", as well as avoiding an unconditional + replacement of "drivedb.h". + + [Test Plan] + + This test plan is for Focal, but applies to Bionic in the same way. + + 0.Preparing the test environment: + + #Preparing the container + lxc launch images:ubuntu/focal focal + lxc shell focal + apt update -y + apt upgrade -y + + #Installing necessary tools + + apt install -y smartmontools gpg debsums wget + + 0.1 Preparing scenario: + + #At this point, debsums always gives all OK for the package: + + root@focal:~# debsums smartmontools + /lib/systemd/system/smartmontools.service OK + /usr/sbin/smartctl OK + /usr/sbin/smartd OK + /usr/sbin/update-smart-drivedb OK + /usr/share/bug/smartmontools/presubj OK + /usr/share/doc/smartmontools/AUTHORS OK + /usr/share/doc/smartmontools/ChangeLog-6.0-7.0.gz OK + /usr/share/doc/smartmontools/NEWS.Debian.gz OK + /usr/share/doc/smartmontools/NEWS.gz OK + /usr/share/doc/smartmontools/README OK + /usr/share/doc/smartmontools/README.Debian OK + /usr/share/doc/smartmontools/badblockhowto.html OK + /usr/share/doc/smartmontools/changelog.Debian.gz OK + /usr/share/doc/smartmontools/copyright OK + /usr/share/doc/smartmontools/examples/Example1 OK + /usr/share/doc/smartmontools/examples/Example2 OK + /usr/share/doc/smartmontools/examples/Example3 OK + /usr/share/doc/smartmontools/examples/Example4 OK + /usr/share/doc/smartmontools/examples/Example5 OK + /usr/share/doc/smartmontools/examples/Example6 OK + /usr/share/doc/smartmontools/examples/Example7 OK + /usr/share/doc/smartmontools/examples/Example8 OK + /usr/share/doc/smartmontools/examples/README OK + /usr/share/doc/smartmontools/smartd.conf.gz OK + /usr/share/lintian/overrides/smartmontools OK + /usr/share/man/man5/smartd.conf.5.gz OK + /usr/share/man/man8/smartctl.8.gz OK + /usr/share/man/man8/smartd.8.gz OK + /usr/share/man/man8/update-smart-drivedb.8.gz OK + /usr/share/smartmontools/smartd-runner OK + /usr/share/smartmontools/smartd_warning.sh OK + /var/lib/smartmontools/drivedb/drivedb.h OK + + #Perform an update of the drivedb.h: + + root@focal:~# update-smart-drivedb + /var/lib/smartmontools/drivedb/drivedb.h updated from branches/RELEASE_7_0_DRIVEDB + + 1. Bad cases: + + root@focal:~# debsums smartmontools | grep drivedb.h + /var/lib/smartmontools/drivedb/drivedb.h FAILED + + 2. Good cases: + + # special attention on the new location of the file + + root@focal:~# debsums smartmontools | grep drivedb.h + /usr/share/smartmontools/drivedb.h OK + + + [Where problems could occur] + + At the end, the file is still used from the /var/lib location, so the + logic of smartmontools for using the file remains the
[Bug 1893202] Re: update-smart-drivedb overwrites package installed file
** Changed in: smartmontools (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893202 Title: update-smart-drivedb overwrites package installed file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1893202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940916] Re: Incorrectly excludes tmpfs filesystems
** Tags removed: server-todo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940916 Title: Incorrectly excludes tmpfs filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1940916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893202] Re: update-smart-drivedb overwrites package installed file
** Changed in: smartmontools (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: smartmontools (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893202 Title: update-smart-drivedb overwrites package installed file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1893202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
Verification for Focal... OK:
-> Availability from proposed:
root@nagios:~# apt list --upgradable -a | grep rsync
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
rsync/focal-proposed 3.1.3-8ubuntu0.2 amd64 [upgradable from: 3.1.3-8ubuntu0.1]
rsync/focal-updates,now 3.1.3-8ubuntu0.1 amd64 [installed,upgradable to:
3.1.3-8ubuntu0.2]
rsync/focal 3.1.3-8 amd64
-> After installing, executing test for scenario 16:
root@nagios:~# rsync -avvvz --delete source_dir target_dir
.
.
.
send files finished
total: matches=0 hash_hits=0 false_alarms=0 data=9162752000
recv_files phase=2
recv_files finished
generate_files phase=3
generate_files finished
sent 9,750,166 bytes received 3,805,745 bytes 186,978.08 bytes/sec
total size is 9,162,752,000 speedup is 675.92
[sender] _exit_cleanup(code=0, file=main.c, line=1207): about to call exit(0)
root@nagios:~#
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
To manage notifications about this bug go to:
https://bugs.launchpad.net/rsync/+bug/1528921/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
Verification for Bionic... OK:
-> Availability from proposed:
root@bionic:/tmp# apt-cache policy rsync
rsync:
Installed: 3.1.2-2.1ubuntu1.3
Candidate: 3.1.2-2.1ubuntu1.3
Version table:
*** 3.1.2-2.1ubuntu1.3 500
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
3.1.2-2.1ubuntu1.2 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
3.1.2-2.1ubuntu1.1 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
3.1.2-2.1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
-> After installing, executing test for scenario 16:
root@bionic:/tmp#
.
.
.
send_files phase=2
send files finished
total: matches=0 hash_hits=0 false_alarms=0 data=9162752000
recv_files phase=2
recv_files finished
generate_files phase=3
generate_files finished
sent 9,750,855 bytes received 3,629,561 bytes 201,209.26 bytes/sec
total size is 9,162,752,000 speedup is 684.79
[sender] _exit_cleanup(code=0, file=main.c, line=1196): about to call exit(0)
root@bionic:/tmp#
** Tags removed: verification-done-focal verification-needed-bionic
** Tags added: verification-done-bionic verification-needed-focal
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
To manage notifications about this bug go to:
https://bugs.launchpad.net/rsync/+bug/1528921/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
Verification for Focal... OK:
-> Availability from proposed
root@focal:~# apt list --upgradable -a | grep rsync
WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.
rsync/focal-proposed 3.1.3-8ubuntu0.2 amd64 [upgradable from: 3.1.3-8ubuntu0.1]
rsync/focal-updates,now 3.1.3-8ubuntu0.1 amd64 [installed,upgradable to:
3.1.3-8ubuntu0.2]
rsync/focal 3.1.3-8 amd64
-> After installing, executing the test for scenario 16:
root@focal:~# rsync -avvvz --delete source_dir target_dir
.
.
send files finished
total: matches=0 hash_hits=0 false_alarms=0 data=9162752000
recv_files phase=2
recv_files finished
generate_files phase=3
generate_files finished
sent 9,750,166 bytes received 3,805,745 bytes 186,978.08 bytes/sec
total size is 9,162,752,000 speedup is 675.92
[sender] _exit_cleanup(code=0, file=main.c, line=1207): about to call exit(0)
root@nagios-focal:~#
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
To manage notifications about this bug go to:
https://bugs.launchpad.net/rsync/+bug/1528921/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
All tests passed already.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
To manage notifications about this bug go to:
https://bugs.launchpad.net/rsync/+bug/1528921/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893202] Re: update-smart-drivedb overwrites package installed file
Hi, [2] and [3] in comment #1 are part of the future release of smartmontools (beyond 7.2), so we'll take only the fix [1] from comment #1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893202 Title: update-smart-drivedb overwrites package installed file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1893202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940916] Re: Incorrectly excludes tmpfs filesystems
Installing... Setting up monitoring-plugins (2.3.1-1ubuntu2.1) ... Checking the #DISK UNKNOWN cases ... all OK: root@checkdisks-impish:~# /usr/lib/nagios/plugins/check_disk -w 10% -c 5% -p /reproduce-tmpfs DISK OK - free space: /reproduce-tmpfs 2048 MB (100% inode=99%);| /reproduce-tmpfs=0MB;1843;1945;0;2048 root@checkdisks-impish:~# /usr/lib/nagios/plugins/check_disk -w 10% -c 5% -N tmpfs DISK OK - free space: /dev 0 MB (99% inode=99%); /dev/lxd 0 MB (100% inode=99%); /dev/.lxd-mounts 0 MB (100% inode=99%); /proc/sys/kernel/random/boot_id 0 MB (99% inode=99%); /dev/shm 32106 MB (100% inode=99%); /run 12842 MB (99% inode=99%); /run/lock 5 MB (100% inode=99%); /sys/fs/cgroup 4 MB (100% inode=98%); /run/user/0 6421 MB (100% inode=99%); /reproduce-tmpfs 2048 MB (100% inode=99%); /reproduce-squashfs 2048 MB (100% inode=99%); /reproduce-tracefs 2048 MB (100% inode=99%); /run/snapd/ns 12842 MB (99% inode=99%);| /dev=0MB;0;0;0;0 /dev/lxd=0MB;0;0;0;0 /dev/.lxd-mounts=0MB;0;0;0;0 /proc/sys/kernel/random/boot_id=0MB;0;0;0;0 /dev/shm=0MB;28895;30500;0;32106 /run=0MB;11557;12199;0;12842 /run/lock=0MB;4;4;0;5 /sys/fs/cgroup=0MB;3;3;0;4 /run/user/0=0MB;5778;6099;0;6421 /reproduce-tmpfs=0MB;1843;1945;0;2048 /reproduce-squashfs=0MB;1843;1945;0;2048 /reproduce-tracefs=0MB;1843;1945;0;2048 /run/snapd/ns=0MB;11557;12199;0;12842 root@checkdisks-impish:~# /usr/lib/nagios/plugins/check_disk -w 10% -c 5% -N tmpfs -p /reproduce-tmpfs DISK OK - free space: /reproduce-tmpfs 2048 MB (100% inode=99%);| /reproduce-tmpfs=0MB;1843;1945;0;2048 root@checkdisks-impish:~# /usr/lib/nagios/plugins/check_disk -w 10% -c 5% -X tmpfs -p /reproduce-tmpfs DISK UNKNOWN - free space:| root@checkdisks-impish:~# /usr/lib/nagios/plugins/check_disk -w 10% -c 5% -X squashfs -p /reproduce-tmpfs DISK OK - free space: /reproduce-tmpfs 2048 MB (100% inode=99%);| /reproduce-tmpfs=0MB;1843;1945;0;2048 root@checkdisks-impish:~# /usr/lib/nagios/plugins/check_disk -w 10% -c 5% -X squashfs -N tmpfs DISK OK - free space: /dev 0 MB (99% inode=99%); /dev/lxd 0 MB (100% inode=99%); /dev/.lxd-mounts 0 MB (100% inode=99%); /proc/sys/kernel/random/boot_id 0 MB (99% inode=99%); /dev/shm 32106 MB (100% inode=99%); /run 12842 MB (99% inode=99%); /run/lock 5 MB (100% inode=99%); /sys/fs/cgroup 4 MB (100% inode=98%); /run/user/0 6421 MB (100% inode=99%); /reproduce-tmpfs 2048 MB (100% inode=99%); /reproduce-squashfs 2048 MB (100% inode=99%); /reproduce-tracefs 2048 MB (100% inode=99%); /run/snapd/ns 12842 MB (99% inode=99%);| /dev=0MB;0;0;0;0 /dev/lxd=0MB;0;0;0;0 /dev/.lxd-mounts=0MB;0;0;0;0 /proc/sys/kernel/random/boot_id=0MB;0;0;0;0 /dev/shm=0MB;28895;30500;0;32106 /run=0MB;11557;12199;0;12842 /run/lock=0MB;4;4;0;5 /sys/fs/cgroup=0MB;3;3;0;4 /run/user/0=0MB;5778;6099;0;6421 /reproduce-tmpfs=0MB;1843;1945;0;2048 /reproduce-squashfs=0MB;1843;1945;0;2048 /reproduce-tracefs=0MB;1843;1945;0;2048 /run/snapd/ns=0MB;11557;12199;0;12842 #DISK CRITICAL cases ... OK too root@checkdisks-impish:~# /usr/lib/nagios/plugins/check_disk -w 10 -c 10 DISK OK - free space: / 7718 MB (91% inode=99%); /dev/fuse 32070 MB (100% inode=99%); /dev/net/tun 32070 MB (100% inode=99%); /dev/full 32070 MB (100% inode=99%); /dev/null 32070 MB (100% inode=99%); /dev/random 32070 MB (100% inode=99%); /dev/tty 32070 MB (100% inode=99%); /dev/urandom 32070 MB (100% inode=99%); /dev/zero 32070 MB (100% inode=99%);| /=748MB;8457;8457;0;8467 /dev/fuse=0MB;32060;32060;0;32070 /dev/net/tun=0MB;32060;32060;0;32070 /dev/full=0MB;32060;32060;0;32070 /dev/null=0MB;32060;32060;0;32070 /dev/random=0MB;32060;32060;0;32070 /dev/tty=0MB;32060;32060;0;32070 /dev/urandom=0MB;32060;32060;0;32070 /dev/zero=0MB;32060;32060;0;32070 root@checkdisks-impish:~# And after install snap for gnome-calculator: root@checkdisks-impish:~# df -h FilesystemSize Used Avail Use% Mounted on default/containers/checkdisks-impish 8.3G 797M 7.5G 10% / none 492K 4.0K 488K 1% /dev tmpfs 100K 0 100K 0% /dev/lxd tmpfs 100K 0 100K 0% /dev/.lxd-mounts tmpfs 32G 0 32G 0% /dev/shm tmpfs 13G 168K 13G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup tmpfs 6.3G 0 6.3G 0% /run/user/0 tmpfs 2.0G 0 2.0G 0% /reproduce-tmpfs squashfs 2.0G 0 2.0G 0% /reproduce-squashfs tracefs 2.0G 0 2.0G 0% /reproduce-tracefs snapfuse 44M 44M 0 100% /snap/snapd/14549 snapfuse 62M 62M 0 100% /snap/core20/1328 snapfuse 128K 128K 0 100% /snap/bare/5
[Bug 1893202] Re: update-smart-drivedb overwrites package installed file
** Changed in: smartmontools (Ubuntu Bionic) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: smartmontools (Ubuntu Focal) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: smartmontools (Ubuntu) Assignee: (unassigned) => Miriam España Acebal (mirespace) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893202 Title: update-smart-drivedb overwrites package installed file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1893202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
** Description changed:
[Impact]
What the user suffering from this bug experiences is that the big amount
of informative messages related to the copy process with the three
spawned processes(sender, receiver and generator) exhaust the I/O
buffer and the sync gets stuck, either because there are too many files
to synchronise and/or because too many detail messages (levels of
verbose mode) have been requested in the output.
The fix, that comes from upstream and is applied there since version
3.2.0., increments the size of the receiver's I/O buffer.
-
[Test Plan]
This test plan is for Focal, but it's the same for Bionic.
0.Preparing the test environment:
#Preparing the container
lxc launch images:ubuntu/focal rsync-iobuffer-focal
lxc shell rsync-iobuffer-focal
apt update -y
apt upgrade -y
#Installing necessary tools
- apt install rsync
+ apt install rsync
apt install wget
- #Get test cases from comments #16 and #19 on this LP bug
+ #Get test cases from comments #16 and #19 on this LP bug: As test case
+ #16 covers both aspects (a lot of files and upper verbosity) and test
+ #19 uses a huge tarball (120 Mb), I'm removing from this SRU the
+ bad/good case for the #19 (but, please feel to check it if you consider
+ it necessary).
cd /tmp/
- #19
- wget
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+attachment/5211950/+files/html2.tgz
- tar -xvzf /tmp/html2.tgz
- mkdir /tmp/rsynctest
-
- #16
+ #16
Paste the contents of https://pastebin.com/raw/ctzJJGwt:
#!/bin/bash
mkdir source_dir
pushd source_dir
dd if=/dev/zero of=source bs=600K count=1
for i in `seq 1 11500`;
do
- cp -v source file_$i;
+ cp -v source file_$i;
done
rm source
for i in `seq 1 10`;
do
- dd if=/dev/zero of=file_large_$i bs=200M count=1
+ dd if=/dev/zero of=file_large_$i bs=200M count=1
done
popd
echo "Created 11500 files with size 600K and 10 files with size 200M, try the
following command:"
echo "rsync -avvvz --delete source_dir target_dir"
in a new file script_comment16.sh
-
- chmod +x script_comment16.sh
+
+ chmod +x script_comment16.sh
./script_comment16.sh
+ #19 (Skip this if you can't download the tarball - Examples of good/bad were
removed).
+ wget
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+attachment/5211950/+files/html2.tgz
+ tar -xvzf /tmp/html2.tgz
+ mkdir /tmp/rsynctest
+
1. Bad cases (without and with using strace):
-
- # Scenario from comment 19
- $ rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
- (Client) Protocol versions: remote=31, negotiated=31
- sending incremental file list
- [sender] change_dir(/tmp)
- send_files starting
- server_recv(2) starting pid=49029
- get_local_name count=7070 /tmp/rsynctest/
- created directory /tmp/rsynctest
- [Receiver] change_dir(/tmp/rsynctest)
- generator starting pid=49029
- delta-transmission disabled for local transfer or --whole-file
- recv_generator(html2,1)
- recv_generator(html2,2)
- set uid of html2 from 0 to 1000
- set gid of html2 from 0 to 1000
- set modtime of html2 to (1447205118) Wed Nov 11 01:25:18 2015
- [...]
- sender finished /tmp/html2/annotator__raw_8h__incl.md5
- send_files(282, /tmp/html2/annotator__raw_8h__incl.png)
- html2/annotator__raw_8h__incl.png
-
- It hangs here, where using strace we can see:
-
- $ strace rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
- [...]
- read(3,
"\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\v\4\0\0\2\233\10\6\0\0\0\361\177\254"...,
262144) = 262144
- select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 2 (in [5], out [4], left
{tv_sec=59, tv_usec=98})
- read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 95)
= 95
- write(4,
"K\374\0\7\177\377\207\343\335\345+{W\335{K\371y\211w`Ysl\336B{\312\340}\320\301"...,
64591) = 64591
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 1 (out [4], left {tv_sec=59,
tv_usec=98})
- write(4,
"\336\322\0\7\177\377\255\371\367\215v\321-\224\323+\363\261\243\7\211Do\230\256\257O\372\367:\357O"...,
53986) = 53986
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
- select(5, [], [4], [], {tv_sec=60, tv_usec=0}
-
# Scenario from comment 16
$ rsync -avvvz --delete source_dir target_dir
sending incremental file list
[sender] make_file(source_dir,*,0)
send_file_list done
[sender] pushing local filters for /root/source_dir/
[sender] make_file(source_dir/file_3048,*,2)
[sender] make_file(source_dir/file_11358,*,2)
[sender] make_file(source_dir/file_5914,*,2)
[sender]
[Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
** Description changed:
- In the last few months my home directory backup stopped completing.
- I've been able to reproduce the problem on a single subdirectory
- although I had to add the --debug=all flag to reproduce it on that
- smaller directory. Specifically, this command never completes:
+ [Impact]
+
+ What the user suffering from this bug experiences is that the big amount
+ of informative messages related to the copy process with the three
+ spawned processes(sender, receiver and generator) exhaust the I/O
+ buffer and the sync gets stuck, either because there are too many files
+ to synchronise and/or because too many detail messages (levels of
+ verbose mode) have been requested in the output.
+
+ The fix, that comes from upstream and is applied there since version
+ 3.2.0., increments the size of the receiver's I/O buffer.
+
+
+ [Test Plan]
+ This test plan is for Focal, but it's the same for Bionic.
+
+ 0.Preparing the test environment:
+
+ #Preparing the container
+ lxc launch images:ubuntu/focal rsync-iobuffer-focal
+ lxc shell rsync-iobuffer-focal
+ apt update -y
+ apt upgrade -y
+
+ #Installing necessary tools
+ apt install rsync
+ apt install wget
+
+ #Get test cases from comments #16 and #19 on this LP bug
+
+ cd /tmp/
+
+ #19
+ wget
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+attachment/5211950/+files/html2.tgz
+ tar -xvzf /tmp/html2.tgz
+ mkdir /tmp/rsynctest
+
+ #16
+ Paste the contents of https://pastebin.com/raw/ctzJJGwt:
+
+ #!/bin/bash
+ mkdir source_dir
+ pushd source_dir
+ dd if=/dev/zero of=source bs=600K count=1
+
+ for i in `seq 1 11500`;
+ do
+ cp -v source file_$i;
+ done
+
+ rm source
+
+ for i in `seq 1 10`;
+ do
+ dd if=/dev/zero of=file_large_$i bs=200M count=1
+ done
+
+ popd
+
+ echo "Created 11500 files with size 600K and 10 files with size 200M, try the
following command:"
+ echo "rsync -avvvz --delete source_dir target_dir"
+
+ in a new file script_comment16.sh
+
+ chmod +x script_comment16.sh
+ ./script_comment16.sh
+
+
+ 1. Bad cases (without and with using strace):
+
+ # Scenario from comment 19
+ $ rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
+ (Client) Protocol versions: remote=31, negotiated=31
+ sending incremental file list
+ [sender] change_dir(/tmp)
+ send_files starting
+ server_recv(2) starting pid=49029
+ get_local_name count=7070 /tmp/rsynctest/
+ created directory /tmp/rsynctest
+ [Receiver] change_dir(/tmp/rsynctest)
+ generator starting pid=49029
+ delta-transmission disabled for local transfer or --whole-file
+ recv_generator(html2,1)
+ recv_generator(html2,2)
+ set uid of html2 from 0 to 1000
+ set gid of html2 from 0 to 1000
+ set modtime of html2 to (1447205118) Wed Nov 11 01:25:18 2015
+ [...]
+ sender finished /tmp/html2/annotator__raw_8h__incl.md5
+ send_files(282, /tmp/html2/annotator__raw_8h__incl.png)
+ html2/annotator__raw_8h__incl.png
+
+ It hangs here, where using strace we can see:
+
+ $ strace rsync --debug=all -avz /tmp/html2 /tmp/rsynctest/
+ [...]
+ read(3,
"\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\v\4\0\0\2\233\10\6\0\0\0\361\177\254"...,
262144) = 262144
+ select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 2 (in [5], out [4], left
{tv_sec=59, tv_usec=98})
+ read(5,
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 95)
= 95
+ write(4,
"K\374\0\7\177\377\207\343\335\345+{W\335{K\371y\211w`Ysl\336B{\312\340}\320\301"...,
64591) = 64591
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 1 (out [4], left {tv_sec=59,
tv_usec=98})
+ write(4,
"\336\322\0\7\177\377\255\371\367\215v\321-\224\323+\363\261\243\7\211Do\230\256\257O\372\367:\357O"...,
53986) = 53986
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
+ select(5, [], [4], [], {tv_sec=60, tv_usec=0}
+
+
+ # Scenario from comment 16
+ $ rsync -avvvz --delete source_dir target_dir
+ sending incremental file list
+ [sender] make_file(source_dir,*,0)
+ send_file_list done
+ [sender] pushing local filters for /root/source_dir/
+ [sender] make_file(source_dir/file_3048,*,2)
+ [sender] make_file(source_dir/file_11358,*,2)
+ [sender] make_file(source_dir/file_5914,*,2)
+ [sender] make_file(source_dir/file_5880,*,2)
+ [sender] make_file(source_dir/file_9318,*,2)
+ [sender] make_file(source_dir/file_5539,*,2)
+ [...]
+ sending file_sum
+ false_alarms=0 hash_hits=0 matches=0
+ sender finished source_dir/file_10807
+ send_files(903, source_dir/file_10808)
+ send_files mapped source_dir/file_10808 of size 614400
+ calling match_sums source_dir/file_10808
+ source_dir/file_10808
+
+ It hangs here, where
[Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
Thanks @r0lf! Thanks @Christian! I will take care of this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
To manage notifications about this bug go to:
https://bugs.launchpad.net/rsync/+bug/1528921/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
** Changed in: rsync (Ubuntu Bionic)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
** Changed in: rsync (Ubuntu Focal)
Assignee: (unassigned) => Miriam España Acebal (mirespace)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
To manage notifications about this bug go to:
https://bugs.launchpad.net/rsync/+bug/1528921/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
Hi,
I checked this bug is still present in Bionic and Focal (versions here
are 3.1.?) but neither in Jammy nor in Impish (versions here are >
3.2.?). I used as steps to reproduce instructions in comments #16 and
#19.
As per comment 7 in upstream's bug 11166 [1], it seems this is fixed in
3.2.0 version, and in the changelog of that version we can see "Avoid a
hang when an overabundance of messages clogs up all the I/O buffers."
[2] and the fix seems to be here [3].
[1] https://bugzilla.samba.org/show_bug.cgi?id=11166#c7
[2] https://download.samba.org/pub/rsync/NEWS#3.2.0
[3]
https://github.com/WayneD/rsync/commit/01b9bbb0f94e4ddd4b1e3ad678b220ca09bc0ad0
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}
** Also affects: rsync (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: rsync (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1528921
Title:
rsync hangs on select(5, [], [4], [], {60, 0}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1528921/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940916] Re: Incorrectly excludes tmpfs filesystems
Hi Brian, sorry, changes for Jammy are now under review in its corresponding MP. I also submitted the change for Impish as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940916 Title: Incorrectly excludes tmpfs filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1940916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940916] Re: Incorrectly excludes tmpfs filesystems
** Also affects: monitoring-plugins (Ubuntu Jammy) Importance: Medium Assignee: Miriam España Acebal (mirespace) Status: In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940916 Title: Incorrectly excludes tmpfs filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1940916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940916] Re: Incorrectly excludes tmpfs filesystems
** Also affects: monitoring-plugins (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: monitoring-plugins (Ubuntu Impish) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: monitoring-plugins (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: monitoring-plugins (Ubuntu Impish) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940916 Title: Incorrectly excludes tmpfs filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1940916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940916] Re: Incorrectly excludes tmpfs filesystems
** Changed in: monitoring-plugins (Ubuntu Focal) Assignee: (unassigned) => Miriam España Acebal (mirespace) ** Changed in: monitoring-plugins (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: monitoring-plugins (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940916 Title: Incorrectly excludes tmpfs filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1940916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940916] Re: Incorrectly excludes tmpfs filesystems
** Description changed: [SRU] [Impact] False positive reports are generated in monitoring tools when artificial file systems are mounted, as they show 100% disk utilisation, and therefore add an unnecessary (but fatal sounding) "CRITICAL DISK" noise. But, if we exclude them by default as we did in the first place in bug 1827159, we limit the use of command options that are commonly used in scripts and that, because of this exclusion, cannot operate on this kind of filesystems (e.g. the path option or the include filesystem option -as excluding has preference over including). [Test Plan] 0.Preparing the test environment: #Preparing the container lxc launch images:ubuntu/focal checkdisks-focal lxc shell checkdisks-focal apt update -y apt upgrade -y #Installing necessary tools apt install monitoring-plugins apt install snapd #Mount some synthetic systems and make use of snap space mkdir /reproduce-tmpfs mkdir /reproduce-squashfs mkdir /reproduce-tracefs mount -t tmpfs -o rw,size=2G tmpfs /reproduce-tmpfs mount -t tmpfs -o rw,size=2G squashfs /reproduce-squashfs mount -t tmpfs -o rw,size=2G tracefs /reproduce-tracefs snap install gnome-calculator 1. Bad cases: # "CRITICAL DISK" noise $ /usr/lib/nagios/plugins/check_disk -w 10 -c 10 DISK CRITICAL - free space: /dev 448 MB (100% inode=99%); /run 96 MB (98% inode=99%); / 884 MB (18% inode=80%); /dev/shm 485 MB (100% inode=99%); /run/lock 5 MB (100% inode=99%); /snap/lxd/21835 0 MB (0% inode=0%); /snap/core20/1270 0 MB (0% inode=0%); /snap/snapd/14295 0 MB (0% inode=0%); /boot/efi 99 MB (95% inode=-); /run/snapd/ns 96 MB (98% inode=99%); /snap/snapd/14549 0 MB (0% inode=0%); /run/user/1000 97 MB (99% inode=99%); /snap/bare/5 0 MB (0% inode=0%); /snap/multipass-sshfs/145 0 MB (0% inode=0%); /home/ubuntu/monitoring-plugins 1024000 MB (100% inode=100%); /home/ubuntu/reproduce 2048 MB (100% inode=99%); /home/ubuntu/reproduce-squash 2048 MB (100% inode=99%); /snap/core20/1328 0 MB (0% inode=0%); /home/ubuntu/reproduce-tracefs 2048 MB (100% inode=99%);| /dev=0MB;438;438;0;448 /run=0MB;87;87;0;97 /=3886MB;4777;4777;0;4787 /dev/shm=0MB;475;475;0;485 /run/lock=0MB;-5;-5;0;5 /snap/lxd/21835=67MB;57;57;0;67 /snap/core20/1270=62MB;52;52;0;62 /snap/snapd/14295=43MB;33;33;0;43 /boot/efi=5MB;94;94;0;104 /run/snapd/ns=0MB;87;87;0;97 /snap/snapd/14549=43MB;33;33;0;43 /run/user/1000=0MB;87;87;0;97 /snap/bare/5=0MB;-10;-10;0;0 /snap/multipass-sshfs/145=1MB;-9;-9;0;1 /home/ubuntu/monitoring-plugins=0MB;1023990;1023990;0;1024000 /home/ubuntu/reproduce=0MB;2038;2038;0;2048 /home/ubuntu/reproduce-squash=0MB;2038;2038;0;2048 /snap/core20/1328=62MB;52;52;0;62 /home/ubuntu/reproduce-tracefs=0MB;2038;2038;0;2048 $ /usr/lib/nagios/plugins/check_disk -w 10 -c 10 -e -X squashfs DISK CRITICAL - free space: /run/lock 5 MB (100% inode=99%);| /dev=0MB;438;438;0;448 /run=0MB;87;87;0;97 /=3886MB;4777;4777;0;4787 /dev/shm=0MB;475;475;0;485 /run/lock=0MB;-5;-5;0;5 /boot/efi=5MB;94;94;0;104 /run/snapd/ns=0MB;87;87;0;97 /run/user/1000=0MB;87;87;0;97 /home/ubuntu/monitoring-plugins=0MB;1023990;1023990;0;1024000 /home/ubuntu/reproduce=0MB;2038;2038;0;2048 /home/ubuntu/reproduce-squash=0MB;2038;2038;0;2048 /home/ubuntu/reproduce-tracefs=0MB;2038;2038;0;2048 $ /usr/lib/nagios/plugins/check_disk -w 10 -c 10 -e -X tracefs DISK CRITICAL - free space: /run/lock 5 MB (100% inode=99%); /snap/lxd/21835 0 MB (0% inode=0%); /snap/core20/1270 0 MB (0% inode=0%); /snap/snapd/14295 0 MB (0% inode=0%); /snap/snapd/14549 0 MB (0% inode=0%); /snap/bare/5 0 MB (0% inode=0%); /snap/multipass-sshfs/145 0 MB (0% inode=0%); /snap/core20/1328 0 MB (0% inode=0%);| /dev=0MB;438;438;0;448 /run=0MB;87;87;0;97 /=3886MB;4777;4777;0;4787 /dev/shm=0MB;475;475;0;485 /run/lock=0MB;-5;-5;0;5 /snap/lxd/21835=67MB;57;57;0;67 /snap/core20/1270=62MB;52;52;0;62 /snap/snapd/14295=43MB;33;33;0;43 /boot/efi=5MB;94;94;0;104 /run/snapd/ns=0MB;87;87;0;97 /snap/snapd/14549=43MB;33;33;0;43 /run/user/1000=0MB;87;87;0;97 /snap/bare/5=0MB;-10;-10;0;0 /snap/multipass-sshfs/145=1MB;-9;-9;0;1 /home/ubuntu/monitoring-plugins=0MB;1023990;1023990;0;1024000 /home/ubuntu/reproduce=0MB;2038;2038;0;2048 /home/ubuntu/reproduce-squash=0MB;2038;2038;0;2048 /snap/core20/1328=62MB;52;52;0;62 /home/ubuntu/reproduce-tracefs=0MB;2038;2038;0;2048 $ /usr/lib/nagios/plugins/check_disk -w 10 -c 10 -e -X tracefs -X squashfs DISK CRITICAL - free space: /run/lock 5 MB (100% inode=99%);| /dev=0MB;438;438;0;448 /run=0MB;87;87;0;97 /=3886MB;4777;4777;0;4787 /dev/shm=0MB;475;475;0;485 /run/lock=0MB;-5;-5;0;5 /boot/efi=5MB;94;94;0;104 /run/snapd/ns=0MB;87;87;0;97 /run/user/1000=0MB;87;87;0;97 /home/ubuntu/monitoring-plugins=0MB;1023990;1023990;0;1024000 /home/ubuntu/reproduce=0MB;2038;2038;0;2048 /home/ubuntu/reproduce-squash=0MB;2038;2038;0;2048 /home/ubuntu/reproduce-tracefs=0MB;2038;2038;0;2048 $
[Bug 1940916] Re: Incorrectly excludes tmpfs filesystems
** Description changed: + [Impact] + + False positive reports are generated in monitoring tools when artificial + file systems are mounted, as they show 100% disk utilisation, and + therefore add an unnecessary (but fatal sounding) "CRITICAL DISK" noise. + But, if we exclude them by default as we did in the first place in bug + 1827159, we limit the use of command options that are commonly used in + scripts and that, because of this exclusion, cannot operate on this kind + of filesystems (e.g. the path option or the include filesystem option + -as excluding has preference over including). + + [Test Plan] + + 0.Preparing the test environment: + + #Preparing the container + lxc launch images:ubuntu/focal checkdisks-focal + lxc shell checkdisks-focal + apt update -y + apt upgrade -y + + #Installing necessary tools + apt install monitoring-plugins + apt install snapd + + #Mount some synthetic systems and make use of snap space + mkdir /reproduce-tmpfs + mkdir /reproduce-squashfs + mkdir /reproduce-tracefs + mount -t tmpfs -o rw,size=2G tmpfs /reproduce-tmpfs + mount -t tmpfs -o rw,size=2G squashfs /reproduce-squashfs + mount -t tmpfs -o rw,size=2G tracefs /reproduce-tracefs + snap install gnome-calculator + + 1. Bad cases: + + # "CRITICAL DISK" noise + + $ /usr/lib/nagios/plugins/check_disk -w 10 -c 10 + DISK CRITICAL - free space: /dev 448 MB (100% inode=99%); /run 96 MB (98% inode=99%); / 884 MB (18% inode=80%); /dev/shm 485 MB (100% inode=99%); /run/lock 5 MB (100% inode=99%); /snap/lxd/21835 0 MB (0% inode=0%); /snap/core20/1270 0 MB (0% inode=0%); /snap/snapd/14295 0 MB (0% inode=0%); /boot/efi 99 MB (95% inode=-); /run/snapd/ns 96 MB (98% inode=99%); /snap/snapd/14549 0 MB (0% inode=0%); /run/user/1000 97 MB (99% inode=99%); /snap/bare/5 0 MB (0% inode=0%); /snap/multipass-sshfs/145 0 MB (0% inode=0%); /home/ubuntu/monitoring-plugins 1024000 MB (100% inode=100%); /home/ubuntu/reproduce 2048 MB (100% inode=99%); /home/ubuntu/reproduce-squash 2048 MB (100% inode=99%); /snap/core20/1328 0 MB (0% inode=0%); /home/ubuntu/reproduce-tracefs 2048 MB (100% inode=99%);| /dev=0MB;438;438;0;448 /run=0MB;87;87;0;97 /=3886MB;4777;4777;0;4787 /dev/shm=0MB;475;475;0;485 /run/lock=0MB;-5;-5;0;5 /snap/lxd/21835=67MB;57;57;0;67 /snap/core20/1270=62MB;52;52;0;62 /snap/snapd/14295=43MB;33;33;0;43 /boot/efi=5MB;94;94;0;104 /run/snapd/ns=0MB;87;87;0;97 /snap/snapd/14549=43MB;33;33;0;43 /run/user/1000=0MB;87;87;0;97 /snap/bare/5=0MB;-10;-10;0;0 /snap/multipass-sshfs/145=1MB;-9;-9;0;1 /home/ubuntu/monitoring-plugins=0MB;1023990;1023990;0;1024000 /home/ubuntu/reproduce=0MB;2038;2038;0;2048 /home/ubuntu/reproduce-squash=0MB;2038;2038;0;2048 /snap/core20/1328=62MB;52;52;0;62 /home/ubuntu/reproduce-tracefs=0MB;2038;2038;0;2048 + + $ /usr/lib/nagios/plugins/check_disk -w 10 -c 10 -e -X squashfs + DISK CRITICAL - free space: /run/lock 5 MB (100% inode=99%);| /dev=0MB;438;438;0;448 /run=0MB;87;87;0;97 /=3886MB;4777;4777;0;4787 /dev/shm=0MB;475;475;0;485 /run/lock=0MB;-5;-5;0;5 /boot/efi=5MB;94;94;0;104 /run/snapd/ns=0MB;87;87;0;97 /run/user/1000=0MB;87;87;0;97 /home/ubuntu/monitoring-plugins=0MB;1023990;1023990;0;1024000 /home/ubuntu/reproduce=0MB;2038;2038;0;2048 /home/ubuntu/reproduce-squash=0MB;2038;2038;0;2048 /home/ubuntu/reproduce-tracefs=0MB;2038;2038;0;2048 + + $ /usr/lib/nagios/plugins/check_disk -w 10 -c 10 -e -X tracefs + DISK CRITICAL - free space: /run/lock 5 MB (100% inode=99%); /snap/lxd/21835 0 MB (0% inode=0%); /snap/core20/1270 0 MB (0% inode=0%); /snap/snapd/14295 0 MB (0% inode=0%); /snap/snapd/14549 0 MB (0% inode=0%); /snap/bare/5 0 MB (0% inode=0%); /snap/multipass-sshfs/145 0 MB (0% inode=0%); /snap/core20/1328 0 MB (0% inode=0%);| /dev=0MB;438;438;0;448 /run=0MB;87;87;0;97 /=3886MB;4777;4777;0;4787 /dev/shm=0MB;475;475;0;485 /run/lock=0MB;-5;-5;0;5 /snap/lxd/21835=67MB;57;57;0;67 /snap/core20/1270=62MB;52;52;0;62 /snap/snapd/14295=43MB;33;33;0;43 /boot/efi=5MB;94;94;0;104 /run/snapd/ns=0MB;87;87;0;97 /snap/snapd/14549=43MB;33;33;0;43 /run/user/1000=0MB;87;87;0;97 /snap/bare/5=0MB;-10;-10;0;0 /snap/multipass-sshfs/145=1MB;-9;-9;0;1 /home/ubuntu/monitoring-plugins=0MB;1023990;1023990;0;1024000 /home/ubuntu/reproduce=0MB;2038;2038;0;2048 /home/ubuntu/reproduce-squash=0MB;2038;2038;0;2048 /snap/core20/1328=62MB;52;52;0;62 /home/ubuntu/reproduce-tracefs=0MB;2038;2038;0;2048 + + $ /usr/lib/nagios/plugins/check_disk -w 10 -c 10 -e -X tracefs -X squashfs + DISK CRITICAL - free space: /run/lock 5 MB (100% inode=99%);| /dev=0MB;438;438;0;448 /run=0MB;87;87;0;97 /=3886MB;4777;4777;0;4787 /dev/shm=0MB;475;475;0;485 /run/lock=0MB;-5;-5;0;5 /boot/efi=5MB;94;94;0;104 /run/snapd/ns=0MB;87;87;0;97 /run/user/1000=0MB;87;87;0;97 /home/ubuntu/monitoring-plugins=0MB;1023990;1023990;0;1024000 /home/ubuntu/reproduce=0MB;2038;2038;0;2048 /home/ubuntu/reproduce-squash=0MB;2038;2038;0;2048 /home/ubuntu/reproduce-tracefs=0MB;2038;2038;0;2048 + + $
[Bug 1940916] Re: Incorrectly excludes tmpfs filesystems
Combining 1) and 2) from #7 the results are ok for both bugs (I'm preparing already the MP): root@nagios-focal-miriam:~# /usr/lib/nagios/plugins/check_disk -w 10 -c 10 DISK OK - free space: / 6971 MB (85% inode=99%); /dev/fuse 32071 MB (100% inode=99%); /dev/net/tun 32071 MB (100% inode=99%); /dev/full 32071 MB (100% inode=99%); /dev/null 32071 MB (100% inode=99%); /dev/random 32071 MB (100% inode=99%); /dev/tty 32071 MB (100% inode=99%); /dev/urandom 32071 MB (100% inode=99%); /dev/zero 32071 MB (100% inode=99%); /snap 6971 MB (85% inode=99%);| /=1204MB;8165;8165;0;8175 /dev/fuse=0MB;32061;32061;0;32071 /dev/net/tun=0MB;32061;32061;0;32071 /dev/full=0MB;32061;32061;0;32071 /dev/null=0MB;32061;32061;0;32071 /dev/random=0MB;32061;32061;0;32071 /dev/tty=0MB;32061;32061;0;32071 /dev/urandom=0MB;32061;32061;0;32071 /dev/zero=0MB;32061;32061;0;32071 /snap=1204MB;8165;8165;0;8175 root@nagios-focal-miriam:~# /usr/lib/nagios/plugins/check_disk -w 10% -c 5% -p /reproduce-tmpfs DISK OK - free space: /reproduce-tmpfs 2048 MB (100% inode=99%);| /reproduce-tmpfs=0MB;1843;1945;0;2048 root@nagios-focal-miriam:~# /usr/lib/nagios/plugins/check_disk -w 10% -c 5% -N tmpfs DISK OK - free space: /dev 0 MB (99% inode=99%); /dev/lxd 0 MB (100% inode=99%); /dev/.lxd-mounts 0 MB (100% inode=99%); /proc/sys/kernel/random/boot_id 0 MB (99% inode=99%); /dev/shm 32106 MB (100% inode=99%); /run 6421 MB (99% inode=99%); /run/lock 5 MB (100% inode=99%); /sys/fs/cgroup 32106 MB (100% inode=99%); /run/user/0 6421 MB (100% inode=99%); /run/snapd/ns 6421 MB (99% inode=99%); /reproduce-tmpfs 2048 MB (100% inode=99%); /reproduce-squashfs 2048 MB (100% inode=99%); /reproduce-tracefs 2048 MB (100% inode=99%);| /dev=0MB;0;0;0;0 /dev/lxd=0MB;0;0;0;0 /dev/.lxd-mounts=0MB;0;0;0;0 /proc/sys/kernel/random/boot_id=0MB;0;0;0;0 /dev/shm=0MB;28895;30500;0;32106 /run=0MB;5778;6099;0;6421 /run/lock=0MB;4;4;0;5 /sys/fs/cgroup=0MB;28895;30500;0;32106 /run/user/0=0MB;5778;6099;0;6421 /run/snapd/ns=0MB;5778;6099;0;6421 /reproduce-tmpfs=0MB;1843;1945;0;2048 /reproduce-squashfs=0MB;1843;1945;0;2048 /reproduce-tracefs=0MB;1843;1945;0;2048 root@nagios-focal-miriam:~# /usr/lib/nagios/plugins/check_disk -w 10% -c 5% -N tmpfs -p /reproduce-tmpfs DISK OK - free space: /reproduce-tmpfs 2048 MB (100% inode=99%);| /reproduce-tmpfs=0MB;1843;1945;0;2048 root@nagios-focal-miriam:~# /usr/lib/nagios/plugins/check_disk -w 10% -c 5% -X tmpfs -p /reproduce-tmpfs DISK UNKNOWN - free space:| root@nagios-focal-miriam:~# /usr/lib/nagios/plugins/check_disk -w 10% -c 5% -X squashfs -p /reproduce-tmpfs DISK OK - free space: /reproduce-tmpfs 2048 MB (100% inode=99%);| /reproduce-tmpfs=0MB;1843;1945;0;2048 root@nagios-focal-miriam:~# /usr/lib/nagios/plugins/check_disk -w 10% -c 5% -X squashfs -N tmpfs DISK OK - free space: /dev 0 MB (99% inode=99%); /dev/lxd 0 MB (100% inode=99%); /dev/.lxd-mounts 0 MB (100% inode=99%); /proc/sys/kernel/random/boot_id 0 MB (99% inode=99%); /dev/shm 32106 MB (100% inode=99%); /run 6421 MB (99% inode=99%); /run/lock 5 MB (100% inode=99%); /sys/fs/cgroup 32106 MB (100% inode=99%); /run/user/0 6421 MB (100% inode=99%); /run/snapd/ns 6421 MB (99% inode=99%); /reproduce- tmpfs 2048 MB (100% inode=99%); /reproduce-squashfs 2048 MB (100% inode=99%); /reproduce-tracefs 2048 MB (100% inode=99%);| /dev=0MB;0;0;0;0 /dev/lxd=0MB;0;0;0;0 /dev/.lxd-mounts=0MB;0;0;0;0 /proc/sys/kernel/random/boot_id=0MB;0;0;0;0 /dev/shm=0MB;28895;30500;0;32106 /run=0MB;5778;6099;0;6421 /run/lock=0MB;4;4;0;5 /sys/fs/cgroup=0MB;28895;30500;0;32106 /run/user/0=0MB;5778;6099;0;6421 /run/snapd/ns=0MB;5778;6099;0;6421 /reproduce-tmpfs=0MB;1843;1945;0;2048 /reproduce- squashfs=0MB;1843;1945;0;2048 /reproduce-tracefs=0MB;1843;1945;0;2048 root@nagios-focal-miriam:~# df -h Filesystem Size Used Avail Use% Mounted on default/containers/nagios-focal-miriam 8.0G 1.2G 6.9G 15% / none492K 4.0K 488K 1% /dev udev 32G 0 32G 0% /dev/tty tmpfs 100K 0 100K 0% /dev/lxd tmpfs 100K 0 100K 0% /dev/.lxd-mounts tmpfs32G 0 32G 0% /dev/shm tmpfs 6.3G 224K 6.3G 1% /run tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs32G 0 32G 0% /sys/fs/cgroup tmpfs 6.3G 0 6.3G 0% /run/user/0 tmpfs 2.0G 0 2.0G 0% /reproduce-tmpfs squashfs2.0G 0 2.0G 0% /reproduce-squashfs tracefs 2.0G 0 2.0G 0% /reproduce-tracefs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940916 Title: Incorrectly
[Bug 1958481] Re: check_disk forcibly ignores tmpfs
*** This bug is a duplicate of bug 1940916 *** https://bugs.launchpad.net/bugs/1940916 Hi Utkarsh, sure, I'll do :). Thanks, Richard also for the approach, which is like 1) in comment #7 [1]... so it looks like it's going in a good direction. [1]https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1940916/comments/7 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958481 Title: check_disk forcibly ignores tmpfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1958481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940916] Re: Incorrectly excludes tmpfs filesystems
Hi Utkarsh, sure :). Thanks Richard also for the approach, which is like 1) in comment #7... so it looks like it's going in a good direction -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940916 Title: Incorrectly excludes tmpfs filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1940916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951779] Re: tempfile command removed from debianutils
In the case of boost1.74, attending to the doc for Quickbook here [1], it seems that can be a rebuild of Quickbook (and maybe use of the warning-check script), because in the build log for boost1.74 [2] the following can be seen: echo "using boostbook ;" > user-config-doc.jam echo "using quickbook ;" >> user-config-doc.jam and the building with b2/bjam : cd tools/quickbook && /<>/b2 -j4 -q -d2 --layout=system --ignore-site-config --user-config=/<>/user-config.jam debug-symbols=on Performing configuration checks but the script is not used here, not deployed later with the package (checking if it can be used in quickbook's rebuilding): ubuntu@tempfile-20-2-22:~$ apt-file search boost1.74 | grep quickbook libboost1.74-doc: /usr/share/doc/libboost1.74-doc/doc/html/quickbook.html libboost1.74-doc: /usr/share/doc/libboost1.74-doc/doc/html/quickbook/change_log.html libboost1.74-doc: /usr/share/doc/libboost1.74-doc/doc/html/quickbook/command_line.html libboost1.74-doc: /usr/share/doc/libboost1.74-doc/doc/html/quickbook/editors.html libboost1.74-doc: /usr/share/doc/libboost1.74-doc/doc/html/quickbook/faq.html libboost1.74-doc: /usr/share/doc/libboost1.74-doc/doc/html/quickbook/install.html libboost1.74-doc: /usr/share/doc/libboost1.74-doc/doc/html/quickbook/ref.html libboost1.74-doc: /usr/share/doc/libboost1.74-doc/doc/html/quickbook/syntax.html libboost1.74-doc: /usr/share/doc/libboost1.74-doc/doc/html/quickbook/syntax/block.html libboost1.74-doc: /usr/share/doc/libboost1.74-doc/doc/html/quickbook/syntax/phrase.html libboost1.74-doc: /usr/share/doc/libboost1.74-doc/doc/html/quickbook/syntax/structure.html libboost1.74-doc: /usr/share/doc/libboost1.74-doc/doc/html/quickbook/versions.html libboost1.74-doc: /usr/share/doc/libboost1.74-doc/examples/tools/quickbook/examples/simple-boostbook/Jamfile.v2 libboost1.74-doc: /usr/share/doc/libboost1.74-doc/examples/tools/quickbook/examples/simple-boostbook/simple.xml libboost1.74-doc: /usr/share/doc/libboost1.74-doc/examples/tools/quickbook/examples/simple-quickbook/Jamfile.v2 libboost1.74-doc: /usr/share/doc/libboost1.74-doc/examples/tools/quickbook/examples/simple-quickbook/simple.qbk libboost1.74-doc: /usr/share/doc/libboost1.74-doc/examples/tools/quickbook/examples/standalone-quickbook/Jamfile.v2 libboost1.74-doc: /usr/share/doc/libboost1.74-doc/examples/tools/quickbook/examples/standalone-quickbook/Jamroot.jam libboost1.74-doc: /usr/share/doc/libboost1.74-doc/examples/tools/quickbook/examples/standalone-quickbook/simple.qbk [1] https://www.boost.org/doc/libs/1_74_0/doc/html/quickbook/install.html#quickbook.install.linux [2] https://launchpadlibrarian.net/580760449/buildlog_ubuntu-jammy-amd64.boost1.74_1.74.0-14ubuntu1_BUILDING.txt.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951779 Title: tempfile command removed from debianutils To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boost1.74/+bug/1951779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
