Re: [Qt-creator] Incompatibility between clang-tidy and gcc
Thank you, that helps. Regards, Jochen Am Mittwoch, dem 29.05.2024 um 13:12 +0200 schrieb Christian Kandeler via Qt-creator: > Hi, > > On 5/29/24 8:27 AM, Jochen Becher via Qt-creator wrote: > > I build my projects with qbs and gcc. For some legacy reasons, it > > uses > > "-fnothrow-opt". Unfortunately, this option is not known by clang- > > tidy > > and for a few versions clang-tidy does not ignore this option any > > longer but exits with an error. > > > > I don't see any chance to fix this in qbs as the qbs product is not > > resolved separately for clang-tidy but it uses the gcc build. Is > > there > > any way to filter the compiler options before they are forwarded to > > clang-tidy? > > we filter these options on a case by case basis, so we can add this > one > as well. In the meantime you can use the environment variable > "QTC_CLANG_CMD_OPTIONS_BLACKLIST" (semicolon-separated list) to > filter > out arbitrary compiler options for the clang tools. > > > Christian > -- Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Re: [Qbs] qbspkgconfig in qbs 2.3.1
Thank you, that does it. It would be great if this will be added to the
qbs manual.
Regards, Jochen
Am Sonntag, dem 02.06.2024 um 19:04 +0300 schrieb Иван Комиссаров:
> Hello!
>
> Short answer:
>
> Use qbsModuleProviders: ["Qt", "qbspkgconfig"]
>
> A longer answer:
>
> Setting qbsModuleProviders property disables «named» lookup for
> providers when Qbs tries to guess provider name from the module name
> (e.g. «Qt» from «Qt.core») .
>
> The "named" lookup exists for backward compatibility and we advise
> listing providers explicitly in the new node.
>
> Ivan
>
> > 1 июня 2024 г., в 13:21, Jochen Becher via Qbs
> > написал(а):
> >
> > Hi,
> >
> > I tried to build a project for the first time after a couple of
> > years
> > and qbs versions. I now use QtCreator 13.0.1 with qbs 2.3.1.
> >
> > The product is a StaticLibrary and has dependencies
> >
> > Depends { name: "Qt", submodules: ["core" , "gui"] }
> > Depends { name: "taglib" }
> >
> > In the past "taglib" has been resolved by the default fallback for
> > pkgconfig.
> >
> > I added
> >
> > qbsModuleProviders: "qbspkgconfig"
> >
> > in the hope to get the correct settings for taglib. But now, qbs
> > fails
> > with the following error message:
> >
> > mediadb-extras.qbs:13: warning: Dependency 'Qt.core' not found for
> > product 'mediadb-extras'.
> >
> > What I am doing wrong? I couldn't find an example showing
> > dependencies
> > to Qt and a pkgconfig provided library.
> >
> > I am running on Ubuntu 22.04 using Qt 5.15.2.
> >
> > Regards, Jochen
> >
> > ___
> > Qbs mailing list
> > Qbs@qt-project.org
> > https://lists.qt-project.org/listinfo/qbs
>
___
Qbs mailing list
Qbs@qt-project.org
https://lists.qt-project.org/listinfo/qbs
Re: [FRIAM] Unpleasant dreams
I do not find Paul's book completely convincing. Randolph M. Nesse's book "Good Reasons for Bad Feelings: Insights from the Frontier of Evolutionary Psychiatry" shows much more clearly that bad feelings prevent us from doing things which are bad for us. They are threat avoidance programs from our genes. His remark about dreams are interesting nevertheless. He mentions for instance this paper from Antti Revonsuo, "The reinterpretation of dreams: An evolutionary hypothesis of the function of dreaming" in Behavioral and Brain Sciences, 23(6) (2000). 877–901; 904–1018; 1083–1121.http://behavioralhealth2000.com/wp-content/uploads/2017/04/The-reinterpretation-of-dreams-An-evolutionary-hypothesis-of-the-function-of-dreaming.pdfRevonsuo argues one function of dreams may be to simulate threatening events. They may help to improve threat prevention by predicting dangerous situations and preparing us for unkown dangers. Some fears seem to be hardcoded but this method has limits. For example we are much more afraid of spiders and snakes than of cars and fast food which are more dangerous to us in the modern worldhttps://nautil.us/how-evolution-designed-your-fear-236858/-J. Original message From: glen Date: 6/3/24 11:04 PM (GMT+01:00) To: friam@redfish.com Subject: Re: [FRIAM] Unpleasant dreams I had a conversation with a psychiatrist friend of mine wherein she assumed the dichotomy between "good feelings" and "bad feelings" (e.g. an angry or relieved reaction to some thing like the Trump verdict). Through about an hour of conversation, I'd tried to convince her that dichotomy is false. Bad things are good and good things are bad. The valence we assign is post-hoc. I failed, of course. But...I feel the same way about phobias. It's a bit trite to suggest that we like exploring our fears in a safe environment like at a movie theater with a friend or two. But it's testament to the milieu that monsters vs treasures is a false dichotomy. And it goes beyond some complementarity like banking present pain for future pleasure. It's truly a dual. The highs *are* the lows and vice versa. If there is such a thing as free will, your assignment of valence might be the only freedom you have.I don't know if Bloom explores this aspect. But the body of work spawned from Friston and the minimization of surprisal targets it directly. It's reasonable to believe that *agency* is what provides the common substructure for an explanatory model of the ascription of valence to an experience. The hypothetical to explore is whether those experiences that promote agency are more often ascribed as (or felt like) "good" ones, whether painful, pleasurable, fearful, triumphant, or whatever the token ascribed.On 6/3/24 13:15, Jochen Fromm wrote:> Did you notice that some of the most successful movies from Spielberg are about our deepest fears? Jurassic Park is about monsters from the past. Jaws is about monsters which lurk in the deep blue sea. Indiana Jones is about monsters (and treasures) hiding in dark tombs.> > > Paul Boom remarks in his book "The Sweet Spot" that psychologists have long known that unpleasant dreams are more frequent than pleasant ones. Why is that so? Do unpleasant dreams prepare us for possible dangers or are we just relieved that the are over if they end?> > https://www.harpercollins.com/products/the-sweet-spot-paul-bloom?variant=40262533840930-- ꙮ Mɥǝu ǝlǝdɥɐuʇs ɟᴉƃɥʇ' ʇɥǝ ƃɹɐss snɟɟǝɹs˙ ꙮ-. --- - / ...- .- .-.. .. -.. / -- --- .-. ... . / -.-. --- -.. .FRIAM Applied Complexity Group listservFridays 9a-12p Friday St. Johns Cafe / Thursdays 9a-12p Zoom https://bit.ly/virtualfriamto (un)subscribe http://redfish.com/mailman/listinfo/friam_redfish.comFRIAM-COMIC http://friam-comic.blogspot.com/archives: 5/2017 thru present https://redfish.com/pipermail/friam_redfish.com/ 1/2003 thru 6/2021 http://friam.383.s1.nabble.com/-. --- - / ...- .- .-.. .. -.. / -- --- .-. ... . / -.-. --- -.. . FRIAM Applied Complexity Group listserv Fridays 9a-12p Friday St. Johns Cafe / Thursdays 9a-12p Zoom https://bit.ly/virtualfriam to (un)subscribe http://redfish.com/mailman/listinfo/friam_redfish.com FRIAM-COMIC http://friam-comic.blogspot.com/ archives: 5/2017 thru present https://redfish.com/pipermail/friam_redfish.com/ 1/2003 thru 6/2021 http://friam.383.s1.nabble.com/
Bug#1072389: patches to make cruft-ng work without locate
* Alexandre Detiste [2024-06-03 22:01]: Le lun. 3 juin 2024 à 21:32, Jochen Sprickerhof a écrit : >The scripts in explain/ ought to be run inside the chroot. Good point. You could actually use unshare to make it work without root but I would also prefer option 2. What do you think of a slow adoption as in explain.cc set's the DPKG_ROOT variable and all explain scripts get a test -z $DPKG_ROOT || exit 0 at the top. Then we can fix them individually as far as it makes sense. Let's do that, that's the simplest. OK, I actually opted for CRUFT_ROOT to stay out of the DPKG namespace. MR is here: https://salsa.debian.org/detiste-guest/cruft-ng/-/merge_requests/1 Can you have a look before I modify more scripts? I gave you write access. Thanks, I pushed a small fixup commit. This could be team-managed but I don't know inside which team it would fit. Maybe QA ? Maybe here: https://packages.debian.org/unstable/forensics-all Maybe just move it to https://salsa.debian.org/debian I use it nowadays to guess what messy people did before me on some filesystems, they were merely lazy, not evil, they did not tried to hide their tweaks at all; I don't know if that count as forensics. Yeah, same here. Btw. what do you think of dropping explain/python3-pip? I think cruft-ng should rather report all non package files and it is easy enough for the user to filter out /usr/local if they want. signature.asc Description: PGP signature
[FRIAM] Unpleasant dreams
Did you notice that some of the most successful movies from Spielberg are about our deepest fears? Jurassic Park is about monsters from the past. Jaws is about monsters which lurk in the deep blue sea. Indiana Jones is about monsters (and treasures) hiding in dark tombs.Paul Boom remarks in his book "The Sweet Spot" that psychologists have long known that unpleasant dreams are more frequent than pleasant ones. Why is that so? Do unpleasant dreams prepare us for possible dangers or are we just relieved that the are over if they end?https://www.harpercollins.com/products/the-sweet-spot-paul-bloom?variant=40262533840930-J.-. --- - / ...- .- .-.. .. -.. / -- --- .-. ... . / -.-. --- -.. . FRIAM Applied Complexity Group listserv Fridays 9a-12p Friday St. Johns Cafe / Thursdays 9a-12p Zoom https://bit.ly/virtualfriam to (un)subscribe http://redfish.com/mailman/listinfo/friam_redfish.com FRIAM-COMIC http://friam-comic.blogspot.com/ archives: 5/2017 thru present https://redfish.com/pipermail/friam_redfish.com/ 1/2003 thru 6/2021 http://friam.383.s1.nabble.com/
Bug#1072389: patches to make cruft-ng work without locate
Hi Alexandre, * Alexandre Detiste [2024-06-03 10:04]: The scripts in explain/ ought to be run inside the chroot. The systemd script for example was already adapted to work without a running init. This could be done with chroot() and a bind mount of /usr/libexec/cruft or alternatively modifying every script to support DPKG_ROOT. I think option 1 will require root while option 2 will work in the non-root mode too. I slightly prerer option 2 which allows more case-by-case handling. Good point. You could actually use unshare to make it work without root but I would also prefer option 2. What do you think of a slow adoption as in explain.cc set's the DPKG_ROOT variable and all explain scripts get a test -z $DPKG_ROOT || exit 0 at the top. Then we can fix them individually as far as it makes sense. I also had a quick look into them, for those just running find and echo it should be ease to adopt. For those running dpkg-query or update-alternatives and alike there is a --root option we could use. There are also some the only make sense on a running system like WSL2 where I would just keep the exit 0 at the top. You can fork this on Salsa which is now the main repository. Right, do you prefer a merge request there? Cheers Jochen signature.asc Description: PGP signature
[FRIAM] Riding Tours in Santa Fe
Do you have good places that offer horseback riding tours around Santa Fe? Then I could perhaps convince my wife to visit Santa Fe next year. Maybe with a stop in L.A. before where we could visit Russ. She likes riding and we have bought a new horse yesterday named "Mack" after we lost the last one recently. The trails around Santa Fe must be nice from what I have seen.https://youtube.com/shorts/aOawCfcpmhU-J.-. --- - / ...- .- .-.. .. -.. / -- --- .-. ... . / -.-. --- -.. . FRIAM Applied Complexity Group listserv Fridays 9a-12p Friday St. Johns Cafe / Thursdays 9a-12p Zoom https://bit.ly/virtualfriam to (un)subscribe http://redfish.com/mailman/listinfo/friam_redfish.com FRIAM-COMIC http://friam-comic.blogspot.com/ archives: 5/2017 thru present https://redfish.com/pipermail/friam_redfish.com/ 1/2003 thru 6/2021 http://friam.383.s1.nabble.com/
Bug#1072389: patches to make cruft-ng work without locate
* Alexandre Detiste [2024-06-02 12:54]:
I'm impressed ! This will get merged.
\o/
I have also implemented a --root option to check chroot, see the
attached patch.
I guess you might be interested into providing
tiny improvement for the "rules/" too
depending on your taste of packages installed on your systems.
(or just the raw cruft report and I can figure out myself
which package own which file)
Honestly I did not look into the rules yet but here is my current cruft
run with some comments:
cruft report: So 02 Jun 2024 20:38:06 CEST
missing: dpkg
unexplained: /
/etc/Muttrc.d/abook.rc
abook.postinst
/etc/X11/default-display-manager
xdm.postinst
/etc/ca-certificates.conf.dpkg-old
/etc/udev/rules.d/72-seat-backlight-pci-_00_02_0.rules
/usr/lib/modules/6.8.12-amd64/modules.weakdep
/usr/lib/x86_64-linux-gnu/libmpi_usempi_ignore_tkr-gfortranso.40
(Bug: #1070985)
/usr/share/fonts/X11/Type1/encodings.dir
/usr/share/fonts/X11/Type1/fonts.alias
/usr/share/fonts/X11/Type1/fonts.dir
/usr/share/fonts/X11/Type1/fonts.scale
/usr/share/info/dir.old
/var/lib/alsa/card0.conf.d
/var/lib/alsa/card0.conf.d/dmics-nhlt.json
/var/lib/systemd/deb-systemd-helper-masked/systemd-rfkill.socket
tlp.postinst
/var/spool/apt-listbugs/lastprefclean
end.
Cheers Jochen
From dd0e111a54525cc7fbfbbc6adeca49cfda8a Mon Sep 17 00:00:00 2001
From: Jochen Sprickerhof
Date: Sun, 2 Jun 2024 20:34:11 +0200
Subject: [PATCH] Support --root to check chroots
Only implemented for --nolocate.
---
cpigs.cc | 6 +++---
cruft.cc | 31 +--
dpkg.h | 4 ++--
dpkg_lib.cc| 8 +---
locate.h | 2 +-
mlocate.cc | 2 +-
plocate.cc | 2 +-
test_locate.cc | 2 +-
8 files changed, 35 insertions(+), 22 deletions(-)
diff --git a/cpigs.cc b/cpigs.cc
index ecd1536..fd6ea6f 100644
--- a/cpigs.cc
+++ b/cpigs.cc
@@ -160,15 +160,15 @@ int main(int argc, char *argv[])
}
vector fs;
- read_locate(fs, "/usr/share/cruft/ignore");
+ read_locate(fs, "/usr/share/cruft/ignore", "/");
elapsed("plocate");
if (csv) cout << "path;package;type;cruft;size" << endl;
vector packages;
vector dpkg;
- dpkg_start();
- read_dpkg(packages, dpkg, static_);
+ dpkg_start("/");
+ read_dpkg(packages, dpkg, static_, "/");
dpkg_end();
elapsed("dpkg");
diff --git a/cruft.cc b/cruft.cc
index 9eb5f74..995cd69 100644
--- a/cruft.cc
+++ b/cruft.cc
@@ -110,7 +110,7 @@ static void one_file(const string& path)
}
// is it a static file ?
- dpkg_start();
+ dpkg_start("/");
if (query(path.c_str())) {
dpkg_end();
exit(0);
@@ -184,6 +184,7 @@ static const char* const default_filter_dir = "/etc/cruft/filters/";
static const char* const default_ignore_file = "/etc/cruft/ignore";
static const char* const default_ruleset_file = "/usr/share/cruft/ruleset";
static const char* const default_bugs_file = "/usr/share/cruft/bugs";
+static const char* const default_root_dir = "/";
static void print_help_message()
{
@@ -199,13 +200,14 @@ static void print_help_message()
cout << "-I --ignore path for ignore file (default: " << default_ignore_file << ")\n";
cout << "-R --ruleset path for ruleset file (default: " << default_ruleset_file << ")\n";
cout << "-B --bugspath for known bugs file (default: " << default_bugs_file << ")\n";
+ cout << "-r --rootroot directory (default: " << default_root_dir << ")\n";
cout << '\n';
cout << "-h --helpthis help message\n";
}
-int read_nolocate(vector& fs, const string& ignore_path)
+int read_nolocate(vector& fs, const string& ignore_path, const string& root_dir)
{
bool debug=getenv("DEBUG") != nullptr;
@@ -220,7 +222,7 @@ int read_nolocate(vector& fs, const string& ignore_path)
for (auto entry =
filesystem::recursive_directory_iterator{
- "/",
+ root_dir,
filesystem::directory_options::skip_permission_denied};
entry != filesystem::recursive_directory_iterator(); entry++)
{
@@ -257,7 +259,7 @@ int read_nolocate(vector& fs, const string& ignore_path)
if (ignored) continue;
if (!pyc_has_py(string{filename}, debug))
- fs.emplace_back(filename);
+ fs.emplace_back(filename.substr(root_dir.length()-1));
}
sort(fs.begin(), fs.end());
@@ -271,7 +273,8 @@ static void cruft(const string& ignore_file,
Bug#1072389: patches to make cruft-ng work without locate
Source: cruft-ng
Version: 0.9.62
Severity: wishlist
Tags: patch
Hi Alexandre,
I would like to use cruft-ng on systems without having a locate
installed as it is fast enough without it on my SSD. Please find two
patches attached to implement this.
Thanks for maintaining cruft-ng!
Cheers Jochen
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.8.11-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
From d79bac0c57cab984fc2708dd7596b387bfd4d5ec Mon Sep 17 00:00:00 2001
From: Jochen Sprickerhof
Date: Sun, 2 Jun 2024 11:59:28 +0200
Subject: [PATCH 1/2] Move read_ignores to own file
Allows using it in other functions.
---
Makefile| 5 +++--
plocate.cc | 18 +-
read_ignores.cc | 23 +++
read_ignores.h | 6 ++
4 files changed, 33 insertions(+), 19 deletions(-)
create mode 100644 read_ignores.cc
create mode 100644 read_ignores.h
diff --git a/Makefile b/Makefile
index d9fe79e..5eb73be 100644
--- a/Makefile
+++ b/Makefile
@@ -7,7 +7,7 @@ CXXFLAGS ?= -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wl,-z
CXXFLAGS += -Wall -Wextra
override CXXFLAGS += $(LIBDPKG_CFLAGS)
#CXXFLAGS += -std=c++17 # clang++
-SHARED_OBJS = explain.o filters.o shellexp.o usr_merge.o python.o owner.o
+SHARED_OBJS = explain.o filters.o shellexp.o usr_merge.o python.o owner.o
read_ignores.o
CRUFT_OBJS = cruft.o dpkg_exclude.o bugs.o
sid: cruft ruleset cpigs
@@ -19,8 +19,9 @@ cpigs.o: cpigs.cc owner.h
owner.o: owner.cc owner.h
explain.o: explain.cc owner.h
filters.o: filters.cc owner.h
-plocate.o: plocate.cc locate.h
+plocate.o: plocate.cc locate.h read_ignores.h
mlocate.o: mlocate.cc locate.h
+read_ignores.o: read_ignores.cc read_ignores.h
cruft.o: cruft.cc explain.h filters.h dpkg.h python.h
dpkg_lib.o: dpkg_lib.cc dpkg.h /usr/include/dpkg/dpkg.h
diff --git a/plocate.cc b/plocate.cc
index 20cf762..9af52ce 100644
--- a/plocate.cc
+++ b/plocate.cc
@@ -9,23 +9,7 @@
#include "locate.h"
#include "python.h"
-
-static void read_ignores(vector& ignores, const string& ignore_path)
-{
- ifstream ignore_file(ignore_path);
- if (!ignore_file.is_open())
- ignore_file.open("/usr/share/cruft/ignore");
-
- for (string ignore_line; getline(ignore_file,ignore_line);)
- {
- if (ignore_line.empty()) continue;
- if (ignore_line.front() == '/') {
- if (ignore_line.back() != '/')
- ignore_line += "/";
- ignores.emplace_back(std::move(ignore_line));
- }
- }
-}
+#include "read_ignores.h"
int read_locate(vector& fs, const string& ignore_path)
{
diff --git a/read_ignores.cc b/read_ignores.cc
new file mode 100644
index 000..d3cd1e5
--- /dev/null
+++ b/read_ignores.cc
@@ -0,0 +1,23 @@
+// Copyright © 2015 Alexandre Detiste
+// SPDX-License-Identifier: GPL-2.0-or-later
+
+#include
+
+#include "read_ignores.h"
+
+void read_ignores(vector& ignores, const string& ignore_path)
+{
+ ifstream ignore_file(ignore_path);
+ if (!ignore_file.is_open())
+ ignore_file.open("/usr/share/cruft/ignore");
+
+ for (string ignore_line; getline(ignore_file,ignore_line);)
+ {
+ if (ignore_line.empty()) continue;
+ if (ignore_line.front() == '/') {
+ if (ignore_line.back() != '/')
+ ignore_line += "/";
+ ignores.emplace_back(std::move(ignore_line));
+ }
+ }
+}
diff --git a/read_ignores.h b/read_ignores.h
new file mode 100644
index 000..cb6c68b
--- /dev/null
+++ b/read_ignores.h
@@ -0,0 +1,6 @@
+#include
+#include
+
+using namespace std;
+
+void read_ignores(vector& ignores, const string& ignore_path);
--
2.45.1
>From 79e76c76202a8183d027d64b931da34c4445750f Mon Sep 17 00:00:00 2001
From: Jochen Sprickerhof
Date: Sun, 2 Jun 2024 12:00:53 +0200
Subject: [PATCH 2/2] Support running without a locate
Also move p/mlocate to Recommends.
---
Makefile | 2 +-
cruft.cc | 92 +-
debian/control | 1 +
3 files changed, 86 insertions(+), 9 deletions(-)
diff --git a/Makefile b/Makefile
index 5eb73be..5b81236 100644
--- a/Makefile
+++ b/Makefile
@@ -23,7 +23,7 @@ plocate.o: plocate.cc locate.h read_ignores.h
mlocate.o: mlocate.cc locate.h
read_ignores.o: read_ignores.cc read_ignores.h
-cruft.o: cruft.cc explain.h filters.h dpkg.h python.h
+cruft.o: cruft.cc explain.h filters.h dpkg.h python.h read_ignores.h
dpkg_lib.o: dpkg_
Re: [Remind-Fans] New release of Remind coming soon; testers wanted
Hi Dianne,
* Dianne Skoll via Remind-fans [2024-05-31 22:15]:
If so, I invite you to check out a branch containing upcoming changes
to Remind:
https://git.skoll.ca/Skollsoft-Public/Remind/src/branch/wip/revamped-expression-evaluation
The only issue I found is:
echo "REM Jan 19 2026 *1 UNTIL [ max('2026-01-19', realtoday()) ] MSG Foo" |
src/remind -
-stdin-(1): Missing ']'
No reminders.
The "Missing ']'" does not show up in Remind 04.03.07.
Cheers Jochen
signature.asc
Description: PGP signature
___
Remind-fans mailing list
Remind-fans@lists.skoll.ca
https://dianne.skoll.ca/mailman/listinfo/remind-fans
Remind is at https://dianne.skoll.ca/projects/remind/
[Qbs] qbspkgconfig in qbs 2.3.1
Hi,
I tried to build a project for the first time after a couple of years
and qbs versions. I now use QtCreator 13.0.1 with qbs 2.3.1.
The product is a StaticLibrary and has dependencies
Depends { name: "Qt", submodules: ["core" , "gui"] }
Depends { name: "taglib" }
In the past "taglib" has been resolved by the default fallback for
pkgconfig.
I added
qbsModuleProviders: "qbspkgconfig"
in the hope to get the correct settings for taglib. But now, qbs fails
with the following error message:
mediadb-extras.qbs:13: warning: Dependency 'Qt.core' not found for
product 'mediadb-extras'.
What I am doing wrong? I couldn't find an example showing dependencies
to Qt and a pkgconfig provided library.
I am running on Ubuntu 22.04 using Qt 5.15.2.
Regards, Jochen
___
Qbs mailing list
Qbs@qt-project.org
https://lists.qt-project.org/listinfo/qbs
Re: [FRIAM] words
This prompt reminds me of the recent book from Matt Strassler named "Waves in an Impossible Sea: How Everyday Life Emerges from the Cosmic Ocean". It sounds interesting but they don't have it in the libraries here yet and the hardcover is too expensive.https://www.harvard.com/book/waves_in_an_impossible_sea/-J. Original message From: glen Date: 5/30/24 7:00 PM (GMT+01:00) To: friam@redfish.com Subject: Re: [FRIAM] words Hm. I suppose it's worth a shot. If we prompt with "All energy in the universe is expressed in motion. All motion is expressed in waves. All waves are curved. So where do the straight lines come from to make the Platonic solids?" Then it's possible the LLM would complete that with "There are no straight lines. So when I took the flower of life and opened it properly, I found all new wave conjugations that expose the in-between spaces. It's the thing that holds us all together." But I sincerely doubt it.But maybe by "have to have", you mean that an LLM *could* be trained (and/or structured) to bias toward rare expressions/concepts in its training set instead of more common ones.On 5/30/24 09:01, Marcus Daniels wrote:> I'm not going to watch Joe Rogan, but I think LLMs don't have to have this homogenous mean problem. They capture a distribution, so it is a question of the inference procedure to sample from it. What is the (beam) search algorithm, how deep does it go, and what is the sampling temperature.> > -Original Message-> From: Friam On Behalf Of glen> Sent: Wednesday, May 29, 2024 1:09 PM> To: friam@redfish.com> Subject: [FRIAM] words> > Terrence Howard | Full Address and Q | Oxford Union https://youtu.be/ca1vIYmGyYA?si=vhbtA5WUX1CV8LZH> > Joe Rogan Experience #2152 - Terrence Howard> https://youtu.be/g197xdRZsW0?si=kFTa7lQJI1lKA6R1> > I just can't help but wonder how many people, while listening to Howard talk, realize they're interacting with a sick individual (who deserves compassion but does not deserve gullibility). Or how many people are (like Rogan seems to have been) ... uh ... hypnotized by Howard's well-crafted word salad. In this LLM era, where many people, including some on this list, are enthralled by random bullshit, it seems like a reasonable thing to wonder about. Luckily, the clear cognitive power Howard exhibits puts him in some kind of rare quantile. So our LLMs, being driven mostly to a homogenous mean, their random bullshit will, by definition, match those of us within 1 or a few sigma and suppress the weirdest among us.> > Being a fan of steel-manning, I'm having a bit of a crisis. The paradox of tolerance tells me that we absolutely must call bullshit at some point, even if it's not ruthless. Those Oxford Union attendees danced around egging him on and calling him out. Is this what the kids call "cringe"? Do we just cringe and tolerate it? Or, like Rogan, pretend to credibility relying on his weirdness to be so weird that it'll disappear into the tails? Or should we be deplatforming the bullshit?> -- ꙮ Mɥǝu ǝlǝdɥɐuʇs ɟᴉƃɥʇ' ʇɥǝ ƃɹɐss snɟɟǝɹs˙ ꙮ-. --- - / ...- .- .-.. .. -.. / -- --- .-. ... . / -.-. --- -.. .FRIAM Applied Complexity Group listservFridays 9a-12p Friday St. Johns Cafe / Thursdays 9a-12p Zoom https://bit.ly/virtualfriamto (un)subscribe http://redfish.com/mailman/listinfo/friam_redfish.comFRIAM-COMIC http://friam-comic.blogspot.com/archives: 5/2017 thru present https://redfish.com/pipermail/friam_redfish.com/ 1/2003 thru 6/2021 http://friam.383.s1.nabble.com/-. --- - / ...- .- .-.. .. -.. / -- --- .-. ... . / -.-. --- -.. . FRIAM Applied Complexity Group listserv Fridays 9a-12p Friday St. Johns Cafe / Thursdays 9a-12p Zoom https://bit.ly/virtualfriam to (un)subscribe http://redfish.com/mailman/listinfo/friam_redfish.com FRIAM-COMIC http://friam-comic.blogspot.com/ archives: 5/2017 thru present https://redfish.com/pipermail/friam_redfish.com/ 1/2003 thru 6/2021 http://friam.383.s1.nabble.com/
Bug#1072222: log viewer does not show some failed test in red
Package: debci Severity: minor Hi, for this log: https://ci.debian.net/packages/s/sbuild/testing/riscv64/47087233/#S6 test build-procenv and test unshare but only the unshare test is shown in red whereas the build-procenv is blue (indicating a successful test). Could you color the build-procenv in red as well? (I asked about this in #debci and Antonio Terceiro proposed to fill a bug.) Thanks! Jochen
Bug#1072085: closing 1072085
close 1072085 thanks This is fixed with sbuild 0.85.9. Cheers Jochen
Bug#1072151: src:golang-github-containerd-cgroups tries to access /sys/kernel/mm/hugepages in tests
Source: golang-github-containerd-cgroups Version: 1.0.4-1 Severity: normal Hi, src:golang-github-containerd-cgroups tries to access /sys/kernel/mm/hugepages which is not guaranteed to be there in containers: https://systemd.io/CONTAINER_INTERFACE/ This is for example the case with sbuild in unshare mode (starting with 0.85.9) due to #1071234. I would propose to either mock the path or disable the test. Cheers Jochen
Bug#1072147: test fail in sbuild+unshare
Source: golang-github-containers-buildah Version: 1.33.7+ds1-1 Severity: normal Hi, golang-github-containers-buildah is affected by #1070003 in sbuild+unshare which is not really fixable: https://buildd.debian.org/status/logs.php?pkg=golang-github-containers-buildah=1.35.3%2Bds1-1=all Can you please fix or disable the test as the buildd started using the unshare backend? Cheers Jochen
Bug#1070014: libwibble: FTBFS on arm{64,el}: (7/36) Fs: ../wibble/sys/fs.test.h: 72: assertion `i.ischr()' failed;
Hi, * Sebastian Ramacher [2024-04-28 17:11]: https://buildd.debian.org/status/fetch.php?pkg=libwibble=arm64=1.1-3%2Bb1=1714230781=0 make[5]: Entering directory '/<>/debian/build' cd /<>/debian/build/wibble && sh -c "LD_LIBRARY_PATH=/<>/debian/build/wibble /<>/debian/build/wibble/wibble-test" (1/36) Regexp: .. 6/6 ok (2/36) Process: .. 2/2 ok (3/36) Range: ... 11/11 ok (4/36) Buffer: . 5/5 ok (5/36) CommandlineEngine: .. 10/10 ok (6/36) Consumer: ... 3/3 ok (7/36) Fs: ../wibble/sys/fs.test.h: 72: assertion `i.ischr()' failed; --> FAILED: (1/11) directoryIsdir (caught signal 6) (7/36) Fs: . 10/11 ok This is due to #1070003 in sbuild+unshare which is not really fixable. As the buildd now use the unshare backend I would propose to disable the test in libwibble. Cheers Jochen signature.asc Description: PGP signature
Bug#1070014: libwibble: FTBFS on arm{64,el}: (7/36) Fs: ../wibble/sys/fs.test.h: 72: assertion `i.ischr()' failed;
Hi, * Sebastian Ramacher [2024-04-28 17:11]: https://buildd.debian.org/status/fetch.php?pkg=libwibble=arm64=1.1-3%2Bb1=1714230781=0 make[5]: Entering directory '/<>/debian/build' cd /<>/debian/build/wibble && sh -c "LD_LIBRARY_PATH=/<>/debian/build/wibble /<>/debian/build/wibble/wibble-test" (1/36) Regexp: .. 6/6 ok (2/36) Process: .. 2/2 ok (3/36) Range: ... 11/11 ok (4/36) Buffer: . 5/5 ok (5/36) CommandlineEngine: .. 10/10 ok (6/36) Consumer: ... 3/3 ok (7/36) Fs: ../wibble/sys/fs.test.h: 72: assertion `i.ischr()' failed; --> FAILED: (1/11) directoryIsdir (caught signal 6) (7/36) Fs: . 10/11 ok This is due to #1070003 in sbuild+unshare which is not really fixable. As the buildd now use the unshare backend I would propose to disable the test in libwibble. Cheers Jochen signature.asc Description: PGP signature
Bug#1070014: libwibble: FTBFS on arm{64,el}: (7/36) Fs: ../wibble/sys/fs.test.h: 72: assertion `i.ischr()' failed;
Hi, * Sebastian Ramacher [2024-04-28 17:11]: https://buildd.debian.org/status/fetch.php?pkg=libwibble=arm64=1.1-3%2Bb1=1714230781=0 make[5]: Entering directory '/<>/debian/build' cd /<>/debian/build/wibble && sh -c "LD_LIBRARY_PATH=/<>/debian/build/wibble /<>/debian/build/wibble/wibble-test" (1/36) Regexp: .. 6/6 ok (2/36) Process: .. 2/2 ok (3/36) Range: ... 11/11 ok (4/36) Buffer: . 5/5 ok (5/36) CommandlineEngine: .. 10/10 ok (6/36) Consumer: ... 3/3 ok (7/36) Fs: ../wibble/sys/fs.test.h: 72: assertion `i.ischr()' failed; --> FAILED: (1/11) directoryIsdir (caught signal 6) (7/36) Fs: . 10/11 ok This is due to #1070003 in sbuild+unshare which is not really fixable. As the buildd now use the unshare backend I would propose to disable the test in libwibble. Cheers Jochen signature.asc Description: PGP signature
Bug#1072146: libexplain: kill(pid = 42 "sh", sig = SIGTERM) failed, Operation not permitted (EPERM)
Source: libexplain Version: 1.4.D001-13 Severity: normal Tags: patch Hi, libexplain fails to build in sbuild+unshare now used on some of the buildd: PATH=`pwd`/bin:$PATH /bin/sh test/04/t0462a.sh 1c1 < kill(pid = 42, sig = SIGTERM) failed, Operation not permitted (EPERM) --- > kill(pid = 42 "sh", sig = SIGTERM) failed, Operation not permitted (EPERM) FAILED test of kill EPERM make[2]: *** [Makefile:42004: t0462a] Error 1 I assume this is due to the test is skipped in the schroot backend. Tagging patch as it is easy to fix from the diff above. Cheers Jochen
Bug#1072146: libexplain: kill(pid = 42 "sh", sig = SIGTERM) failed, Operation not permitted (EPERM)
Source: libexplain Version: 1.4.D001-13 Severity: normal Tags: patch Hi, libexplain fails to build in sbuild+unshare now used on some of the buildd: PATH=`pwd`/bin:$PATH /bin/sh test/04/t0462a.sh 1c1 < kill(pid = 42, sig = SIGTERM) failed, Operation not permitted (EPERM) --- > kill(pid = 42 "sh", sig = SIGTERM) failed, Operation not permitted (EPERM) FAILED test of kill EPERM make[2]: *** [Makefile:42004: t0462a] Error 1 I assume this is due to the test is skipped in the schroot backend. Tagging patch as it is easy to fix from the diff above. Cheers Jochen
[Qt-creator] Incompatibility between clang-tidy and gcc
Hi, I build my projects with qbs and gcc. For some legacy reasons, it uses "-fnothrow-opt". Unfortunately, this option is not known by clang-tidy and for a few versions clang-tidy does not ignore this option any longer but exits with an error. I don't see any chance to fix this in qbs as the qbs product is not resolved separately for clang-tidy but it uses the gcc build. Is there any way to filter the compiler options before they are forwarded to clang-tidy? I added a simple filter function in clangtoolrunner.cpp but I would prefer a solution that is external to QtCreator. Regards, Jochen -- Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Bug#1072145: docker.io: Failing test Can't find mount point of /
Source: docker.io Version: 20.10.24+dfsg1-1 Severity: normal Tags: patch Hi, The docker.io package carries a patch to disable a test in pbuilder: https://sources.debian.org/src/docker.io/20.10.25%2Bdfsg1-3/debian/patches/test--skip-daemon-oci-linux-pbuilder-tests.patch/ Please skip that test unconditionally as it also fails in other environments like sbuild in unshare mode which is now used on the buildd. Cheers Jochen
[Bug 1580088] Re: Trusty sbuild fails for source debs that contain staged dependencies
** Changed in: sbuild (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580088 Title: Trusty sbuild fails for source debs that contain staged dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/1580088/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1619608] Re: sbuild should depend on libdpkg-perl ≥ 1.17.14
Closing this as it is about a backport for a no longer supported version. ** Changed in: sbuild (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1619608 Title: sbuild should depend on libdpkg-perl ≥ 1.17.14 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1619608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1440851] Re: `--foreign` flag broken
trusty is no longer supported, so closing this. ** Changed in: sbuild (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1440851 Title: `--foreign` flag broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sbuild/+bug/1440851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Bug#1071939: taskwarrior: Naming conflict with go-task task tool
Hi Guillaume, * Guillaume Yziquel [2024-05-26 09:30]: For various development reaons on my machine, I had to install the go-task task tool. It is a task runner in the go ecosystem that has named its executable... task. https://github.com/go-task/task.git This very obviously conflicts with the name of taskwarrior's executable. Which saddens me a lot. That naming choice from go-task is most unfortunate. But I do not expect this name conflict to be of major importance to them. But I need both taskwarrior and go-task's task. Because I use go-task's task in a git repository, and use custom taskwarrior configuration to handle a local bug-tracker local to the same git repository. I would therefore appreciate, even if I do not have much hope on that front, that debian packaging and the go-task team could come up with an agreement on the name used here. As to myself, I'll be looking at a way to rename the task taskwarrior executable on my system, possibly by modifying the debian packaging. As long as go-task is not part of Debian I don't think we should act on this. Otherwise Debian policy 10.1 has something on name conflicts: https://www.debian.org/doc/debian-policy/ch-files.html#s-binaries P.S.: using ubuntu (for the moment), but I believe debian is the right place to report this bug. I would rather recommend adding symbolic links in /usr/local/bin or ~/.local/bin with the new names. Cheers Jochen signature.asc Description: PGP signature
Bug#1072085: FTBFS: PermissionError: [Errno 13] Permission denied: '/dev/stdout'
Hi Chris,
this is #1070007. I plan to upload a new version soon (just need to look
into two unrelated regressions), so I would propose to not act on this.
Cheers Jochen
* Chris Hofstaedtler [2024-05-28 10:01]:
Source: supervisor
Version: 4.2.5-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: z...@debian.org
Dear Maintainer,
your package fails to build from source, see below and the attached
build log.
This build was done in sbuild with unshare backend. As this is now a
configuration used by the buildds, people consider such problems to be
release-critical.
Chris
==
ERROR: test_ctor_with_dev_stdout
(supervisor.tests.test_loggers.StdoutTests.test_ctor_with_dev_stdout)
--
Traceback (most recent call last):
File "/<>/supervisor/tests/test_loggers.py", line 232, in
test_ctor_with_dev_stdout
handler = self._makeOne('/dev/stdout')
File "/<>/supervisor/tests/test_loggers.py", line 37, in _makeOne
return klass(*arg, **kw)
^
File "/<>/supervisor/loggers.py", line 160, in __init__
self.stream = open(filename, mode)
PermissionError: [Errno 13] Permission denied: '/dev/stdout'
--
Ran 1369 tests in 9.365s
FAILED (errors=1)
Test failed:
error: Test failed:
E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1:
python3.11 setup.py test
dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned
exit code 13
make: *** [debian/rules:4: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
signature.asc
Description: PGP signature
Bug#1072085: FTBFS: PermissionError: [Errno 13] Permission denied: '/dev/stdout'
Hi Chris,
this is #1070007. I plan to upload a new version soon (just need to look
into two unrelated regressions), so I would propose to not act on this.
Cheers Jochen
* Chris Hofstaedtler [2024-05-28 10:01]:
Source: supervisor
Version: 4.2.5-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: z...@debian.org
Dear Maintainer,
your package fails to build from source, see below and the attached
build log.
This build was done in sbuild with unshare backend. As this is now a
configuration used by the buildds, people consider such problems to be
release-critical.
Chris
==
ERROR: test_ctor_with_dev_stdout
(supervisor.tests.test_loggers.StdoutTests.test_ctor_with_dev_stdout)
--
Traceback (most recent call last):
File "/<>/supervisor/tests/test_loggers.py", line 232, in
test_ctor_with_dev_stdout
handler = self._makeOne('/dev/stdout')
File "/<>/supervisor/tests/test_loggers.py", line 37, in _makeOne
return klass(*arg, **kw)
^
File "/<>/supervisor/loggers.py", line 160, in __init__
self.stream = open(filename, mode)
PermissionError: [Errno 13] Permission denied: '/dev/stdout'
--
Ran 1369 tests in 9.365s
FAILED (errors=1)
Test failed:
error: Test failed:
E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1:
python3.11 setup.py test
dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" returned
exit code 13
make: *** [debian/rules:4: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
signature.asc
Description: PGP signature
Bug#1072068: golang-github-elazarl-goproxy accesses network resources during the build
Source: golang-github-elazarl-goproxy
Version: 1.1+git20231117.7cc037d+dfsg-1
Severity: serious
Tags: sid trixie ftbfs
Justification: Policy 4.9
X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org
Control: affects -1 buildd.debian.org
Hi,
golang-github-elazarl-goproxy accesses network resources during the
build:
=== RUN TestSimpleHttpRequest
serving end proxy server at localhost:5000
proxy_test.go:958: Error while requesting google with http
&{500 Internal Server Error 500 HTTP/1.1 1 1 map[Content-Length:[108]
Content-Type:[text/plain; charset=utf-8] Date:[Tue, 28 May 2024 04:36:39 GMT]
X-Content-Type-Options:[nosniff]] 0xc00053e800 108 [] false false map[]
0xcc6360 }
&{500 Internal Server Error 500 HTTP/1.1 1 1 map[Content-Length:[108]
Content-Type:[text/plain; charset=utf-8] Date:[Tue, 28 May 2024 04:36:39 GMT]
X-Content-Type-Options:[nosniff]] 0xc00053eac0 108 [] false false map[]
0xcc6c60 }
--- FAIL: TestSimpleHttpRequest (1.01s)
=== RUN TestResponseContentLength
--- PASS: TestResponseContentLength (0.00s)
FAIL
FAILgithub.com/elazarl/goproxy 4.643s
This can be tested with the sbuild unshare backend.
Cheers Jochen
Bug#1072068: golang-github-elazarl-goproxy accesses network resources during the build
Source: golang-github-elazarl-goproxy
Version: 1.1+git20231117.7cc037d+dfsg-1
Severity: serious
Tags: sid trixie ftbfs
Justification: Policy 4.9
X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org
Control: affects -1 buildd.debian.org
Hi,
golang-github-elazarl-goproxy accesses network resources during the
build:
=== RUN TestSimpleHttpRequest
serving end proxy server at localhost:5000
proxy_test.go:958: Error while requesting google with http
&{500 Internal Server Error 500 HTTP/1.1 1 1 map[Content-Length:[108]
Content-Type:[text/plain; charset=utf-8] Date:[Tue, 28 May 2024 04:36:39 GMT]
X-Content-Type-Options:[nosniff]] 0xc00053e800 108 [] false false map[]
0xcc6360 }
&{500 Internal Server Error 500 HTTP/1.1 1 1 map[Content-Length:[108]
Content-Type:[text/plain; charset=utf-8] Date:[Tue, 28 May 2024 04:36:39 GMT]
X-Content-Type-Options:[nosniff]] 0xc00053eac0 108 [] false false map[]
0xcc6c60 }
--- FAIL: TestSimpleHttpRequest (1.01s)
=== RUN TestResponseContentLength
--- PASS: TestResponseContentLength (0.00s)
FAIL
FAILgithub.com/elazarl/goproxy 4.643s
This can be tested with the sbuild unshare backend.
Cheers Jochen
Bug#1072067: golang-github-containerd-stargz-snapshotter fails to build on non tmpfs
Source: golang-github-containerd-stargz-snapshotter Version: 0.12.0-2 Severity: minor Hi, your package fails to build when the build directory is not on a tmpfs: === RUN TestOverlayView snapshot_test.go:713: expected 1 mount option but got 2 --- FAIL: TestOverlayView (0.01s) FAIL FAILgithub.com/containerd/stargz-snapshotter/snapshot 0.026s Can you please fix or disable the test? Cheers Jochen -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.8.11-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1072047: missing build dependency on passwd
Source: nsscache Version: 0.49-2 Severity: minor Tags: ftbfs patch Hi, your package fails to build when the passwd package is not installed. For the buildd this is currently still the case but will change once debootstrap 1.0.133 or later is used. Could you please add the build dependency? Cheers Jochen
Bug#1072046: missing build dependency on passwd
Source: go-dlib Version: 5.6.0.9+dfsg-4 Severity: minor Tags: ftbfs patch Hi, your package fails to build when the passwd package is not installed. For the buildd this is currently still the case but will change once debootstrap 1.0.133 or later is used. Could you please add the build dependency? Cheers Jochen -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.8.11-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
[go-nuts] mutex in slog/handler.go?
Hello,
In the Go standard library, in the file log/slog/handler.go, I found the
following code:
func (h *commonHandler) clone() *commonHandler {
// We can't use assignment because we can't copy the mutex.
return {
json: h.json,
opts: h.opts,
preformattedAttrs: slices.Clip(h.preformattedAttrs),
groupPrefix: h.groupPrefix,
groups:slices.Clip(h.groups),
nOpenGroups: h.nOpenGroups,
w: h.w,
mu:h.mu, // mutex shared among all clones of this handler
}
}
The first comment states that "we can't copy the mutex", but then the last
line seems to copy the mutex anyway. What is going on here?
Maybe this just an oversight from a time when every hander had its own
mutex? Or is there something subtle going on here?
Many thanks,
Jochen
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/golang-nuts/153e9898-f17e-44cc-ab2a-8570f916c0c3n%40googlegroups.com.
Bug#1071712: RM: ros-bond-core/experimental -- ROM; not needed for t64 transition
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: ros-bond-c...@packages.debian.org Control: affects -1 + src:ros-bond-core User: ftp.debian@packages.debian.org Usertags: remove -- debian-science-maintainers mailing list debian-science-maintainers@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-maintainers
Bug#1071712: RM: ros-bond-core/experimental -- ROM; not needed for t64 transition
Package: ftp.debian.org Severity: normal X-Debbugs-Cc: ros-bond-c...@packages.debian.org Control: affects -1 + src:ros-bond-core User: ftp.debian@packages.debian.org Usertags: remove
(commons-lang) branch master updated: Fixing the previous commit.
This is an automated email from the ASF dual-hosted git repository.
jochen pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-lang.git
The following commit(s) were added to refs/heads/master by this push:
new 1e64e11e7 Fixing the previous commit.
1e64e11e7 is described below
commit 1e64e11e747b03a8d49c293c18847b3a9e65fcfb
Author: Jochen Wiedmann
AuthorDate: Thu May 23 00:05:37 2024 +0200
Fixing the previous commit.
---
.mvn/.gitignore| 4 +
.../commons/lang3/annotations/AnnotationsTest.java | 122 -
2 files changed, 4 insertions(+), 122 deletions(-)
diff --git a/.mvn/.gitignore b/.mvn/.gitignore
new file mode 100644
index 0..f26bafb8b
--- /dev/null
+++ b/.mvn/.gitignore
@@ -0,0 +1,4 @@
+#
+# Empty file (Maven 4 wants the directory .mvn to be present,
+# and we want Git to create it.)
+#
diff --git
a/src/test/java/org/apache/commons/lang3/annotations/AnnotationsTest.java
b/src/test/java/org/apache/commons/lang3/annotations/AnnotationsTest.java
deleted file mode 100644
index df1aa70f3..0
--- a/src/test/java/org/apache/commons/lang3/annotations/AnnotationsTest.java
+++ /dev/null
@@ -1,122 +0,0 @@
-/*
- * Licensed to the Apache Software Foundation (ASF) under one or more
- * contributor license agreements. See the NOTICE file distributed with
- * this work for additional information regarding copyright ownership.
- * The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
- * the License. You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-package org.apache.commons.lang3.annotations;
-
-import static org.junit.jupiter.api.Assertions.assertNotNull;
-import static org.junit.jupiter.api.Assertions.assertSame;
-
-import java.lang.annotation.Target;
-import java.util.function.Function;
-
-import org.junit.jupiter.api.Test;
-
-
-/** This class ensures, that the annotations are properly configured
- * with regard to {@link Target}.
- *
- * The so-called test methods are not actually testing anything, because
- * an invalid configuration would be detected by the compiler. However,
- * we have the unit test framework in place, and it is running anyways,
- * so there's no harm in a few additional methods.
- */
-public class AnnotationsTest {
-public static class Wrapper {
-private final Object wrappedObject;
-
-@Insecure
-public Wrapper(Object wrappedObject) {
-this.wrappedObject = wrappedObject;
-}
-
-Object getWrappedObject() {
-return wrappedObject;
-}
-}
-
-private static Wrapper newWrapper(Object wrappedObject) {
-return new Wrapper(wrappedObject);
-}
-
-/** Test, whether we can have an @Insecure annotation on a constructor.
- */
-@Test
-public void testConstructorAnnotatableAsInsecure() {
-final Object unsafeObject = new Object();
-// Static code analysis should reject this, because the
-// parameter (the newly created instance of Object) isn't known
-// to be safe.
-final Wrapper wrapper = new Wrapper(unsafeObject);
-assertNotNull(wrapper);
-assertSame(unsafeObject, wrapper.getWrappedObject());
-}
-
-/** Test, whether we can have an @Insecure annotation on a method.
- */
-@Test
-public void testMethodAnnotatableAsInsecure() {
-final Object unsafeObject = new Object();
-// Static code analysis should reject this, because the
-// parameter (the newly created instance of Object) isn't known
-// to be safe.
-final Wrapper wrapper = newWrapper(unsafeObject);
-assertNotNull(wrapper);
-assertSame(unsafeObject, wrapper.getWrappedObject());
-}
-
-/** Test, whether we can have a @Safe annotation on a local variable.
- */
-@Test
-public void testLocalVariablesAnnotatableAsSafe() {
-@Safe final String wrappedString = "Hello, world!";
-// Static code analysis should accept this, because the variable
-// is annotated with @Safe.
-final Wrapper wrapper = newWrapper(wrappedString);
-assertNotNull(wrapper);
-assertSame(wrappedString, wrapper.getWrappedObject());
-}
-
-/** Test, whether we can have a @Safe annotation on a field.
- */
-@Test
-public void testFieldsAnnotatableAsSafe() {
-// Static code analysis should accept this, because the field
-// is annota
(commons-lang) branch master updated: Undoing 3322d974876b8d4f934d3544967103ebbcaef726
This is an automated email from the ASF dual-hosted git repository.
jochen pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-lang.git
The following commit(s) were added to refs/heads/master by this push:
new 9980cf11e Undoing 3322d974876b8d4f934d3544967103ebbcaef726
9980cf11e is described below
commit 9980cf11e36ee58bf8556188bf252946f290b6c8
Author: Jochen Wiedmann
AuthorDate: Wed May 22 20:00:10 2024 +0200
Undoing 3322d974876b8d4f934d3544967103ebbcaef726
---
src/changes/changes.xml| 1 -
.../apache/commons/lang3/annotations/Insecure.java | 48 -
.../org/apache/commons/lang3/annotations/Safe.java | 61 --
.../commons/lang3/annotations/package-info.java| 37 -
4 files changed, 147 deletions(-)
diff --git a/src/changes/changes.xml b/src/changes/changes.xml
index b69e1f8a2..34841687a 100644
--- a/src/changes/changes.xml
+++ b/src/changes/changes.xml
@@ -140,7 +140,6 @@ The type attribute can be add,update,fix,remove.
Bump org.apache.commons:commons-text from 1.11.0 to 1.12.0
#1200.
Drop obsolete JDK 13 Maven profile #1142.
-Added the annotations
package, including the Insecure, and Safe annotations.
diff --git a/src/main/java/org/apache/commons/lang3/annotations/Insecure.java
b/src/main/java/org/apache/commons/lang3/annotations/Insecure.java
deleted file mode 100644
index 2802f1189..0
--- a/src/main/java/org/apache/commons/lang3/annotations/Insecure.java
+++ /dev/null
@@ -1,48 +0,0 @@
-/*
- * Licensed to the Apache Software Foundation (ASF) under one or more
- * contributor license agreements. See the NOTICE file distributed with
- * this work for additional information regarding copyright ownership.
- * The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
- * the License. You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-package org.apache.commons.lang3.annotations;
-
-import java.lang.annotation.Documented;
-import java.lang.annotation.ElementType;
-import java.lang.annotation.Retention;
-import java.lang.annotation.RetentionPolicy;
-import java.lang.annotation.Target;
-
-/**
- * This annotation is used to indicate, that a constructor, or method
- * is insecure to use, unless the input parameters contain safe ("trusted")
- * values.
- *
- * For example, consider a method like
- * {@literal @Insecure}
- * public void runCommand(String pCmdLine) {
- * }
- *
- *
- * The example method would invoke {@code /bin/sh} (Linux, Unix, or MacOS), or
- * {@code cmd} (Windows) to run an external command, as given by the parameter
- * {@code pCmdLine}. Obviously, depending on the value of the parameter,
- * this can be dangerous, unless the API user (downstream developer)
- * knows, that the parameter value is safe (for example, because it
- * is hard coded, or because it has been compared to a white list of
- * permissible values).
- */
-@Retention(RetentionPolicy.RUNTIME)
-@Target({ElementType.CONSTRUCTOR, ElementType.METHOD})
-@Documented
-public @interface Insecure {
-}
diff --git a/src/main/java/org/apache/commons/lang3/annotations/Safe.java
b/src/main/java/org/apache/commons/lang3/annotations/Safe.java
deleted file mode 100644
index c3a710cf2..0
--- a/src/main/java/org/apache/commons/lang3/annotations/Safe.java
+++ /dev/null
@@ -1,61 +0,0 @@
-/*
- * Licensed to the Apache Software Foundation (ASF) under one or more
- * contributor license agreements. See the NOTICE file distributed with
- * this work for additional information regarding copyright ownership.
- * The ASF licenses this file to You under the Apache License, Version 2.0
- * (the "License"); you may not use this file except in compliance with
- * the License. You may obtain a copy of the License at
- *
- * http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-package org.apache.commons.lang3.annotations;
-
-import java.lang.annotation.Documented;
-import java.lang.annotation.ElementType;
-import java.lang.annotation.Retention;
-import java.lang.annotation.RetentionPolicy;
-import java.lang.annotation.Targ
Bug#1065973: kmod: FTBFS due to time64 transition
Hi Marco, last week you offered in #debian-devel to upload kmod with tests disabled for 32 bit arm to work around the current situation. Could you please do that? Cheers Jochen * Simon McVittie [2024-03-21 12:23]: On Thu, 21 Mar 2024 at 15:45:13 +0500, Andrey Rakhmatullin wrote: On Wed, Mar 13, 2024 at 08:23:07AM +0100, Helge Deller wrote: > The patch below builds for me on the hppa platform. Unfortunately tests fail here with it in an armhf chroot, I don't know if it's generic or because the chroot is a qemu-based one on amd64. I think the root cause (both for needing to unset _FILE_OFFSET_BITS, and for the tests failing) is that kmod's test suite is interposing mock/wrapped versions of the stat() family. With the transition to 64-bit time_t, there are new members of the stat() family that will also need interposing on 32-bit architectures: __lstat64_time64() is the replacement for lstat(), and __stat64_time64() for stat(). There are also __fstat64_time64() and __fstatat64_time64(), but kmod doesn't seem to interpose fstat() or fstatat(), so those are probably unnecessary in this case. fakeroot, fakechroot and other LD_PRELOAD modules that interpose stat() will already be doing something similar, and might provide a useful reference for what is needed. Here's the equivalent in fakechroot: https://github.com/dex4er/fakechroot/pull/104/commits/dac74cd68cfb6eeaae9cd13bdc48737a44980df9 smcv signature.asc Description: PGP signature
Bug#1065973: kmod: FTBFS due to time64 transition
Hi Marco, last week you offered in #debian-devel to upload kmod with tests disabled for 32 bit arm to work around the current situation. Could you please do that? Cheers Jochen * Simon McVittie [2024-03-21 12:23]: On Thu, 21 Mar 2024 at 15:45:13 +0500, Andrey Rakhmatullin wrote: On Wed, Mar 13, 2024 at 08:23:07AM +0100, Helge Deller wrote: > The patch below builds for me on the hppa platform. Unfortunately tests fail here with it in an armhf chroot, I don't know if it's generic or because the chroot is a qemu-based one on amd64. I think the root cause (both for needing to unset _FILE_OFFSET_BITS, and for the tests failing) is that kmod's test suite is interposing mock/wrapped versions of the stat() family. With the transition to 64-bit time_t, there are new members of the stat() family that will also need interposing on 32-bit architectures: __lstat64_time64() is the replacement for lstat(), and __stat64_time64() for stat(). There are also __fstat64_time64() and __fstatat64_time64(), but kmod doesn't seem to interpose fstat() or fstatat(), so those are probably unnecessary in this case. fakeroot, fakechroot and other LD_PRELOAD modules that interpose stat() will already be doing something similar, and might provide a useful reference for what is needed. Here's the equivalent in fakechroot: https://github.com/dex4er/fakechroot/pull/104/commits/dac74cd68cfb6eeaae9cd13bdc48737a44980df9 smcv signature.asc Description: PGP signature
Bug#1069904: Autopkgtests failed
Hi Elena, I have opened a MR to fix this: https://salsa.debian.org/python-team/packages/python-gnupg/-/merge_requests/1 Due to #1071561 I will not do more but it would be great if we could get this fixed. Cheers Jochen * Andrey Rakhmatullin [2024-04-27 00:32]: Package: python3-gnupg Version: 0.5.2-1 Severity: serious https://ci.debian.net/packages/p/python-gnupg/unstable/amd64/45884087/ 277s + python3.11 test_gnupg.py 493s ...F... 493s == 493s FAIL: test_search_keys (__main__.GPGTestCase.test_search_keys) 493s Test that searching for keys works 493s -- 493s Traceback (most recent call last): 493s File "/tmp/autopkgtest- lxc.s9943af9/downtmp/build.Ev1/src/test_gnupg.py", line 1252, in test_search_keys 493s self.assertEqual(0, r.returncode, 'Non-zero return code') 493s AssertionError: 0 != 2 : Non-zero return code -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-gnupg depends on: ii gnupg2.2.40-3 ii python3 3.11.8-1 python3-gnupg recommends no packages. python3-gnupg suggests no packages. signature.asc Description: PGP signature
Bug#1069904: Autopkgtests failed
Hi Elena, I have opened a MR to fix this: https://salsa.debian.org/python-team/packages/python-gnupg/-/merge_requests/1 Due to #1071561 I will not do more but it would be great if we could get this fixed. Cheers Jochen * Andrey Rakhmatullin [2024-04-27 00:32]: Package: python3-gnupg Version: 0.5.2-1 Severity: serious https://ci.debian.net/packages/p/python-gnupg/unstable/amd64/45884087/ 277s + python3.11 test_gnupg.py 493s ...F... 493s == 493s FAIL: test_search_keys (__main__.GPGTestCase.test_search_keys) 493s Test that searching for keys works 493s -- 493s Traceback (most recent call last): 493s File "/tmp/autopkgtest- lxc.s9943af9/downtmp/build.Ev1/src/test_gnupg.py", line 1252, in test_search_keys 493s self.assertEqual(0, r.returncode, 'Non-zero return code') 493s AssertionError: 0 != 2 : Non-zero return code -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-gnupg depends on: ii gnupg2.2.40-3 ii python3 3.11.8-1 python3-gnupg recommends no packages. python3-gnupg suggests no packages. signature.asc Description: PGP signature
Bug#1069904: marked as pending in python-gnupg
Control: tag -1 pending Hello, Bug #1069904 in python-gnupg reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-gnupg/-/commit/ed1d9477c00fea5e11c365cb66a6a9992bd712ab Switch to autopkgtest-pkg-pybuild Helmut confirmed that the gpg workaround for #682648 is no longer needed. Closes: #1069904 (this message was generated automatically) -- Greetings https://bugs.debian.org/1069904
[Puppet Users] Apache with HTTP2 and PHP setup using puppet
Hi, I would like to update my apache-php servers with http2 but am facing several difficulties. It seems like apache must be multithreaded for http2 and a multithreaded apache does not work with mod-php. I have the feeling I will need something like php-fpm from now on and it seems like this cannot be configured using puppet::apache alone. Looks like there are quite to many changes to cope with. I am looking for some examples to setup a sane Debian setup with apache and http2 and PHP using puppet. Can anyone share a link or two please? Thanks, best Jochen -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/c979c2f3-8a4e-48ee-b966-a9c391fedeabn%40googlegroups.com.
[jira] [Commented] (IO-783) Fetching file extension using FilenameUtils.getExtension method throws error in windows machine
[
https://issues.apache.org/jira/browse/IO-783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847634#comment-17847634
]
Jochen Wiedmann commented on IO-783:
I would like to point out, that the check, as it is, is broken anyways. For
example c:\\file.txt is certainly a valid file name on Windows.
> Fetching file extension using FilenameUtils.getExtension method throws error
> in windows machine
> ---
>
> Key: IO-783
> URL: https://issues.apache.org/jira/browse/IO-783
> Project: Commons IO
> Issue Type: Bug
> Components: Utilities
>Affects Versions: 2.7, 2.8.0, 2.9.0, 2.10.0, 2.11.0
> Environment: Run the below line of code in windows environment.
> String fileName = FilenameUtils.getExtension("Top of Information
> Store\\Archive\\Informational-severity alert: eDiscovery search started or
> exported.msg");
> System.out.println(fileName);
>
> We are getting the error,
> Exception in thread "main" java.lang.IllegalArgumentException: NTFS ADS
> separator (':') in file name is forbidden.
> at
> org.apache.commons.io.FilenameUtils.indexOfExtension(FilenameUtils.java:737)
> at
> org.apache.commons.io.FilenameUtils.getExtension(FilenameUtils.java:1057)
>Reporter: Samraj
>Priority: Major
>
> Hi Team,
> I am using FilenameUtils.getExtension method to get the file extension from
> the file path ( Available as string). Due to one of the bug fix happen after
> 2.7 breaks the code.
> Run the below line of code in windows environment.
> String fileName = FilenameUtils.getExtension("Top of Information
> Store\\Archive
> Informational-severity alert: eDiscovery search started or exported.msg");
> System.out.println(fileName);
>
> We are getting the error,
> Exception in thread "main" java.lang.IllegalArgumentException: NTFS ADS
> separator (':') in file name is forbidden.
> at
> org.apache.commons.io.FilenameUtils.indexOfExtension(FilenameUtils.java:737)
> at
> org.apache.commons.io.FilenameUtils.getExtension(FilenameUtils.java:1057)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (IO-830) Rethink AbstractOrigin
[ https://issues.apache.org/jira/browse/IO-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847387#comment-17847387 ] Jochen Wiedmann commented on IO-830: [~elharo] While I agree with you, in general (for example, I'd like to see a distinction between an origin, that is based on a byte stream, and an origin, that is based on a character stream), I don't see any real pain. The mere fact, that an UnsupportedOperationException is being used, is (in my opinion) not enough reason to implement changes. In particular, as far as I can tell, the UOE isn't actually thrown, but just declared in the Javadocs. > Rethink AbstractOrigin > -- > > Key: IO-830 > URL: https://issues.apache.org/jira/browse/IO-830 > Project: Commons IO > Issue Type: Bug >Reporter: Elliotte Rusty Harold >Priority: Critical > > UnuspportedOperationException is a code smell that indicates the class > hierarchy doesn't really fit the problem and violates the Liskov Subsitution > Principle > See > https://softwareengineering.stackexchange.com/questions/337850/is-expecting-the-api-user-to-implement-an-unsupportedoperationexception-okay > It doesn't work to treat all origins the same. E.g. CharSequences really, > really need a character set before they can be converted to byte arrays or > input streams, but byte arrays and files don't. In reverse files need a > character set to be converted to a reader but char sequences don't. > Different classes need different arguments, whether you use a builder or a > constructor. There's not common type here. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (IO-833) Every origin needs a charset
[
https://issues.apache.org/jira/browse/IO-833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17847382#comment-17847382
]
Jochen Wiedmann commented on IO-833:
[~elharo] As far as I can tell, the implementation does use a Charset:
{{ {color:#5a5a5a}{color:#7f0055}private{color}{color:#00} Charset
{color}{color:#c0}charset{color}{color:#00} =
Charset.{color}{color:#00}defaultCharset{color}{color:#00}();{color}{color}}}
I admit, that the choice of Charset is questionable, I'd have recommended
UTF_8, but that can't be changed without loosing compatibility.
> Every origin needs a charset
>
>
> Key: IO-833
> URL: https://issues.apache.org/jira/browse/IO-833
> Project: Commons IO
> Issue Type: Bug
>Reporter: Elliotte Rusty Harold
>Priority: Critical
>
> Every origin except possibly URIOrigin needs a charset. There is no reliable,
> acceptable way to convert bytes to chars (ByteOrigin, PathOrigin) or chars to
> bytes (CharSequenceOrigin) without it.
> The only possible exception is URIOrigin which can have enough metadata to
> usefully deduce the charset.
> Methods like getBytes and getReader should throw an IllegalStateException if
> charset is needed and not supplied.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [Openvpn-users] TLS key negotiation failed to occur ISP screws up the VPN
On 17.05.24 15:49, shadowbladeee via Openvpn-users wrote: Time is correct on the machines, certs expire in 2049. Any *CRLs* that might have expired? I note that the tcpdump shows only quite *small* packets. MTU issues that could lead to (persistent) loss of large ones from the other end? Kind regards, -- Jochen Bern Systemingenieur Binect GmbH smime.p7s Description: S/MIME Cryptographic Signature ___ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
(commons-lang) branch master updated: Minor documentation fixes.
This is an automated email from the ASF dual-hosted git repository.
jochen pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-lang.git
The following commit(s) were added to refs/heads/master by this push:
new 797f9a4f5 Minor documentation fixes.
797f9a4f5 is described below
commit 797f9a4f5d8746a8c2c5dc28c422176ead897516
Author: Jochen Wiedmann
AuthorDate: Fri May 17 01:02:06 2024 +0200
Minor documentation fixes.
---
src/main/java/org/apache/commons/lang3/annotations/Safe.java | 2 +-
src/main/java/org/apache/commons/lang3/annotations/package-info.java | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/main/java/org/apache/commons/lang3/annotations/Safe.java
b/src/main/java/org/apache/commons/lang3/annotations/Safe.java
index 4b5212c71..c3a710cf2 100644
--- a/src/main/java/org/apache/commons/lang3/annotations/Safe.java
+++ b/src/main/java/org/apache/commons/lang3/annotations/Safe.java
@@ -26,7 +26,7 @@ import java.lang.annotation.Target;
* This annotation is used to indicate, that a variable, field, or parameter
* contains a safe value. If so, the annotated element may be used in an
* invocation of a constructor, or method, which is annotated with
- * {@code @Trusted}.
+ * {@code @Insecure}.
*
* For example, suggest the following method declaration:
*
diff --git
a/src/main/java/org/apache/commons/lang3/annotations/package-info.java
b/src/main/java/org/apache/commons/lang3/annotations/package-info.java
index 43d54d606..720d61069 100644
--- a/src/main/java/org/apache/commons/lang3/annotations/package-info.java
+++ b/src/main/java/org/apache/commons/lang3/annotations/package-info.java
@@ -30,7 +30,7 @@
* By annotating a variable with {@code @Safe}, the API user
* declares, that the variable contains trusted input, that can be
* used as a parameter in an invocation of a constructor, or method,
- * that is annotated with {@code @Trusted}.
+ * that is annotated with {@code @Insecure}.
*
* @since 3.15
*/
(commons-lang) branch master updated: Adding the @Insecure, and @Safe annotations.
This is an automated email from the ASF dual-hosted git repository.
jochen pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/commons-lang.git
The following commit(s) were added to refs/heads/master by this push:
new 3322d9748 Adding the @Insecure, and @Safe annotations.
3322d9748 is described below
commit 3322d974876b8d4f934d3544967103ebbcaef726
Author: Jochen Wiedmann
AuthorDate: Fri May 17 00:28:39 2024 +0200
Adding the @Insecure, and @Safe annotations.
---
src/changes/changes.xml| 1 +
.../apache/commons/lang3/annotations/Insecure.java | 48
.../org/apache/commons/lang3/annotations/Safe.java | 61 +++
.../commons/lang3/annotations/package-info.java| 37 +++
.../commons/lang3/annotations/AnnotationsTest.java | 122 +
5 files changed, 269 insertions(+)
diff --git a/src/changes/changes.xml b/src/changes/changes.xml
index 34841687a..b69e1f8a2 100644
--- a/src/changes/changes.xml
+++ b/src/changes/changes.xml
@@ -140,6 +140,7 @@ The type attribute can be add,update,fix,remove.
Bump org.apache.commons:commons-text from 1.11.0 to 1.12.0
#1200.
Drop obsolete JDK 13 Maven profile #1142.
+Added the annotations
package, including the Insecure, and Safe annotations.
diff --git a/src/main/java/org/apache/commons/lang3/annotations/Insecure.java
b/src/main/java/org/apache/commons/lang3/annotations/Insecure.java
new file mode 100644
index 0..2802f1189
--- /dev/null
+++ b/src/main/java/org/apache/commons/lang3/annotations/Insecure.java
@@ -0,0 +1,48 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.commons.lang3.annotations;
+
+import java.lang.annotation.Documented;
+import java.lang.annotation.ElementType;
+import java.lang.annotation.Retention;
+import java.lang.annotation.RetentionPolicy;
+import java.lang.annotation.Target;
+
+/**
+ * This annotation is used to indicate, that a constructor, or method
+ * is insecure to use, unless the input parameters contain safe ("trusted")
+ * values.
+ *
+ * For example, consider a method like
+ * {@literal @Insecure}
+ * public void runCommand(String pCmdLine) {
+ * }
+ *
+ *
+ * The example method would invoke {@code /bin/sh} (Linux, Unix, or MacOS), or
+ * {@code cmd} (Windows) to run an external command, as given by the parameter
+ * {@code pCmdLine}. Obviously, depending on the value of the parameter,
+ * this can be dangerous, unless the API user (downstream developer)
+ * knows, that the parameter value is safe (for example, because it
+ * is hard coded, or because it has been compared to a white list of
+ * permissible values).
+ */
+@Retention(RetentionPolicy.RUNTIME)
+@Target({ElementType.CONSTRUCTOR, ElementType.METHOD})
+@Documented
+public @interface Insecure {
+}
diff --git a/src/main/java/org/apache/commons/lang3/annotations/Safe.java
b/src/main/java/org/apache/commons/lang3/annotations/Safe.java
new file mode 100644
index 0..4b5212c71
--- /dev/null
+++ b/src/main/java/org/apache/commons/lang3/annotations/Safe.java
@@ -0,0 +1,61 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.commons.lang3.annotations;
+
+import java.lang.annotation.Documented;
+import java.lang.annotation.ElementType;
+import java.lang.annotation.Retention;
+import java.lang.annotation.Re
[go-nuts] replacement for filepath.HasPrefix?
Dear all, filepath.HasPrefix is deprecated, because it doesn't alway work. What would be a replacement for this function, which at least respects path boundaries, and maybe also ignores case when needed? All the best, Jochen -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/4cca691c-ab0a-4081-9e60-2fa0b2155f62n%40googlegroups.com.
Bug#1071190: golang-github-shirou-gopsutil fails to build with no physical disks present
Source: golang-github-shirou-gopsutil Version: 3.24.1-1 Severity: normal X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org Control: affects -1 buildd.debian.org Hi, golang-github-shirou-gopsutil fails to build when there are no physical drives mounted: === RUN TestDisk_partitions disk_test.go:38: error disk_test.go:40: [] disk_test.go:43: ret is empty --- FAIL: TestDisk_partitions (0.00s) This happens for example in the sbuild unshare backend. Cheers Jochen
[Bug 2037302] Re: ros-robot and ros-simulators-dev missing related packages
apt show ros-robot gives: Description: Python Robot OS robot metapackage This package is part of Robot OS (ROS). It is a metapackage which provides all the ROS robot system (including ROS base). . Different to upstream, this package does not provide: control_msgs, executive_smach, filters, xacro. Please install them from source, if you need them. So it clearly describes the situation. What do you mean by packaging errors? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2037302 Title: ros-robot and ros-simulators-dev missing related packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ros-metapackages/+bug/2037302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Groovy Poster for Community Over Code EU
I like it On 14.05.24 13:47, Paul King wrote: Hi folks, We have a poster that will be displayed at Community Over Code EU in Bratislava in a few weeks. Here is my current draft: https://github.com/apache/apachecon-eu/blob/main/static/posters/CoCEU_WhyGroovyToday.pdf There is a small window to make changes before they send the posters off to the printers. It will be printed I think on A1 size paper, about 594mm W x 841mm H (23.4 x 33.1 inches). At the moment, it is rich in technical content - perhaps a little light in marketing the benefits. If I was to make changes I'd prefer to maybe reduce the first slightly and increase the latter. Let me know if you have any feedback. Thanks, Paul.
Re: weird error report
On 13.05.24 16:16, o...@ocs.cz wrote:
[...]
2074 ocs /tmp> /usr/local/groovy-4.0.18/bin/groovy q
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
/private/tmp/q.groovy: 1: Unexpected input: '{' @ line 1, column 32.
def all=['hi','there'].findAll { it.startsWith('h')) }
^
1 error
2076 ocs /tmp>
===
I assume the problem is the )) for the startsWith. The parser backtracks
because there is no opening ( for the closing one and then finds that {
can't be a valid input here.
Could you please make an issue for this? We should look into how we can
improve this
bye Jochen
[go-nuts] tls.VerifyClientCertIfGiven
Hello, In a server I use tls.Config.ClientAuth=tls.VerifyClientCertIfGiven. If then a client manages to connect and I can see a certificate in http.Request.TLS.PeerCertificates, does this just mean that the client has the certificate, or does this also prove that the client has the associated private key? Many thanks, Jochen -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/7003fa55-2436-4b85-a5ab-eed2d54430d0n%40googlegroups.com.
[Bug 2046047] Re: No aptX support
Thanks for the reply, the actual problem is that it must be --with- libopenaptx not --enable-libopenaptx as currently in the package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046047 Title: No aptX support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez-alsa/+bug/2046047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[FRIAM] The Rise of the Maya Civilization
Takeshi Inomata from the University of Arizona does interesting work on the rise of the Maya civilization:Monumental architecture at Aguada Fenix and the rise of Maya civilization, Nature 582 (2020) 530-533https://pasolibre.grecu.mx/wp-content/uploads/2020/07/41586_2020_2343_opt.pdf-J.-. --- - / ...- .- .-.. .. -.. / -- --- .-. ... . / -.-. --- -.. . FRIAM Applied Complexity Group listserv Fridays 9a-12p Friday St. Johns Cafe / Thursdays 9a-12p Zoom https://bit.ly/virtualfriam to (un)subscribe http://redfish.com/mailman/listinfo/friam_redfish.com FRIAM-COMIC http://friam-comic.blogspot.com/ archives: 5/2017 thru present https://redfish.com/pipermail/friam_redfish.com/ 1/2003 thru 6/2021 http://friam.383.s1.nabble.com/
[ClusterLabs] Mixing globally-unique with non-globally-unique resources
I have the following use case: There are several cluster IP addresses in the cluster. Each address is different, and multiple addresses can be scheduled on the same node. This makes the address clone a globally-unique clone as far as I understood. Then I have one service per node which manages traffic for all addresses on a node where an address is active, which makes the service clone not-globally-unique. The service should only run if at least one address is active on the node, and there cannot be more than one instance of the service on each node. How would I create this pattern in Pacemaker? ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
[Bug 2046047] Re: No aptX support
From my understanding --enable-aptx and --enable-aptx-hd depend on https://github.com/Arkq/openaptx which states in the readme: This project is for research purposes only. Without a proper license private and commercial usage might be a case of a patent infringement. So we can't distribute it in Debian or depend on it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2046047 Title: No aptX support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez-alsa/+bug/2046047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [DISCUSS] RAT tickets
On Sat, May 11, 2024 at 9:45 AM Claude Warren wrote: > > I think that we should do the following: ... > create a licenses section in the configuration. > > --licenses : a list of files to be read as license files. > --licenses-approved : a list of license IDs to approve. > --licenses-approved-file : A file containing license IDs to approve. > --licenses-no-default : An enumeration of DEF (do not load license > definitions), APPROVAL (do not load default license approvals) Not exactly sure, what you refer to as "the configuration". However, I'd like to expand on your idea by proposing that we ought to have not only "license files" in the source tree (or external from the source tree in another shared location ), but also a configuration file, which controls Rat in the absence of command line options / Maven properties / Ant arguments. Basically, by simply invoking Rat, the configuration would be specified by the configuration file only. The purpose of command line options / Maven properties / Ant arguments would be to overrule the configuration file. Jochen
Re: Replacing GrapeIvy
On 03.05.24 00:28, Paul King wrote: Hi folks, One of the things we know is that Apache Ivy (used by Grab/grapes) is being maintained less these days. I am going to start a spike to better understand what a replacement using Apache Maven Resolver might look like. If anyone has strong opinions or free cycles and wants to help, let me know and you can join in the fun. Otherwise, I'll create future issues(s)/PR(s) for folks to look at in due course assuming all goes well. I'd love to help, but I have currently no spare cycles, sorry. I was wondering... hos does @GrabConfig(systemClassLoader=true) work these days? From my knowledge this cannot work anymore in later JDK versions (9+) because of the changes to the system class loader. Or did we somehow bypass the limitation? I personally use these in script files only. There is a potential class loader suitable to do such work, but it is still not the system class loader. If something really would need that, it would be having no chance of working. I hear really really little for such a nice feature having a problem. So maybe it does not matter in reality? bye Jochen
Bug#1070952: ros-vcstools: FTBFS in bullseye
Hi Santiago, thanks for the report. This seems to be due to git 1:2.30.2-1+deb11u1 as it works with the version before (1:2.30.2-1). Give that it is a security fix and a testing only problem that could worked around easily, I would leave this as is. Cheers Jochen * Santiago Vila [2024-05-11 21:53]: Package: src:ros-vcstools Version: 0.1.42-3 Severity: serious Control: close -1 0.1.42-7 Tags: ftbfs bullseye Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary dh binary --with python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:232: python3.9 setup.py config /<>/setup.py:3: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import imp running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:232: /usr/bin/python3 setup.py build /<>/setup.py:3: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import imp [... snipped ...] 6 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_checkout_into_subdir_without_existing_parent (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_checkout_specific_version_and_update (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved 0 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 0 files updated, 0 files merged, 2 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 2 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 0 files updated, 0 files merged, 2 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 2 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_current_version_label (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved 0 files updated, 0 files merged, 5 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 5 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 1 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_environment_metadata (test.test_hg.HGClientTest) ... ok test_get_remote_version (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved abort: destination '/tmp/tmp18ac112f/local' is not empty pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 0 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 1 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_type_name (test.test_hg.HGClientTest) ... ok test_get_url_by_reading (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved 0 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_url_nonexistant (test.test_hg.HGClientTest) ... ok marked working directory as branch test_branch (branches are permanent and global, did you want a bookmark?) updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved testStatusUntracked (test.test_hg.HGDiffStatClientTest) ... ok test_diff (test.test_hg.HGDiffStatClientTest) ... ok test_diff_relpath (test.test_hg.HGDiffStatClientTest) ... ok test_get_version_modified (test.test_hg.HGDiffStatClientTest) ... ok test_hg_diff_path_change_None (test.test_hg.HGDiffStatClientTest) ... ok test_status (test.test_hg.HGDiffStatClientTest) ... ok test_status_relpath (test.test_hg.HGDiffStatClientTest) ... ok marked working directory as branch test_branch (branches are permanent and global, did you want a bookmark?) updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved test_export_repository (test.test_hg.HGExportRepositoryClientTest) ... ok marked working directory as branch test_branch (branches are permanent and global, did you want a bookmark?) updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved test_get_branches (test.test_hg.HGGetBranchesClientTest) ...
Bug#1070952: ros-vcstools: FTBFS in bullseye
Hi Santiago, thanks for the report. This seems to be due to git 1:2.30.2-1+deb11u1 as it works with the version before (1:2.30.2-1). Give that it is a security fix and a testing only problem that could worked around easily, I would leave this as is. Cheers Jochen * Santiago Vila [2024-05-11 21:53]: Package: src:ros-vcstools Version: 0.1.42-3 Severity: serious Control: close -1 0.1.42-7 Tags: ftbfs bullseye Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary dh binary --with python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:232: python3.9 setup.py config /<>/setup.py:3: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import imp running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:232: /usr/bin/python3 setup.py build /<>/setup.py:3: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import imp [... snipped ...] 6 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_checkout_into_subdir_without_existing_parent (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_checkout_specific_version_and_update (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved 0 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 0 files updated, 0 files merged, 2 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 2 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 0 files updated, 0 files merged, 2 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 2 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_current_version_label (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved 0 files updated, 0 files merged, 5 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 5 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 1 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_environment_metadata (test.test_hg.HGClientTest) ... ok test_get_remote_version (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved abort: destination '/tmp/tmp18ac112f/local' is not empty pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 0 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 1 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_type_name (test.test_hg.HGClientTest) ... ok test_get_url_by_reading (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved 0 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_url_nonexistant (test.test_hg.HGClientTest) ... ok marked working directory as branch test_branch (branches are permanent and global, did you want a bookmark?) updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved testStatusUntracked (test.test_hg.HGDiffStatClientTest) ... ok test_diff (test.test_hg.HGDiffStatClientTest) ... ok test_diff_relpath (test.test_hg.HGDiffStatClientTest) ... ok test_get_version_modified (test.test_hg.HGDiffStatClientTest) ... ok test_hg_diff_path_change_None (test.test_hg.HGDiffStatClientTest) ... ok test_status (test.test_hg.HGDiffStatClientTest) ... ok test_status_relpath (test.test_hg.HGDiffStatClientTest) ... ok marked working directory as branch test_branch (branches are permanent and global, did you want a bookmark?) updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved test_export_repository (test.test_hg.HGExportRepositoryClientTest) ... ok marked working directory as branch test_branch (branches are permanent and global, did you want a bookmark?) updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved test_get_branches (test.test_hg.HGGetBranchesClientTest) ...
Bug#1070952: ros-vcstools: FTBFS in bullseye
Hi Santiago, thanks for the report. This seems to be due to git 1:2.30.2-1+deb11u1 as it works with the version before (1:2.30.2-1). Give that it is a security fix and a testing only problem that could worked around easily, I would leave this as is. Cheers Jochen * Santiago Vila [2024-05-11 21:53]: Package: src:ros-vcstools Version: 0.1.42-3 Severity: serious Control: close -1 0.1.42-7 Tags: ftbfs bullseye Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules binary dh binary --with python3 --buildsystem=pybuild dh_update_autotools_config -O--buildsystem=pybuild dh_autoreconf -O--buildsystem=pybuild dh_auto_configure -O--buildsystem=pybuild I: pybuild base:232: python3.9 setup.py config /<>/setup.py:3: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import imp running config dh_auto_build -O--buildsystem=pybuild I: pybuild base:232: /usr/bin/python3 setup.py build /<>/setup.py:3: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import imp [... snipped ...] 6 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_checkout_into_subdir_without_existing_parent (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_checkout_specific_version_and_update (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved 0 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 0 files updated, 0 files merged, 2 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 2 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 0 files updated, 0 files merged, 2 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 2 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_current_version_label (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved 0 files updated, 0 files merged, 5 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 5 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 1 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_environment_metadata (test.test_hg.HGClientTest) ... ok test_get_remote_version (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved abort: destination '/tmp/tmp18ac112f/local' is not empty pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 0 files updated, 0 files merged, 0 files removed, 0 files unresolved pulling from /tmp/tmp18ac112f/remote searching for changes no changes found 1 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_type_name (test.test_hg.HGClientTest) ... ok test_get_url_by_reading (test.test_hg.HGClientTest) ... updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved 0 files updated, 0 files merged, 0 files removed, 0 files unresolved ok test_get_url_nonexistant (test.test_hg.HGClientTest) ... ok marked working directory as branch test_branch (branches are permanent and global, did you want a bookmark?) updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved testStatusUntracked (test.test_hg.HGDiffStatClientTest) ... ok test_diff (test.test_hg.HGDiffStatClientTest) ... ok test_diff_relpath (test.test_hg.HGDiffStatClientTest) ... ok test_get_version_modified (test.test_hg.HGDiffStatClientTest) ... ok test_hg_diff_path_change_None (test.test_hg.HGDiffStatClientTest) ... ok test_status (test.test_hg.HGDiffStatClientTest) ... ok test_status_relpath (test.test_hg.HGDiffStatClientTest) ... ok marked working directory as branch test_branch (branches are permanent and global, did you want a bookmark?) updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved test_export_repository (test.test_hg.HGExportRepositoryClientTest) ... ok marked working directory as branch test_branch (branches are permanent and global, did you want a bookmark?) updating to branch default 6 files updated, 0 files merged, 0 files removed, 0 files unresolved test_get_branches (test.test_hg.HGGetBranchesClientTest) ...
Bug#1070973: Please add a include_optional to /etc/mpd.conf
Package: mpd Version: 0.23.14-2+b2 Severity: wishlist Tags: patch Hi, can you please add a include_optional to simplify local modifications? Something like this should do: echo 'include_optional "mpd_local.conf"' >> debian/mpd.conf Thanks! Jochen
[Qt-creator] Unclear requirement in setting "Skip clean whitespace for file types"
Hi, I wondered why "Skip clean whitespace for file types" does not work: If I edit a makefile named "Makefile" the tabs are still translated to spaces on save. There seems to be some unclear requirements here: the label of the checkbox is "Skip clean whitespace for file types" but the implementation names this checkbox "skipTrailingWhitespace" and this is really the implemented functionality. I would like to fix that. Renaming the label to "Skip removing trailing whitespaces for file types" doesn't make much sense to me. I would prefer renaming the checkbox to "skipCleanupWhitespaceForFileTypes" and implement it that way. I could also add another checkbox "skipTrailingWhitespace" with that label but no text edit box for specific file types. On the long term, most of the TextEditor settings should be mappable to user selectable file types. What do you think? -- Qt-creator mailing list Qt-creator@qt-project.org https://lists.qt-project.org/listinfo/qt-creator
Bug#1070332: Wont fix
Hi Thomas, * Thomas Goirand [2024-05-06 08:21]: I already explained this: I am *NOT* interested in addressing this type of failure. Designate is "OpenStack DNS as a Service", therefore, it is expected that it's going to check/use /etc/resolv.conf. If you carefully look at what's going on, you'll see that it's not even doing DNS queries to the outside, it's simply testing itself. Removing the test would mean less Q/A, which is not desirable. "Fixing" the test would mean more work, which isn't needed in this case (the package works perfectly). Feel free to bug upstream and resolve it there if you think that's valuable, though I am of the opinion it's a loss of time. Also, note that the package builds perfectly fine in the current buildd environment (and on my laptop's sbuild setup). If that was going to change, of course, I'd review my opinion. In the mean time, I see no point in this bug. Fix your build env... Note that the buildds started switching to the unshare backend so the package will FTBFS soon. Cheers Jochen signature.asc Description: PGP signature
Bug#1070436: autopkgtest-virt-schroot: error when using 'unshare --net' even though schroot allows this
Hi Richard, * Richard Lewis [2024-05-05 11:32]: If i try and run tests that use 'unshare --net' with a schroot backend they fail inside autopkgtest even though this works in the schroot being used. This works fine in a 'plain schroot' (I expect i allowed the calling user to run the schroot as root in the schroot in /etc/schroot): $ schroot --chroot chroot:unstable-amd64-sbuild --directory / --user root -- unshare --net --map-root-user ls bin boot build dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var I can't reproduce this. Testing in a fresh debvm: $ debvm-create --size=2G --release=stable -- \ --include=sbuild,schroot,debootstrap,autopkgtest \ --hook-dir=/usr/share/mmdebstrap/hooks/useradd $ debvm-run # echo "inside debvm" # sbuild-createchroot unstable /srv/chroot/unstable-amd64-sbuild \ http://deb.debian.org/debian # sbuild-adduser user # su - user $ schroot --chroot chroot:unstable-amd64-sbuild --directory / --user root -- unshare --net --map-root-user ls unshare: unshare failed: Operation not permitted Do you have any idea why it works for you? But if i have an autopkgtest with eg a debian/tests/control with Test-Command: unshare --map-root-user --net ./debian/tests/foo Depends: @ Features: test-name=foo Restrictions: needs-root This looks odd. If you only want to unshare the network, as stated in the bug title, you neither need --map-root-user nor needs-root. Indeed dropping both makes it work for me. Can you give some background what you actually want to do here? then even adding '--user root' doesnt work: $ /usr/bin/autopkgtest package.changes --user root -- schroot unstable-amd64-sbuild I guess this is due to autopkgtest-virt-schroot starts an schroot session but I can't verify without reproducing your example without a session. i get errors like unshare: unshare failed: Operation not permitted This maps to unshare(2) returning EPERM. From the manpage: | CLONE_NEWUSER was specified in flags and the caller is in a chroot | environment (i.e., the caller's root directory does not match the root | directory of the mount namespace in which it resides). I think this is what happens here. Over all I think using unshare --map-root-user in autopkgtest-virt-schroot is not supported and I don't think there is a way around that except using a different autopkgtest backend. Cheers Jochen signature.asc Description: PGP signature
Bug#1070415: runc fails to build as a normal user due to cgroups access
Source: runc
Version: 1.1.12+ds1-2
Severity: important
X-Debbugs-Cc: debian-wb-team@lists.debian.org
Usertags: unshare
Hi,
runc tries to write cgroups files during the build which fails as a
normal user:
=== RUN TestDevicesSetAllow
--- FAIL: TestDevicesSetAllow (0.00s)
panic: runtime error: index out of range [0] with length 0 [recovered]
panic: runtime error: index out of range [0] with length 0
goroutine 63 [running]:
testing.tRunner.func1.2({0x5e12c0, 0xc0001ed2c0})
/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({0x5e12c0?, 0xc0001ed2c0?})
/usr/lib/go-1.22/src/runtime/panic.go:770 +0x132
github.com/opencontainers/runc/libcontainer/cgroups/fs.TestDevicesSetAllow(0xc0001fcd00)
/<>/_build/src/github.com/opencontainers/runc/libcontainer/cgroups/fs/devices_test.go:42
+0x45e
testing.tRunner(0xc0001fcd00, 0x607748)
/usr/lib/go-1.22/src/testing/testing.go:1689 +0xfb
created by testing.(*T).Run in goroutine 1
/usr/lib/go-1.22/src/testing/testing.go:1742 +0x390
FAILgithub.com/opencontainers/runc/libcontainer/cgroups/fs 0.044s
https://salsa.debian.org/go-team/packages/runc/-/blob/debian/1.1.5+ds1-1/libcontainer/cgroups/fs/devices_test.go?ref_type=tags#L42
This also fails with the sbuild unshare backend.
Cheers Jochen
Bug#1070415: runc fails to build as a normal user due to cgroups access
Source: runc
Version: 1.1.12+ds1-2
Severity: important
X-Debbugs-Cc: debian-wb-t...@lists.debian.org
Usertags: unshare
Hi,
runc tries to write cgroups files during the build which fails as a
normal user:
=== RUN TestDevicesSetAllow
--- FAIL: TestDevicesSetAllow (0.00s)
panic: runtime error: index out of range [0] with length 0 [recovered]
panic: runtime error: index out of range [0] with length 0
goroutine 63 [running]:
testing.tRunner.func1.2({0x5e12c0, 0xc0001ed2c0})
/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({0x5e12c0?, 0xc0001ed2c0?})
/usr/lib/go-1.22/src/runtime/panic.go:770 +0x132
github.com/opencontainers/runc/libcontainer/cgroups/fs.TestDevicesSetAllow(0xc0001fcd00)
/<>/_build/src/github.com/opencontainers/runc/libcontainer/cgroups/fs/devices_test.go:42
+0x45e
testing.tRunner(0xc0001fcd00, 0x607748)
/usr/lib/go-1.22/src/testing/testing.go:1689 +0xfb
created by testing.(*T).Run in goroutine 1
/usr/lib/go-1.22/src/testing/testing.go:1742 +0x390
FAILgithub.com/opencontainers/runc/libcontainer/cgroups/fs 0.044s
https://salsa.debian.org/go-team/packages/runc/-/blob/debian/1.1.5+ds1-1/libcontainer/cgroups/fs/devices_test.go?ref_type=tags#L42
This also fails with the sbuild unshare backend.
Cheers Jochen
Bug#1070414: fails to build when not build inside schroot
Source: kel-agent Version: 0.4.6-2 Severity: important X-Debbugs-Cc: debian-wb-team@lists.debian.org Usertags: unshare Hi, kel-agent hard codes to skip a test when build inside schroot: https://sources.debian.org/src/kel-agent/0.4.6-2/integration/suite_test.go/#L27 But the test also fails in other environments for me, for example as a local user or in the sbuild unshare backend. Please either fix or disable the test. Cheers Jochen
Bug#1070414: fails to build when not build inside schroot
Source: kel-agent Version: 0.4.6-2 Severity: important X-Debbugs-Cc: debian-wb-t...@lists.debian.org Usertags: unshare Hi, kel-agent hard codes to skip a test when build inside schroot: https://sources.debian.org/src/kel-agent/0.4.6-2/integration/suite_test.go/#L27 But the test also fails in other environments for me, for example as a local user or in the sbuild unshare backend. Please either fix or disable the test. Cheers Jochen
Bug#1070413: sogo fails to build when test succeeds
Source: sogo Version: 5.10.0-2 Severity: important Hi, the sogo package contains a patch that hard coded the number of failing tests to two: https://sources.debian.org/src/sogo/5.10.0-2/debian/patches/0006-Update-unit-test-expected-failures.patch/ This makes the package FTBFS when more tests succeeds, for example in a local build or in sbuild with the unshare backend. Please drop this patch and fix or disable the failing tests instead. Cheers Jochen
Bug#1070412: Fails to build due to hard coded OS platform
Source: golang-github-kardianos-service Version: 1.2.0-2 Severity: important X-Debbugs-Cc: debian-wb-team@lists.debian.org Usertags: unshare Hi, golang-github-kardianos-service fails to build when it can't detect the OS platform: === RUN TestPlatformName name_test.go:15: Platform is unix-systemv name_test.go:18: Platform() want: /^linux-.*$/, got: unix-systemv --- FAIL: TestPlatformName (0.00s) This happens for example in the sbuild unshare bachend. The problem is that in the test: https://sources.debian.org/src/golang-github-kardianos-service/1.2.1-1/name_test.go/?hl=13#L13 runtime.GOOS is hard coded to linux. Cheers Jochen
Bug#1070412: Fails to build due to hard coded OS platform
Source: golang-github-kardianos-service Version: 1.2.0-2 Severity: important X-Debbugs-Cc: debian-wb-t...@lists.debian.org Usertags: unshare Hi, golang-github-kardianos-service fails to build when it can't detect the OS platform: === RUN TestPlatformName name_test.go:15: Platform is unix-systemv name_test.go:18: Platform() want: /^linux-.*$/, got: unix-systemv --- FAIL: TestPlatformName (0.00s) This happens for example in the sbuild unshare bachend. The problem is that in the test: https://sources.debian.org/src/golang-github-kardianos-service/1.2.1-1/name_test.go/?hl=13#L13 runtime.GOOS is hard coded to linux. Cheers Jochen
Bug#1070411: containerd fails to build as a normal user due to sysctl
Source: containerd Version: 1.6.20~ds1-1 Severity: important X-Debbugs-Cc: debian-wb-team@lists.debian.org Usertags: unshare Hi, containerd uses sysctl during the build which fails as a normal user: === RUN TestLinuxSandboxContainerSpec sandbox_run_linux_test.go:241: TestCase "spec should reflect original config" sandbox_run_linux_test.go:71: Check PodSandbox annotations sandbox_run_linux_test.go:124: Error Trace: /<>/_build/src/github.com/containerd/containerd/pkg/cri/server/sandbox_run_linux_test.go:124 /<>/_build/src/github.com/containerd/containerd/pkg/cri/server/sandbox_run_linux_test.go:259 Error: "" does not contain "0 2147483647" Test: TestLinuxSandboxContainerSpec sandbox_run_linux_test.go:241: TestCase "host namespace" sandbox_run_linux_test.go:71: Check PodSandbox annotations sandbox_run_linux_test.go:241: TestCase "should set supplemental groups correctly" sandbox_run_linux_test.go:71: Check PodSandbox annotations sandbox_run_linux_test.go:241: TestCase "should overwrite default sysctls" sandbox_run_linux_test.go:71: Check PodSandbox annotations sandbox_run_linux_test.go:241: TestCase "sandbox sizing annotations should be set if LinuxContainerResources were provided" sandbox_run_linux_test.go:71: Check PodSandbox annotations sandbox_run_linux_test.go:241: TestCase "sandbox sizing annotations should not be set if LinuxContainerResources were not provided" sandbox_run_linux_test.go:71: Check PodSandbox annotations sandbox_run_linux_test.go:241: TestCase "sandbox sizing annotations are zero if the resources are set to 0" sandbox_run_linux_test.go:71: Check PodSandbox annotations --- FAIL: TestLinuxSandboxContainerSpec (0.00s) https://salsa.debian.org/go-team/packages/containerd/-/blob/debian/sid/pkg/cri/server/sandbox_run_linux_test.go#L124 This make the build fail for example in the sbuild unshare backend. Cheers Jochen
Bug#1070411: containerd fails to build as a normal user due to sysctl
Source: containerd Version: 1.6.20~ds1-1 Severity: important X-Debbugs-Cc: debian-wb-t...@lists.debian.org Usertags: unshare Hi, containerd uses sysctl during the build which fails as a normal user: === RUN TestLinuxSandboxContainerSpec sandbox_run_linux_test.go:241: TestCase "spec should reflect original config" sandbox_run_linux_test.go:71: Check PodSandbox annotations sandbox_run_linux_test.go:124: Error Trace: /<>/_build/src/github.com/containerd/containerd/pkg/cri/server/sandbox_run_linux_test.go:124 /<>/_build/src/github.com/containerd/containerd/pkg/cri/server/sandbox_run_linux_test.go:259 Error: "" does not contain "0 2147483647" Test: TestLinuxSandboxContainerSpec sandbox_run_linux_test.go:241: TestCase "host namespace" sandbox_run_linux_test.go:71: Check PodSandbox annotations sandbox_run_linux_test.go:241: TestCase "should set supplemental groups correctly" sandbox_run_linux_test.go:71: Check PodSandbox annotations sandbox_run_linux_test.go:241: TestCase "should overwrite default sysctls" sandbox_run_linux_test.go:71: Check PodSandbox annotations sandbox_run_linux_test.go:241: TestCase "sandbox sizing annotations should be set if LinuxContainerResources were provided" sandbox_run_linux_test.go:71: Check PodSandbox annotations sandbox_run_linux_test.go:241: TestCase "sandbox sizing annotations should not be set if LinuxContainerResources were not provided" sandbox_run_linux_test.go:71: Check PodSandbox annotations sandbox_run_linux_test.go:241: TestCase "sandbox sizing annotations are zero if the resources are set to 0" sandbox_run_linux_test.go:71: Check PodSandbox annotations --- FAIL: TestLinuxSandboxContainerSpec (0.00s) https://salsa.debian.org/go-team/packages/containerd/-/blob/debian/sid/pkg/cri/server/sandbox_run_linux_test.go#L124 This make the build fail for example in the sbuild unshare backend. Cheers Jochen
Bug#1070410: golang-github-pion-webrtc.v3 accesses the internet during build
Source: golang-github-pion-webrtc.v3
Version: 3.1.56-2
Severity: serious
Justification: Policy 4.9
X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org
Control: affects -1 buildd.debian.org
Hi,
golang-github-pion-webrtc.v3 attempts network access during build.
This is forbidden by Policy 4.9:
For packages in the main archive, required targets must not attempt
network access, except, via the loopback interface, to services on the
build host that have been started by the build.
This can be tested with the sbuild unshare backend:
=== NAME TestDataChannelParamters_Go
util.go:41: Unexpected routines on test end:
goroutine 34 [select]:
github.com/pion/interceptor/pkg/nack.(*GeneratorInterceptor).loop(0xc240a0,
{0x9f4b80, 0xc3ec30})
/<>/_build/src/github.com/pion/interceptor/pkg/nack/generator_interceptor.go:139
+0x12d
created by
github.com/pion/interceptor/pkg/nack.(*GeneratorInterceptor).BindRTCPWriter in
goroutine 16
/<>/_build/src/github.com/pion/interceptor/pkg/nack/generator_interceptor.go:74
+0x115
goroutine 35 [select]:
github.com/pion/interceptor/pkg/report.(*ReceiverInterceptor).loop(0xc0001303c0,
{0x9f4b80, 0xc3ec30})
/<>/_build/src/github.com/pion/interceptor/pkg/report/receiver_interceptor.go:97
+0x19c
created by
github.com/pion/interceptor/pkg/report.(*ReceiverInterceptor).BindRTCPWriter in
goroutine 16
/<>/_build/src/github.com/pion/interceptor/pkg/report/receiver_interceptor.go:86
+0x115
goroutine 36 [select]:
github.com/pion/interceptor/pkg/report.(*SenderInterceptor).loop(0xc000130420,
{0x9f4b80, 0xc3ec30})
/<>/_build/src/github.com/pion/interceptor/pkg/report/sender_interceptor.go:98
+0x19c
created by
github.com/pion/interceptor/pkg/report.(*SenderInterceptor).BindRTCPWriter in
goroutine 16
/<>/_build/src/github.com/pion/interceptor/pkg/report/sender_interceptor.go:87
+0x115
[...]
Cheers Jochen
Bug#1070410: golang-github-pion-webrtc.v3 accesses the internet during build
Source: golang-github-pion-webrtc.v3
Version: 3.1.56-2
Severity: serious
Justification: Policy 4.9
X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org
Control: affects -1 buildd.debian.org
Hi,
golang-github-pion-webrtc.v3 attempts network access during build.
This is forbidden by Policy 4.9:
For packages in the main archive, required targets must not attempt
network access, except, via the loopback interface, to services on the
build host that have been started by the build.
This can be tested with the sbuild unshare backend:
=== NAME TestDataChannelParamters_Go
util.go:41: Unexpected routines on test end:
goroutine 34 [select]:
github.com/pion/interceptor/pkg/nack.(*GeneratorInterceptor).loop(0xc240a0,
{0x9f4b80, 0xc3ec30})
/<>/_build/src/github.com/pion/interceptor/pkg/nack/generator_interceptor.go:139
+0x12d
created by
github.com/pion/interceptor/pkg/nack.(*GeneratorInterceptor).BindRTCPWriter in
goroutine 16
/<>/_build/src/github.com/pion/interceptor/pkg/nack/generator_interceptor.go:74
+0x115
goroutine 35 [select]:
github.com/pion/interceptor/pkg/report.(*ReceiverInterceptor).loop(0xc0001303c0,
{0x9f4b80, 0xc3ec30})
/<>/_build/src/github.com/pion/interceptor/pkg/report/receiver_interceptor.go:97
+0x19c
created by
github.com/pion/interceptor/pkg/report.(*ReceiverInterceptor).BindRTCPWriter in
goroutine 16
/<>/_build/src/github.com/pion/interceptor/pkg/report/receiver_interceptor.go:86
+0x115
goroutine 36 [select]:
github.com/pion/interceptor/pkg/report.(*SenderInterceptor).loop(0xc000130420,
{0x9f4b80, 0xc3ec30})
/<>/_build/src/github.com/pion/interceptor/pkg/report/sender_interceptor.go:98
+0x19c
created by
github.com/pion/interceptor/pkg/report.(*SenderInterceptor).BindRTCPWriter in
goroutine 16
/<>/_build/src/github.com/pion/interceptor/pkg/report/sender_interceptor.go:87
+0x115
[...]
Cheers Jochen
Bug#1070409: golang-github-pion-ice.v2: accesses the internet during build
v2/transport_test.go:219 # 0x746424 github.com/pion/ice/v2.TestConnectionStateCallback+0x344 /<>/_build/src/github.com/pion/ice/v2/agent_test.go:653 # 0x4fa01atesting.tRunner+0xfa /usr/lib/go-1.22/src/testing/testing.go:1689 1 @ 0x43f36e 0x4510c5 0x73a965 0x766d45 0x766d46 0x476061 # 0x73a964github.com/pion/ice/v2.(*Agent).connect+0x124 /<>/_build/src/github.com/pion/ice/v2/transport.go:53 # 0x766d44github.com/pion/ice/v2.(*Agent).Accept+0x64 /<>/_build/src/github.com/pion/ice/v2/transport.go:21 # 0x766d45github.com/pion/ice/v2.connect.func1+0x65 /<>/_build/src/github.com/pion/ice/v2/transport_test.go:213 panic: timeout goroutine 195 [running]: github.com/pion/ice/v2.TestConnectionStateCallback.TimeOut.func2() /<>/_build/src/github.com/pion/transport/test/util.go:24 +0x8c created by time.goFunc /usr/lib/go-1.22/src/time/sleep.go:177 +0x2d FAILgithub.com/pion/ice/v2 8.728s Cheers Jochen
Bug#1070409: golang-github-pion-ice.v2: accesses the internet during build
v2/transport_test.go:219 # 0x746424 github.com/pion/ice/v2.TestConnectionStateCallback+0x344 /<>/_build/src/github.com/pion/ice/v2/agent_test.go:653 # 0x4fa01atesting.tRunner+0xfa /usr/lib/go-1.22/src/testing/testing.go:1689 1 @ 0x43f36e 0x4510c5 0x73a965 0x766d45 0x766d46 0x476061 # 0x73a964github.com/pion/ice/v2.(*Agent).connect+0x124 /<>/_build/src/github.com/pion/ice/v2/transport.go:53 # 0x766d44github.com/pion/ice/v2.(*Agent).Accept+0x64 /<>/_build/src/github.com/pion/ice/v2/transport.go:21 # 0x766d45github.com/pion/ice/v2.connect.func1+0x65 /<>/_build/src/github.com/pion/ice/v2/transport_test.go:213 panic: timeout goroutine 195 [running]: github.com/pion/ice/v2.TestConnectionStateCallback.TimeOut.func2() /<>/_build/src/github.com/pion/transport/test/util.go:24 +0x8c created by time.goFunc /usr/lib/go-1.22/src/time/sleep.go:177 +0x2d FAILgithub.com/pion/ice/v2 8.728s Cheers Jochen
Bug#1070334: libnet-frame-device-perl needs network access during build
Source: libnet-frame-device-perl Version: 1.12-1 Severity: serious Justification: Policy 4.9 X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org Control: affects -1 buildd.debian.org Hi, libnet-frame-device-perl fails to build with no network connection: 1..1 # Running under perl version 5.038002 for linux # Current time local: Sat Apr 27 12:53:04 2024 # Current time GMT: Sat Apr 27 12:53:04 2024 # Using Test.pm version 1.31 ok 1 # skip Test::Pod 1.00 required for testing ok Net::Frame::Device: updateFromDefault: unable to get dnet This can be tested with the sbuild unshare backend. Cheers Jochen
Bug#1070334: libnet-frame-device-perl needs network access during build
Source: libnet-frame-device-perl Version: 1.12-1 Severity: serious Justification: Policy 4.9 X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org Control: affects -1 buildd.debian.org Hi, libnet-frame-device-perl fails to build with no network connection: 1..1 # Running under perl version 5.038002 for linux # Current time local: Sat Apr 27 12:53:04 2024 # Current time GMT: Sat Apr 27 12:53:04 2024 # Using Test.pm version 1.31 ok 1 # skip Test::Pod 1.00 required for testing ok Net::Frame::Device: updateFromDefault: unable to get dnet This can be tested with the sbuild unshare backend. Cheers Jochen
Bug#1070333: python-eventlet fails to build with an empty /etc/resolv.conf
Source: python-eventlet
Version: 0.35.1-1
Severity: normal
X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org
Control: affects -1 buildd.debian.org
Hi,
python-eventlet fails to build with no nameserver specified in
/etc/resolv.conf:
=== FAILURES ===
_ TestProxyResolver.test_clear _
self =
def test_clear(self):
rp = greendns.ResolverProxy()
assert rp._cached_resolver is None
> resolver = rp._resolver
tests/greendns_test.py:304:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
eventlet/support/greendns.py:347: in _resolver
self.clear()
eventlet/support/greendns.py:355: in clear
self._resolver = dns.resolver.Resolver(filename=self._filename)
/usr/lib/python3/dist-packages/dns/resolver.py:944: in __init__
self.read_resolv_conf(filename)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
self =
f = <_io.TextIOWrapper name='/etc/resolv.conf' mode='r' encoding='UTF-8'>
def read_resolv_conf(self, f: Any) -> None:
"""Process *f* as a file in the /etc/resolv.conf format. If f is
a ``str``, it is used as the name of the file to open; otherwise it
is treated as the file itself.
Interprets the following items:
- nameserver - name server IP address
- domain - local domain name
- search - search list for host-name lookup
- options - supported options are rotate, timeout, edns0, and ndots
"""
nameservers = []
if isinstance(f, str):
try:
cm: contextlib.AbstractContextManager = open(f)
except OSError:
# /etc/resolv.conf doesn't exist, can't be read, etc.
raise NoResolverConfiguration(f"cannot open {f}")
else:
cm = contextlib.nullcontext(f)
with cm as f:
for l in f:
if len(l) == 0 or l[0] == "#" or l[0] == ";":
continue
tokens = l.split()
# Any line containing less than 2 tokens is malformed
if len(tokens) < 2:
continue
if tokens[0] == "nameserver":
nameservers.append(tokens[1])
elif tokens[0] == "domain":
self.domain = dns.name.from_text(tokens[1])
# domain and search are exclusive
self.search = []
elif tokens[0] == "search":
# the last search wins
self.search = []
for suffix in tokens[1:]:
self.search.append(dns.name.from_text(suffix))
# We don't set domain as it is not used if
# len(self.search) > 0
elif tokens[0] == "options":
for opt in tokens[1:]:
if opt == "rotate":
self.rotate = True
elif opt == "edns0":
self.use_edns()
elif "timeout" in opt:
try:
self.timeout = int(opt.split(":")[1])
except (ValueError, IndexError):
pass
elif "ndots" in opt:
try:
self.ndots = int(opt.split(":")[1])
except (ValueError, IndexError):
pass
if len(nameservers) == 0:
> raise NoResolverConfiguration("no nameservers")
E dns.resolver.NoResolverConfiguration: no nameservers
/usr/lib/python3/dist-packages/dns/resolver.py:1038: NoResolverConfiguration
This fails in sbuild with the unshare backend.
Cheers Jochen
Bug#1070332: designate fails to build with no nameserver specified in /etc/resolv.conf
Source: designate
Version: 1:18.0.0-1
Severity: normal
X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org
Control: affects -1 buildd.debian.org
Hi,
designate fails to build with no nameserver specified in
/etc/resolv.conf:
==
FAIL: designate.tests.unit.mdns.test_handler.MdnsHandleTest.test_notify
designate.tests.unit.mdns.test_handler.MdnsHandleTest.test_notify
--
testtools.testresult.real._StringException: Traceback (most recent call last):
File "/usr/lib/python3.12/unittest/mock.py", line 1390, in patched
return func(*newargs, **newkeywargs)
^
File "/<>/designate/tests/unit/mdns/test_handler.py", line 79,
in test_notify
self.assertEqual(dns.rcode.NOERROR, tuple(response)[0].rcode())
^^^
File "/<>/designate/mdns/handler.py", line 142, in _handle_notify
resolver = dns.resolver.Resolver()
^^^
File "/usr/lib/python3/dist-packages/dns/resolver.py", line 944, in __init__
self.read_resolv_conf(filename)
File "/usr/lib/python3/dist-packages/dns/resolver.py", line 1038, in
read_resolv_conf
raise NoResolverConfiguration("no nameservers")
dns.resolver.NoResolverConfiguration: no nameservers
This fails in sbuild with the unshare backend. Please disable the
failing tests:
designate.tests.unit.mdns.test_handler.MdnsHandleTest.test_notify
designate.tests.unit.mdns.test_handler.MdnsHandleTest.test_notify_same_serial
Cheers Jochen
Bug#1070325: fails to build without a non local IP
Source: servefile Version: 0.5.4-3 Severity: normal Tags: patch X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org Control: affects -1 buildd.debian.org Hi, servefile fails to build when self.getIPs() does not return an IP: Traceback (most recent call last): File "", line 198, in _run_module_as_main File "", line 88, in _run_code File "/<>/.pybuild/cpython3_3.12_servefile/build/servefile/__main__.py", line 3, in servefile.main() File "/<>/.pybuild/cpython3_3.12_servefile/build/servefile/servefile.py", line 1289, in main server.serve() File "/<>/.pybuild/cpython3_3.12_servefile/build/servefile/servefile.py", line 1008, in serve self.server.append(self._createServer(self.handler)) File "/<>/.pybuild/cpython3_3.12_servefile/build/servefile/servefile.py", line 982, in _createServer self.genKeyPair() File "/<>/.pybuild/cpython3_3.12_servefile/build/servefile/servefile.py", line 927, in genKeyPair for ip in self.getIPs() + ["127.0.0.1", "::1"]: ~~^~ TypeError: unsupported operand type(s) for +: 'NoneType' and 'list' This fails in sbuild with the unshare backend. A simple fix would be: --- servefile-0.5.4.orig/servefile/servefile.py +++ servefile-0.5.4/servefile/servefile.py @@ -890,7 +890,7 @@ class ServeFile(): ips = [ip for ip in ips if ':' in ip] return ips -return None +return [] def setSSLKeys(self, cert, key): """ Set SSL cert/key. Can be either path to file or pyopenssl X509/PKey object. """ Cheers Jochen
Bug#1070324: fails to build when no local ssh server is running
Source: python-scrapli
Version: 2023.7.30-2
Severity: normal
X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org
Control: affects -1 buildd.debian.org
Hi,
python-scrapli has a test that tries to connect to localhost port 22:
https://sources.debian.org/src/python-scrapli/2023.7.30-2/tests/unit/transport/base/test_base_socket.py/#L6
This fails in sbuild with the unshare backend:
=== FAILURES ===
test_socket_open_close_isalive
self =
socket_address_families = {}
def _connect(self, socket_address_families: Set["socket.AddressFamily"]) ->
None:
"""
Try to open socket to host using all possible address families
It seems that very occasionally when resolving a hostname (i.e.
localhost during functional
tests against vrouter devices), a v6 address family will be the first
af the socket
getaddrinfo returns, in this case, because the qemu hostfwd is not
listening on ::1, instead
only listening on 127.0.0.1 the connection will fail. Presumably this
is something that can
happen in real life too... something gets resolved with a v6 address
but is denying
connections or just not listening on that ipv6 address. This little
connect wrapper is
intended to deal with these weird scenarios.
Args:
socket_address_families: set of address families available for the
provided host
really only should ever be v4 AND v6 if providing a hostname
that resolves with
both addresses, otherwise if you just provide a v4/v6 address
it will just be a
single address family for that type of address
Returns:
None
Raises:
ScrapliConnectionNotOpened: if socket refuses connection on all
address families
ScrapliConnectionNotOpened: if socket connection times out on all
address families
"""
for address_family_index, address_family in
enumerate(socket_address_families, start=1):
self.sock = socket.socket(address_family, socket.SOCK_STREAM)
self.sock.settimeout(self.timeout)
try:
> self.sock.connect((self.host, self.port))
E ConnectionRefusedError: [Errno 111] Connection refused
scrapli/transport/base/base_socket.py:82: ConnectionRefusedError
The above exception was the direct cause of the following exception:
socket_transport =
def test_socket_open_close_isalive(socket_transport):
"""Test socket initialization/opening"""
assert socket_transport.host == "localhost"
assert socket_transport.port == 22
assert socket_transport.timeout == 10.0
> socket_transport.open()
Please disable those tests tests:
tests/unit/transport/base/test_base_socket.py::test_socket_open_close_isalive
tests/unit/transport/base/test_base_socket.py::test_socket_bool
Cheers Jochen
Bug#1070319: fails to build without a non lo IP address
Source: google-guest-agent Version: 2026.00-6 Severity: normal X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org Control: affects -1 buildd.debian.org Hi, google-guest-agent has a test that depends on having an IP address available in the build environment: https://sources.debian.org/src/google-guest-agent/2026.00-6/google_guest_agent/wsfc_test.go/#L206 This fails in sbuild with the unshare backend: === RUN TestWsfcRunAgentE2E wsfc_test.go:207: health check failed with , got = , want 1 wsfc_test.go:209: EOF --- FAIL: TestWsfcRunAgentE2E (1.00s) Cheers Jochen
Bug#1070317: fails to build without a non lo IP address
* Jochen Sprickerhof [2024-05-03 18:55]: This fails in sbuild with the chroot backend: I mean the unshare backend. signature.asc Description: PGP signature
Bug#1070319: fails to build without a non lo IP address
Source: google-guest-agent Version: 2026.00-6 Severity: normal X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org Control: affects -1 buildd.debian.org Hi, google-guest-agent has a test that depends on having an IP address available in the build environment: https://sources.debian.org/src/google-guest-agent/2026.00-6/google_guest_agent/wsfc_test.go/#L206 This fails in sbuild with the unshare backend: === RUN TestWsfcRunAgentE2E wsfc_test.go:207: health check failed with , got = , want 1 wsfc_test.go:209: EOF --- FAIL: TestWsfcRunAgentE2E (1.00s) Cheers Jochen
Bug#1070317: fails to build without a non lo IP address
Source: golang-github-likexian-gokit Version: 0.25.9-3 Severity: normal X-Debbugs-Cc: d...@debian.org, wb-t...@buildd.debian.org Control: affects -1 buildd.debian.org Hi, golang-github-likexian-gokit has a test that depends on having an IP address available in the build environment: https://sources.debian.org/src/golang-github-likexian-gokit/0.25.9-3/xip/xip_test.go/#L213 This fails in sbuild with the chroot backend: === RUN TestGetEthIPv4 assert.go:197: /<>/obj-x86_64-linux-gnu/src/github.com/likexian/gokit/xip/xip_test.go:213 assert.go:172: ! expected true, but got false --- FAIL: TestGetEthIPv4 (0.00s) Cheers Jochen
Re: Vulnerability in dropwizard-client
Hi Manuel, Your dependency check is taking a sh*t on you and your valuable time. I would ditch it for something actually working. For the record, Dropwizard 4.0.7 is not using any of the vulnerable versions of Apache HttpClient. https://github.com/dropwizard/dropwizard/blob/v4.0.7/dropwizard-dependencies/pom.xml#L37-L38 The message mentions "metrics-httpclient5" which is an entirely different thing *and also not vulnerable*. https://github.com/dropwizard/metrics/blob/v4.2.25/metrics-httpclient5/pom.xml#L21 Cheers, Jochen > Am 24.04.2024 um 14:38 schrieb 'Manuel Baden' via dropwizard-dev > : > > Hello there, > > i am using dropwizard (version 4.0.7) and when i run a dependency check it > shows the following (transitive) vulnerability: > > metrics-httpclient5-4.2.25.jar > (pkg:maven/io.dropwizard.metrics/metrics-httpclient5@4.2.25, > cpe:2.3:a:apache:httpclient:4.2.25:*:*:*:*:*:*:*) : CVE-2014-3577, > CVE-2020-13956 > > Is this problem getting fixed? > > Thank you for your help > Manuel -- You received this message because you are subscribed to the Google Groups "dropwizard-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to dropwizard-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/dropwizard-dev/546E5471-CB71-4840-9B25-7682F692EEAA%40schalanda.name.
[Freeipa-users] Fedora 40: new warning in ipa-healthckeck
Hi,
I've upgraded my freeipa server to Fedora 40 (the system was installed
several releases ago). After the upgrade I get the following new warning
from ipa-healthcheck:
{
"source": "ipahealthcheck.ds.backends",
"check": "BackendsCheck",
"result": "WARNING",
"uuid": "875db8e3-029c-46f7-87e5-bf9a216d9637",
"when": "20240426184431Z",
"duration": "0.031642",
"kw": {
"key": "DSBLE0005",
"items": [
"nsslapd-dbcachesize",
"nsslapd-db-logdirectory",
"nsslapd-db-transaction-wait",
"nsslapd-db-checkpoint-interval",
"nsslapd-db-compactdb-interval",
"nsslapd-db-compactdb-time",
"nsslapd-db-transaction-batch-val",
"nsslapd-db-transaction-batch-min-wait",
"nsslapd-db-transaction-batch-max-wait",
"nsslapd-db-logbuf-size",
"nsslapd-db-page-size",
"nsslapd-db-locks",
"nsslapd-db-locks-monitoring-enabled",
"nsslapd-db-locks-monitoring-threshold",
"nsslapd-db-locks-monitoring-pause",
"nsslapd-db-private-import-mem",
"nsslapd-db-deadlock-policy"
],
"msg": "Found configuration attributes that are not applicable for the
configured backend type."
}
},
According to
https://www.port389.org/docs/389ds/FAQ/Berkeley-DB-deprecation.html the
bdb backend is deprecated. The system was installed with
389-ds-base < 1.4.4.9-1.fc33.x86_64 (I see the upgrade to that version
in /var/log/dnf.rpm.log*. Since 3.0 new installations should use LMBD as
the backend. Is that true for new installations?
What is the desired action that I should take?
I can remove the options from the dirsrv configuration. Should I?
Shall I switch to lmdb manually? Or is that something that
ipa-server-upgrade should be doing?
Otherwise I can suppress the message in ipa-healthcheck for now. But I
guess I should fix my installation before the deprecated support really
gets dropped... Is deploying a new replica and decommisioning the old
server we the preferred action?
Jochen
--
This space is intentionally left blank.
--
___
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
Bug#1069809: xhtml2pdf accesses network resources during the build
Source: xhtml2pdf Version: 0.2.15+dfsg-1 Severity: serious Tags: sid trixie ftbfs xhtml2pdf accesses network resources during the build: == FAIL: test_document_cannot_identify_image (tests.test_document.DocumentTest.test_document_cannot_identify_image) Test that images which cannot be identified don't cause stack trace to be printed -- Traceback (most recent call last): File "/build/package/package/.pybuild/cpython3_3.11_xhtml2pdf/build/tests/test_document.py", line 189, in test_document_cannot_identify_image self.assertEqual( AssertionError: Lists differ: ['WAR[16 chars]ags:Could not get image data from src attribut[265 chars]>\''] != ['WAR[16 chars]ags:Cannot identify image file:\n\'\'' + ['WARNING:xhtml2pdf.tags:Cannot identify image file:\n' - ['WARNING:xhtml2pdf.tags:Could not get image data from src attribute: ' - 'https://raw.githubusercontent.com/python-pillow/Pillow/7921da54a73dd4a30c23957369b79cda176005c6/Tests/images/zero_width.gif\n' "'https://raw.githubusercontent.com/python-pillow/Pillow/7921da54a73dd4a30c23957369b79cda176005c6/Tests/images/zero_width.gif"/>\''] == FAIL: test_document_with_broken_image (tests.test_document.DocumentTest.test_document_with_broken_image) Test that broken images don't cause unhandled exception -- Traceback (most recent call last): File "/build/package/package/.pybuild/cpython3_3.11_xhtml2pdf/build/tests/test_document.py", line 169, in test_document_with_broken_image self.assertEqual( AssertionError: Lists differ: [] != ["WARNING:xhtml2pdf.xhtml2pdf_reportlab:SV[151 chars]ml'"] Second list contains 1 additional elements. First extra element 0: "WARNING:xhtml2pdf.xhtml2pdf_reportlab:SVG drawing could not be resized: 'https://raw.githubusercontent.com/xhtml2pdf/xhtml2pdf/b01b1d8f9497dedd0f2454409d03408bdeea997c/tests/samples/images.html'" - [] + ['WARNING:xhtml2pdf.xhtml2pdf_reportlab:SVG drawing could not be resized: ' + "'https://raw.githubusercontent.com/xhtml2pdf/xhtml2pdf/b01b1d8f9497dedd0f2454409d03408bdeea997c/tests/samples/images.html'"]
Bug#1069809: xhtml2pdf accesses network resources during the build
Source: xhtml2pdf Version: 0.2.15+dfsg-1 Severity: serious Tags: sid trixie ftbfs xhtml2pdf accesses network resources during the build: == FAIL: test_document_cannot_identify_image (tests.test_document.DocumentTest.test_document_cannot_identify_image) Test that images which cannot be identified don't cause stack trace to be printed -- Traceback (most recent call last): File "/build/package/package/.pybuild/cpython3_3.11_xhtml2pdf/build/tests/test_document.py", line 189, in test_document_cannot_identify_image self.assertEqual( AssertionError: Lists differ: ['WAR[16 chars]ags:Could not get image data from src attribut[265 chars]>\''] != ['WAR[16 chars]ags:Cannot identify image file:\n\'\'' + ['WARNING:xhtml2pdf.tags:Cannot identify image file:\n' - ['WARNING:xhtml2pdf.tags:Could not get image data from src attribute: ' - 'https://raw.githubusercontent.com/python-pillow/Pillow/7921da54a73dd4a30c23957369b79cda176005c6/Tests/images/zero_width.gif\n' "'https://raw.githubusercontent.com/python-pillow/Pillow/7921da54a73dd4a30c23957369b79cda176005c6/Tests/images/zero_width.gif"/>\''] == FAIL: test_document_with_broken_image (tests.test_document.DocumentTest.test_document_with_broken_image) Test that broken images don't cause unhandled exception -- Traceback (most recent call last): File "/build/package/package/.pybuild/cpython3_3.11_xhtml2pdf/build/tests/test_document.py", line 169, in test_document_with_broken_image self.assertEqual( AssertionError: Lists differ: [] != ["WARNING:xhtml2pdf.xhtml2pdf_reportlab:SV[151 chars]ml'"] Second list contains 1 additional elements. First extra element 0: "WARNING:xhtml2pdf.xhtml2pdf_reportlab:SVG drawing could not be resized: 'https://raw.githubusercontent.com/xhtml2pdf/xhtml2pdf/b01b1d8f9497dedd0f2454409d03408bdeea997c/tests/samples/images.html'" - [] + ['WARNING:xhtml2pdf.xhtml2pdf_reportlab:SVG drawing could not be resized: ' + "'https://raw.githubusercontent.com/xhtml2pdf/xhtml2pdf/b01b1d8f9497dedd0f2454409d03408bdeea997c/tests/samples/images.html'"]
Bug#1069805: scikit-build tries pip install during build
Source: scikit-build
Version: 0.17.6-1
Severity: serious
Tags: trixie sid ftbfs
scikit-build accesses network resources during the build:
process =
stdout = None, stderr = None, retcode = 1
def run(*popenargs,
input=None, capture_output=False, timeout=None, check=False,
**kwargs):
"""Run command with arguments and return a CompletedProcess instance.
The returned instance will have attributes args, returncode, stdout and
stderr. By default, stdout and stderr are not captured, and those
attributes
will be None. Pass stdout=PIPE and/or stderr=PIPE in order to capture
them,
or pass capture_output=True to capture both.
If check is True and the exit code was non-zero, it raises a
CalledProcessError. The CalledProcessError object will have the return
code
in the returncode attribute, and output & stderr attributes if those
streams
were captured.
If timeout is given, and the process takes too long, a TimeoutExpired
exception will be raised.
There is an optional argument "input", allowing you to
pass bytes or a string to the subprocess's stdin. If you use this
argument
you may not also use the Popen constructor's "stdin" argument, as
it will be used internally.
By default, all communication is in bytes, and therefore any "input"
should
be bytes, and the stdout and stderr will be bytes. If in text mode, any
"input" should be a string, and stdout and stderr will be strings
decoded
according to locale encoding, or by "encoding" if set. Text mode is
triggered by setting any of text, encoding, errors or
universal_newlines.
The other arguments are the same as for the Popen constructor.
"""
if input is not None:
if kwargs.get('stdin') is not None:
raise ValueError('stdin and input arguments may not both be
used.')
kwargs['stdin'] = PIPE
if capture_output:
if kwargs.get('stdout') is not None or kwargs.get('stderr') is not
None:
raise ValueError('stdout and stderr arguments may not be used '
'with capture_output.')
kwargs['stdout'] = PIPE
kwargs['stderr'] = PIPE
with Popen(*popenargs, **kwargs) as process:
try:
stdout, stderr = process.communicate(input, timeout=timeout)
except TimeoutExpired as exc:
process.kill()
if _mswindows:
# Windows accumulates the output in a single blocking
# read() call run on child threads, with the timeout
# being done in a join() on those threads. communicate()
# _after_ kill() is required to collect that and add it
# to the exception.
exc.stdout, exc.stderr = process.communicate()
else:
# POSIX _communicate already populated the output so
# far into the TimeoutExpired exception.
process.wait()
raise
except: # Including KeyboardInterrupt, communicate handled that.
process.kill()
# We don't call process.wait() as .__exit__ does that for us.
raise
retcode = process.poll()
if check and retcode:
> raise CalledProcessError(retcode, process.args,
output=stdout, stderr=stderr)
E subprocess.CalledProcessError: Command '['/usr/bin/python3.12',
'-m', 'pip', 'wheel', '--wheel-dir',
'/tmp/pytest-of-jspricke/pytest-21/wheelhouse0', '/build/package/package']'
returned non-zero exit status 1.
Bug#1069805: scikit-build tries pip install during build
Source: scikit-build
Version: 0.17.6-1
Severity: serious
Tags: trixie sid ftbfs
scikit-build accesses network resources during the build:
process =
stdout = None, stderr = None, retcode = 1
def run(*popenargs,
input=None, capture_output=False, timeout=None, check=False,
**kwargs):
"""Run command with arguments and return a CompletedProcess instance.
The returned instance will have attributes args, returncode, stdout and
stderr. By default, stdout and stderr are not captured, and those
attributes
will be None. Pass stdout=PIPE and/or stderr=PIPE in order to capture
them,
or pass capture_output=True to capture both.
If check is True and the exit code was non-zero, it raises a
CalledProcessError. The CalledProcessError object will have the return
code
in the returncode attribute, and output & stderr attributes if those
streams
were captured.
If timeout is given, and the process takes too long, a TimeoutExpired
exception will be raised.
There is an optional argument "input", allowing you to
pass bytes or a string to the subprocess's stdin. If you use this
argument
you may not also use the Popen constructor's "stdin" argument, as
it will be used internally.
By default, all communication is in bytes, and therefore any "input"
should
be bytes, and the stdout and stderr will be bytes. If in text mode, any
"input" should be a string, and stdout and stderr will be strings
decoded
according to locale encoding, or by "encoding" if set. Text mode is
triggered by setting any of text, encoding, errors or
universal_newlines.
The other arguments are the same as for the Popen constructor.
"""
if input is not None:
if kwargs.get('stdin') is not None:
raise ValueError('stdin and input arguments may not both be
used.')
kwargs['stdin'] = PIPE
if capture_output:
if kwargs.get('stdout') is not None or kwargs.get('stderr') is not
None:
raise ValueError('stdout and stderr arguments may not be used '
'with capture_output.')
kwargs['stdout'] = PIPE
kwargs['stderr'] = PIPE
with Popen(*popenargs, **kwargs) as process:
try:
stdout, stderr = process.communicate(input, timeout=timeout)
except TimeoutExpired as exc:
process.kill()
if _mswindows:
# Windows accumulates the output in a single blocking
# read() call run on child threads, with the timeout
# being done in a join() on those threads. communicate()
# _after_ kill() is required to collect that and add it
# to the exception.
exc.stdout, exc.stderr = process.communicate()
else:
# POSIX _communicate already populated the output so
# far into the TimeoutExpired exception.
process.wait()
raise
except: # Including KeyboardInterrupt, communicate handled that.
process.kill()
# We don't call process.wait() as .__exit__ does that for us.
raise
retcode = process.poll()
if check and retcode:
> raise CalledProcessError(retcode, process.args,
output=stdout, stderr=stderr)
E subprocess.CalledProcessError: Command '['/usr/bin/python3.12',
'-m', 'pip', 'wheel', '--wheel-dir',
'/tmp/pytest-of-jspricke/pytest-21/wheelhouse0', '/build/package/package']'
returned non-zero exit status 1.
Bug#1069804: rust-mio-0.6 accesses network resources during the build
Source: rust-mio-0.6
Version: 0.6.23-3
Severity: serious
Tags: sid trixie ftbfs
rust-mio-0.6 accesses network resources during the build:
Test executable failed (exit status: 101).
stderr:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os {
code: 101, kind: NetworkUnreachable, message: "Network is unreachable" }',
src/sys/unix/ready.rs:22:16
stack backtrace:
0: rust_begin_unwind
at /usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5
1: core::panicking::panic_fmt
at /usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14
2: core::result::unwrap_failed
at /usr/src/rustc-1.70.0/library/core/src/result.rs:1687:5
3: core::result::Result::unwrap
4: rust_out::main
5: core::ops::function::FnOnce::call_once
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose
backtrace.
failures:
src/poll.rs - poll::Poll (line 267)
src/poll.rs - poll::Poll::deregister (line 877)
src/poll.rs - poll::Poll::register (line 735)
src/poll.rs - poll::Poll::reregister (line 820)
src/sys/unix/ready.rs - sys::unix::ready::UnixReady (line 66)
test result: FAILED. 74 passed; 5 failed; 0 ignored; 0 measured; 0 filtered
out; finished in 4.37s
