Re: how to fix lintian error: library-not-linked-against-libc

Ahmad Khalifa writes: > Instead, lintian should alert that some symbols are "unversioned". The problem is that unversioned symbols are often correct. For one, not every shared library uses symbol versioning; we may want them all to use symbol versioning, and certainly way more of them do today,

Re: how to fix lintian error: library-not-linked-against-libc

terfered with proper Russ> symbol versioning and could cause the symbols to be resolved Russ> weirdly in a way that could cause serious bugs. Yeah, and so the symbol versions would not be present, and so I think we're back to needing to know what symbols are from libc6. A

Re: how to fix lintian error: library-not-linked-against-libc

erfered with proper >> Russ> symbol versioning and could cause the symbols to be resolved >> Russ> weirdly in a way that could cause serious bugs. >> Yeah, and so the symbol versions would not be present, and so I think >> we're back to needing to know wha

Re: how to fix lintian error: library-not-linked-against-libc

the symbols to be resolved weirdly Russ> in a way that could cause serious bugs. Yeah, and so the symbol versions would not be present, and so I think we're back to needing to know what symbols are from libc6. A better error if we knew how to generate it efficiently would be using a libc

Re: how to fix lintian error: library-not-linked-against-libc

irdly Russ> in a way that could cause serious bugs. Yeah, and so the symbol versions would not be present, and so I think we're back to needing to know what symbols are from libc6. A better error if we knew how to generate it efficiently would be using a libc symbol without a symbol version.

Re: how to fix lintian error: library-not-linked-against-libc

Ahmad Khalifa writes: > But reading that, I don't see how the linker could declare a dynamic > GLIBC_ symbol without the related library reference. > In fact, it should choke with "undefined reference" long before outputting > a .so file. Even when compiling with -nolibc. But there is always a >

Re: how to fix lintian error: library-not-linked-against-libc

ic. If the tag is useful, we should fix it; if it's not useful, we should delete it. It's not a pedantic issue with the package. If the error is real, it's serious, but Lintian's check for the error has a high false positive rate. That's not what pedantic is for. Pedantic is

Re: how to fix lintian error: library-not-linked-against-libc

g to Pedantic, but not deleting it. So, I guess I'll say this more explicitly: I am opposed to downgrading the tag to pedantic. If the tag is useful, we should fix it; if it's not useful, we should delete it. It's not a pedantic issue with the package. If the error is real, it&#

Re: how to fix lintian error: library-not-linked-against-libc

On 27/01/2025 18:24, Russ Allbery wrote: Marvin Renich writes: * Russ Allbery [250126 12:47]: In theory it would be possible to do better in Lintian by scanning the symbol table to see if the libc dependency is really unneeded. But doing that sounds at least a little annoying. Annoying to

Re: how to fix lintian error: library-not-linked-against-libc

wrong with it? Nothing so far as I know. It's just work, and if people don't think that the problem is likely to occur, maybe the work isn't worth doing and the tag should just be deleted. > Clearly the current state is a bug in lintian, as so many packages > override this er

Re: how to fix lintian error: library-not-linked-against-libc

I thought of this solution while reading earlier in this thread, and it seems like the "correct" solution to me. What is wrong with it? Clearly the current state is a bug in lintian, as so many packages override this error. And from your description, the test has a significant purpose t

Re: how to fix lintian error: library-not-linked-against-libc

bering. It's certainly easy to introduce a libc dependency by writing normal C code and calling some function that's universally available, including on Windows, without thinking about it, thus making the state of "not using libc" somewhat unstable. But problems like that combine

Re: how to fix lintian error: library-not-linked-against-libc

On Sun, 26 Jan 2025 at 09:14:30 -0800, Russ Allbery wrote: > maybe it's more common these days to have plugin libraries > that aren't linked with libc? Back in the day, it was very rare for people > to successfully manage to write code that never called a libc symbol. In ecosystems with a "platfor

Re: how to fix lintian error: library-not-linked-against-libc

Jeremy Bícha writes: > On Sun, Jan 26, 2025 at 6:28 AM Ahmad Khalifa wrote: >> The lintian error is a great heads-up and it's up to the reader to >> decide whether it's a true error to fix or a false-positive to >> override. > I have never seen this Lintian er

Re: how to fix lintian error: library-not-linked-against-libc

On 26/01/2025 12:41, Jeremy Bícha wrote: On Sun, Jan 26, 2025 at 6:28 AM Ahmad Khalifa wrote: The lintian error is a great heads-up and it's up to the reader to decide whether it's a true error to fix or a false-positive to override. I have never seen this Lintian error actually be

Re: how to fix lintian error: library-not-linked-against-libc

On Sun, Jan 26, 2025 at 6:28 AM Ahmad Khalifa wrote: > The lintian error is a great heads-up and it's up to the reader to > decide whether it's a true error to fix or a false-positive to override. I have never seen this Lintian error actually be useful. I think an error is fa

Re: how to fix lintian error: library-not-linked-against-libc

Hi, unrelated to your question, but there are things that jump out for me: Am Sat, Jan 25, 2025 at 10:57:26PM -0600, schrieb Steven Robbins: > The (CMake-generated) link line does have a bunch of options. Nothing jumped > out at me: > > /usr/bin/c++ -fPIC -g -O2 > -ffile-prefix-map=/home/stev

Re: how to fix lintian error: library-not-linked-against-libc

.so.6", the question is whether that is an error or not. I think we're on the same page, I just added an extra step out of caution :) The lintian error is a great heads-up and it's up to the reader to decide whether it's a true error to fix or a false-positive to override. -- Regards, Ahmad

Re: how to fix lintian error: library-not-linked-against-libc

On Sun, Jan 26, 2025 at 01:02:25AM -0600, Steven Robbins wrote: > > I've come to realise the ITK build has 15 libraries that lintian flags with > > error library-not-linked-against-libc. > > Someone suggested to run ldd -r. Okay, so what does this tell me? > > $

Re: how to fix lintian error: library-not-linked-against-libc

On Sun, Jan 26, 2025 at 11:07:12AM +, Ahmad Khalifa wrote: > > The error description seems straightforward.  But how does one solve > > this?  I have to assume that the linker would by default link with the > > libc (?), so perhaps the linker invocation has options that

Re: how to fix lintian error: library-not-linked-against-libc

On 26/01/2025 04:57, Steven Robbins wrote: I've come to realise the ITK build has 15 libraries that lintian flags with ... The error description seems straightforward.  But how does one solve this?  I have to assume that the linker would by default link with the libc (?), so perhap

Re: how to fix lintian error: library-not-linked-against-libc

On Saturday, January 25, 2025 10:57:26 P.M. CST you wrote: > I've come to realise the ITK build has 15 libraries that lintian flags with > error library-not-linked-against-libc. Someone suggested to run ldd -r. Okay, so what does this tell me? $ ldd -r /lib/x86_64-linux-gnu/libITKC

Re: how to fix lintian error: library-not-linked-against-libc

On Sat, Jan 25, 2025 at 10:57:26PM -0600, Steven Robbins wrote: > I've come to realise the ITK build has 15 libraries that lintian flags with > error library-not-linked-against-libc. > > https://lintian.debian.org/tags/library-not-linked-against-libc.html[1] > > The

how to fix lintian error: library-not-linked-against-libc

I've come to realise the ITK build has 15 libraries that lintian flags with error library-not-linked-against-libc. https://lintian.debian.org/tags/library-not-linked-against-libc.html[1] The error description seems straightforward. But how does one solve this? I have to assume tha

Bug#1093660: ITP: ocaml-markup -- error-recovering functional HTML5 and XML parsers and writers

: MIT Programming Lang: OCaml Description : error-recovering functional HTML5 and XML parsers and writers Markup.ml provides an HTML parser and an XML parser. The parsers are wrapped in a simple interface: they are functions that transform byte streams to parsing signal streams

Bug#1092266: ITP: golang-github-jackc-pgerrcode -- constants for PostgreSQL error codes

Description : constants for PostgreSQL error codes Package pgerrcode contains constants for PostgreSQL error codes. https://salsa.debian.org/go-team/packages/golang-github-jackc-pgerrcode This package is added as a new upstream dependency [1] noticed when trying to upgrade Trillian from 1.6.0

Re: Strange armel build error

On 18/08/2024 11:35, Adam D. Barratt wrote: On Sun, 2024-08-18 at 14:23 +0500, Andrey Rakhmatullin wrote: On Sun, Aug 18, 2024 at 11:02:03AM +0200, Alec Leamas wrote: [...]-- If you can’t fix the build, you don’t need to exclude the architecture — you can ask for removal of the armel pac

Re: Strange armel build error

On 8/18/24 11:23 AM, Andrey Rakhmatullin wrote: On Sun, Aug 18, 2024 at 11:02:03AM +0200, Alec Leamas wrote: On 18/08/2024 09:04, Stephen Kitt wrote: On Fri, 16 Aug 2024 17:46:45 +0200, Alec Leamas wrote: Or just exclude that architecture i. e., list all archs but armel? If you can’t fix the

Re: Strange armel build error

Hi list, On 18/08/2024 11:23, Andrey Rakhmatullin wrote: On Sun, Aug 18, 2024 at 11:02:03AM +0200, Alec Leamas wrote: Hi Stephen, On 18/08/2024 09:04, Stephen Kitt wrote: On Fri, 16 Aug 2024 17:46:45 +0200, Alec Leamas wrote: Or just exclude that architecture i. e., list all archs but armel

Re: Strange armel build error

Hi; On 18/08/2024 06:11, Wookey wrote: On 2024-08-17 17:58 +0200, Alec Leamas wrote: To make it more interesting, the simple -latomic fix doesn't seem to cut it That's a pity, it sounds plausible. I'll try to take a look. Thanks! That said, unless you have oceans of time, perhaps it might m

Re: Strange armel build error

On Sun, 2024-08-18 at 14:23 +0500, Andrey Rakhmatullin wrote: > On Sun, Aug 18, 2024 at 11:02:03AM +0200, Alec Leamas wrote: > > Hi Stephen, > > > > On 18/08/2024 09:04, Stephen Kitt wrote: > > [...] > > > If you can’t fix the build, you don’t need to exclude the > > > architecture — you > > > ca

Re: Strange armel build error

On Sun, Aug 18, 2024 at 11:02:03AM +0200, Alec Leamas wrote: > Hi Stephen, > > On 18/08/2024 09:04, Stephen Kitt wrote: > > On Fri, 16 Aug 2024 17:46:45 +0200, Alec Leamas > > wrote: > > > Or just exclude that architecture i. e., list all archs but armel? > > If you can’t fix the build, you don’

Re: Strange armel build error

Hi Stephen, On 18/08/2024 09:04, Stephen Kitt wrote: On Fri, 16 Aug 2024 17:46:45 +0200, Alec Leamas wrote: Or just exclude that architecture i. e., list all archs but armel? If you can’t fix the build, you don’t need to exclude the architecture — you can ask for removal of the armel package

Re: Strange armel build error

On Fri, 16 Aug 2024 17:46:45 +0200, Alec Leamas wrote: > Or just exclude that architecture i. e., list all archs but armel? If you can’t fix the build, you don’t need to exclude the architecture — you can ask for removal of the armel package in testing. That will allow the package to migrate even

Re: Strange armel build error

On 2024-08-17 17:58 +0200, Alec Leamas wrote: > > > Fair enough. But TBH, i just cannot wait "a couple of weeks" for a possible > reply; there are users waiting for the backports as I write. Fair enough. If you can't wait then you can't wait. > To make it more interesting, the simple -latomic

Re: Strange armel build error

On 17/08/2024 14:42, Wookey wrote: On 2024-08-16 17:46 +0200, Alec Leamas wrote: From another perspective: what is the right thing to do in a situation like this? Trying to hunt down the problem, and thus causing all sorts of noise like this message? This is what the policy says, but still

Re: Strange armel build error

On 2024-08-16 17:46 +0200, Alec Leamas wrote: > > From another perspective: what is the right thing to do in a situation like > this? Trying to hunt down the problem, and thus causing all sorts of noise > like this message? This is what the policy says, but still... > > Or just exclude that arc

Re: Strange armel build error

Hi Timo and Paul, On 16/08/2024 18:10, Timo Röhling wrote: Hi Alec, * Alec Leamas [2024-08-16 17:46]: /usr/include/c++/14/bits/atomic_futex.h:278:(.text+0x16dc): undefined reference to `std::__atomic_futex_unsigned_base::_M_futex_notify_all(unsigned int*)' /usr/bin/ld: /usr/include/c++/14/b

Re: Strange armel build error

Hi Alec, * Alec Leamas [2024-08-16 17:46]: /usr/include/c++/14/bits/atomic_futex.h:278:(.text+0x16dc): undefined reference to `std::__atomic_futex_unsigned_base::_M_futex_notify_all(unsigned int*)' /usr/bin/ld: /usr/include/c++/14/bits/atomic_futex.h:278:(.text+0x29d8): undefined reference to

Re: Strange armel build error

Hi, On 16-08-2024 17:46, Alec Leamas wrote: All other builds are OK. Has anyone a hint about what might be going on here? https://release.debian.org/testing/arch_qualify.html armel column. Paul OpenPGP_signature.asc Description: OpenPGP digital signature

Strange armel build error

Dear list, Still trying to maintain opencpn. Now looking at an error in the armel build [1]. The core is a bunch of messages like /usr/include/c++/14/bits/atomic_futex.h:278:(.text+0x16dc): undefined reference to `std::__atomic_futex_unsigned_base::_M_futex_notify_all(unsigned int*)'

Re: broadcast error messages, unofficial Debian 12

pment of debian. Your > query appears to be user support, which takes place on debian-user. > I've set Reply-To: debian-user. > > On Wed, Dec 13, 2023 at 02:52:11PM -0500, Alan Corey wrote: > > I can have 2 or more Zutty terminal windows running to work on a > > pro

Re: broadcast error messages, unofficial Debian 12

to work on a > program. When I get a compiling error in one terminal it gets > broadcast to both windows. > > This particular error is not anything in my code, I don't recognize any of > it, but it shows up because I had a warning in my stuff: > > W [main.cc:1161]

broadcast error messages, unofficial Debian 12

This is in an unofficial debian release at https://raspi.debian.net/tested-images/, the one for 8 GB Pis. I've never seen anything like it. I can have 2 or more Zutty terminal windows running to work on a program. When I get a compiling error in one terminal it gets broadcast to both wi

Bug#1051590: general: Received error from D-Bus search

Package: general Severity: normal X-Debbugs-Cc: kru...@gmail.com Dear Maintainer, Received error from D-Bus search provider org.gnome.Terminal.desktop: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Obiekt nie istnieje w ścieżce „/org/gnome/Terminal/SearchProvider”

Strange Error After Update

Hi, I receive the following error after logging into the Gnome desktop following and update. Detailed errors from the package manager follow: failed to build result for 71b677ca0f1bc2c5b804fa1d59e52064ce589293 This is reported in a pop-up from the Gnome Software app I believe, and

Re: Debian 5.19.11-1 (2022-10-03) x86_64 GNU/Linux: NFSv3 Input/output error while cat , 5.14 or below ok

: > WinNFSd.exe -log on "F/Kernel5.19/NFS" > client: > mount -t nfs 192.168.0.21:/F/Kernel5.19/NFS /mnt/img -o noatime,nfsvers=3 > cd /mnt/img/GPCImageV4.0 > cat parts > *** What was the outcome of this action?*** > "Input/output error." > terminal interfac

Debian 5.19.11-1 (2022-10-03) x86_64 GNU/Linux: NFSv3 Input/output error while cat , 5.14 or below ok

ineffective)?*** server: WinNFSd.exe -log on "F/Kernel5.19/NFS" client: mount -t nfs 192.168.0.21:/F/Kernel5.19/NFS /mnt/img -o noatime,nfsvers=3 cd /mnt/img/GPCImageV4.0 cat parts *** What was the outcome of this action?*** "Input/output error." terminal interface stuck *** What ou

Re: Bug#1029911: rust-ureq FTBFS: error: unable to load build system class 'cargo': Can't locate String/ShellQuote.pm

On Sun, Jan 29, 2023 at 01:33:56AM +0100, Jonas Smedegaard wrote: > Hi, > > Can someone help me understand what is going wrong in Bug#1029911? > > The source package build-depends on libstring-shellquote-perl but it > seems like that build-dependency is not getting installed on the buildd. >...

Re: Bug#1029911: rust-ureq FTBFS: error: unable to load build system class 'cargo': Can't locate String/ShellQuote.pm

Quoting Adrian Bunk (2023-01-29 01:53:19) > On Sun, Jan 29, 2023 at 01:33:56AM +0100, Jonas Smedegaard wrote: > > Hi, > > > > Can someone help me understand what is going wrong in Bug#1029911? > > > > The source package build-depends on libstring-shellquote-perl but it > > seems like that build-d

Re: Bug#1029911: rust-ureq FTBFS: error: unable to load build system class 'cargo': Can't locate String/ShellQuote.pm

Hi, Can someone help me understand what is going wrong in Bug#1029911? The source package build-depends on libstring-shellquote-perl but it seems like that build-dependency is not getting installed on the buildd. I use same setup for a range of Rust library packages, and this is the only one fai

Bug#1027332: ITP: ruby-google-cloud-errors -- Error classes for google-cloud-ruby

https://github.com/googleapis/google-cloud-ruby/tree/master/google-cloud-errors * License : Apache-2.0 Programming Lang: ruby Description : Error classes for google-cloud-ruby This Ruby library contains error classes raised by Google Cloud API clients. google-cloud-errors defin

Bug#1018891: marked as done (general: Can't install fans on msi laptop due to missing ec_sys kernel. Command prompt modprobe ec_sys write_support=1, I get error: FATAL: Module ec_sys not found in dire

Your message dated Tue, 13 Sep 2022 21:33:03 +0200 with message-id and subject line Re: Bug#1018891: general: Can't install fans on msi laptop due to missing ec_sys kernel. Command prompt modprobe ec_sys write_support=1, I get error: FATAL: Module ec_sys not found in directory /lib/mo

Bug#1018891: general: Can't install fans on msi laptop due to missing ec_sys kernel. Command prompt modprobe ec_sys write_support=1, I get error: FATAL: Module ec_sys not found in directory /lib/modul

Package: general Severity: normal X-Debbugs-Cc: velmory...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was

Re: Error when running dh_dwz (actually an error when running dwz(1))

> ( > > > https://salsa.debian.org/input-method-team/marisa/commit/f5ff598466266b230d68c9db9f8e31281604b7a6 > > > ). The following error will pop up when dwz is called: > > > > > > = > > > [...] > > >dh_dwz > > > dwz

Re: Error when running dh_dwz (actually an error when running dwz(1))

itself but I'm looking > > for some help inside Debian first. > > > > Please try to build package marisa from its git packaging repo > > ( > > https://salsa.debian.org/input-method-team/marisa/commit/f5ff598466266b230d68c9db9f8e31281

Re: faker,ruby-faker: error when trying to install together

On Tue, Jul 05, 2022 at 06:44:15PM +0200, Timo Röhling wrote: > On Mon, 23 May 2022 01:58:56 +0200 Andreas Beckmann wrote: > > Package: faker,ruby-faker > > Severity: serious > > Tags: sid bookworm > > User: trei...@debian.org > > Usertags: edos-file-overwrite > > Control: found -1 0.9.3-0.1 > > C

Re: faker,ruby-faker: error when trying to install together

On Mon, 23 May 2022 01:58:56 +0200 Andreas Beckmann wrote: Package: faker,ruby-faker Severity: serious Tags: sid bookworm User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 0.9.3-0.1 Control: found -1 2.20.0-1 [...] Here is a list of files that are known to be shared by bo

Re: Help needed: C++ compile error with nix 2.5.1

* Thomas Koch , 2022-01-16, 11:23: https://github.com/NixOS/nix/issues/5923 The first bad commit is: https://github.com/nlohmann/json/commit/0e694b4060ed55df (This happens to be also the first bad commit for , so I guess it's the same issue.) I

Help needed: C++ compile error with nix 2.5.1

For a C++ programmer who cares about nix in Debian: https://github.com/NixOS/nix/issues/5923 Thank you! Thomas

Bug#1002808: ITP: golang-github-muesli-toktok -- typo/error resilient, human-readable token generator (Go library)

Description : typo/error resilient, human-readable token generator (Go library) Go package toktok is a human-friendly token generator. It creates tokens which avoid characters that can be easily misinterpreted, like '1' and 'I' or '8' and 'B', as well

Bug#1002724: ITP: openfec -- Forward Error Correction codes

License : CeCILL-C Programming Lang: C Description : Forward Error Correction codes Application-Level Forward Error Correction codes add redundancy in order to be able to recover from erasures. this library is required by the Roc Project, whose PipeWire modules are currently disa

Re: Unmet :native dependency error when cross-compiling with dpkg-buildpackage

self is being compiled using sbuild. During "Install > package > build dependencies" stage, 'swig:native' is correctly resolved to > 'swig:amd64'. All deps are correctly installed, then. But later, when it > comes > to dpkg-buildpackage stage, it f

Unmet :native dependency error when cross-compiling with dpkg-buildpackage

Hello. While experimenting with cross-compilation I faced an error that looks like a bug in dpkg-buildpackage for me. The conditions are the following: Build Architecture: amd64 Host Architecture: arm64 The package I'm trying to cross-build is 'u-boot' with some patches. It

Re: Debian 11 Bullseye Setup Problems Error Report

G'day admin4, I suggest you take this to the #debian IRC channel where you can hopefully drill down to the root cause of the problem. A mailing list like debian-devel is not really well suited to do back-and-forth debugging... *t On 23.09.21 12:08, admin4 wrote: GoodDay Mates, network conn

Re: Debian 11 Bullseye Setup Problems Error Report

GoodDay Mates, network connectivity dropping during package download is still there, it is a major problem, sometimes it works, sometimes not, this used to work very well. it will especially annoy new users, so this issue need to be debugged & fixed! will also write to SpaceX about it (if it has

Re: Debian 11 Bullseye Setup Problems Error Report

Paul Wise writes: > On Wed, Aug 18, 2021 at 10:42 AM admin4 wrote: > >> is there a Debian "testing" team? > > That is composed of everyone who uses Debian and especially those who > decide to report an issue they found. While that probably accounts for the bulk of the effort, there are also peo

Re: Debian 11 Bullseye Setup Problems Error Report

On Fri, Aug 20, 2021 at 10:15 PM Timothy M Butterworth wrote: > I give the installer a 5 star rating although I would like to see some > improvements made to the disk configuration utility. Currently the > disk configuration utility is non-intuitive and appears to be designed > for keyboard only n

Re: Debian 11 Bullseye Setup Problems Error Report

I have been using Debian 11 since Alpha 1 release. I installed with non-free live DVD using the calamaris installer. I have it installed on three systems one Intel Celeron, one Intel i5 and one AMD Ryzen 7. I give the installer a 5 star rating although I would like to see some improvements made to

Re: Debian 11 Bullseye Setup Problems Error Report

Hello all valuable and constructive contributors :) 1) so thanks again for Debian it is just a lovely distro 2) forgot to mention: was using the net install ISOs for the test (hardware used server hp proliant g6 (amd64) (the raid is detected fine!)

Re: Debian 11 Bullseye Setup Problems Error Report

On Wed, Aug 18, 2021 at 10:42 AM admin4 wrote: > is there a Debian "testing" team? That is composed of everyone who uses Debian and especially those who decide to report an issue they found. > that does test setups of Debian ISOs on a bunch of different hardware with > priority on the most use

Re: Debian 11 Bullseye Setup Problems Error Report

On Wed, Aug 18, 2021 at 9:12 AM admin4 wrote: > cat feed.xml |nano # wohooo it works > > Too many errors from stdin You need to tell nano to load stdin: cat feed.xml | nano - > here we go admin4 into the spam database... for trying to report a problem > and improve a GNU Linux distribution. P

Re: Debian 11 Bullseye Setup Problems Error Report

Hello all, in short, * is there a Debian "testing" team?, that does test setups of Debian ISOs on a bunch of different hardware with priority on the most used CPUs like amd64 and i386, (free and non-free versions)), * before the ISOs spread across the world on all those nice download

Re: Debian 11 Bullseye Setup Problems Error Report

On Wed, Aug 18, 2021 at 12:25:58PM +0200, admin4 wrote: > Hello all, in short, > > * is there a Debian "testing" team?, that does test setups of Debian > ISOs on a bunch of different hardware with priority on the most used > CPUs like amd64 and i386, (free and non-free versions)), > *

Re: Debian 11 Bullseye Setup Problems Error Report

Hello Andrey, On 8/18/21 11:20 AM, Andrey Rahmatullin wrote: > On Wed, Aug 18, 2021 at 10:54:17AM +0200, admin4 wrote: Q1: (question1): why is there nor vi nor less included in the setup? > Both are included, less has Priority: standard, vim-tiny has Priority: > important. after setup is com

Re: Debian 11 Bullseye Setup Problems Error Report

On Wed, Aug 18, 2021 at 10:54:17AM +0200, admin4 wrote: > >> Q1: (question1): why is there nor vi nor less included in the setup? Both are included, less has Priority: standard, vim-tiny has Priority: important. > in theory yes... in reality try this: > > wget https://thesquareplanet.com/feed.xml

Re: Debian 11 Bullseye Setup Problems Error Report

Hello Paul, thanks for the timely reply. On 8/18/21 4:33 AM, Paul Wise wrote: > On Tue, Aug 17, 2021 at 10:39 AM admin4 wrote: > >> today was the day trying out the new Debian 11 with LTS (LTS is a reason for >> users consider switching to Ubuntu, so good choice there) > Debian 11/bullseye is no

Re: Debian 11 Bullseye Setup Problems Error Report

On Tue, Aug 17, 2021 at 10:39 AM admin4 wrote: > today was the day trying out the new Debian 11 with LTS (LTS is a reason for > users consider switching to Ubuntu, so good choice there) Debian 11/bullseye is not in LTS mode yet. Debian 10/buster will be in LTS mode in a year's time when regular

Debian 11 Bullseye Setup Problems Error Report

to report errors* S.1.) include a "report problem" button, that automatic generates a report to store away any error logs (and dmesg) that is generated during the setup on a usb drive, for easy upload to https://debian.org/report-a-problem <https://debian.org/report-problem> or: S2.

Bug#991657: ITP: golang-github-gravitational-trace -- Package for error handling and error reporting

: Package for error handling and error reporting This package is a dependency of github.com/vulcand/predicate Cheers,

Bug#985833: General: when searching repos I get an error message

Package: General Severity: normal X-Debbugs-Cc: 51lv3rb...@protonmail.com Dear Maintainer, After using the command apt search 'package_name' if the package can't be found I get the following error message, when the error happened and every other instance I have a good internet

Bug#985833: General: when searching repos I get an error message

Control: reassign -1 command-not-found Control: tags -1 + wontfix Hi Silverback! unable to open database file Traceback (most recent call last): File "/usr/share/command-not-found/CommandNotFound/util.py", line 23, in crash_guard callback() File "/usr/lib/command-not-found", line 90, in m

Processed: Re: Bug#985833: General: when searching repos I get an error message

Processing control commands: > reassign -1 command-not-found Bug #985833 [general] General: when searching repos I get an error message Bug reassigned from package 'general' to 'command-not-found'. Ignoring request to alter found versions of bug #985833 to the same

Bug#976153: ITP: libcerror -- library for cross-platform C error functions

* URL : https://github.com/libyal/libcerror * License : LGPL-3+ Programming Lang: C Description : library for cross-platform C error functions libcerror is a library for cross-platform C error functions. licerror is a build-dep for libluksde (https://github.com/libyal/lib

Bug#964940: marked as done (bugs.debian.org: After an upgrade and crash, the boot process say ACPI error: AE_NOT_FOUND. I think that the problem was an upgrade not completed on the bios machine or

Your message dated Mon, 31 Aug 2020 01:48:50 +0200 with message-id <20200830234849.jezb7nkmm63uy...@percival.namespace.at> and subject line Re: Bug#964940: bugs.debian.org: After an upgrade and crash, the boot process say ACPI error: AE_NOT_FOUND. I think that the problem was an upgra

Processed (with 1 error): reassign 969263 to general, reassign 968647 to firefox-esr, reassign 966004 to general ...

previously set > reassign 964940 general Bug #964940 [bugs.debian.org] bugs.debian.org: After an upgrade and crash, the boot process say ACPI error: AE_NOT_FOUND. I think that the problem was an upgrade not completed on the bios machine or similar. Bug reassigned from package 'bugs.debian.org&

Bug#648889: marked as done (/usr/include/features.h(323): catastrophic error: could not open source file "bits/predefs.h")

.h(323): catastrophic error: could not open source file "bits/predefs.h" to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If

Bug#962639: ITP: node-pruddy-error -- Prettify given error object

Package: wnpp Severity: wishlist Owner: Harley Swick X-Debbugs-CC: debian-devel@lists.debian.org * Package name : node-pruddy-error Version : 2.0.2 Upstream Author : Arnout Kazemier * URL : https://github.com/bigpipe/pruddy-error#readme * License : BSD Programming Lang: JavaScript Description

Bug#949951: ITP: h5cpp-compiler -- This LLVM/clang based C++ source code transformation tool automates the otherwise time consuming, error prone process of generating type descriptors for HDF5 Compoun

++ source code transformation tool automates the otherwise time consuming, error prone process of generating type descriptors for HDF5 Compound datatypes by building the AST of a given TU translation unit, and identifying all POD datatypes referenced from H5CPP operators/functions. The result is a

Debian Buster update error

update-initramfs: failed for /boot/initrd.img-4.19.0-6-amd64 with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-4.19.0-6-amd64 (--configure): installed linux-image-4.19.0-6-amd64 package post-installation script subprocess

Re: Error when running dh_dwz (actually an error when running dwz(1))

build package marisa from its git packaging repo > ( > https://salsa.debian.org/input-method-team/marisa/commit/f5ff598466266b230d68c9db9f8e31281604b7a6 > ). The following error will pop up when dwz is called: > > = > [...] >dh_dwz > dwz: debian/ruby-ma

Re: Error when running dh_dwz (actually an error when running dwz(1))

Hi Boyuan, > I don't have much experience of dealing with debugging symbols so any hints > would be appreciated. I would also be interested in this from my "Lintian hat" of: https://bugs.debian.org/931632#35 Best wishes, -- ,''`. : :' : Chris Lamb `. `'` la...@deb

Error when running dh_dwz (actually an error when running dwz(1))

n.org/input-method-team/marisa/commit/f5ff598466266b230d68c9db9f8e31281604b7a6 ). The following error will pop up when dwz is called: = [...] dh_dwz dwz: debian/ruby-marisa/usr/lib/x86_64-linux-gnu/ruby/2.5.0/marisa.so: Found compressed .debug_aranges section, not attemptin

Re: error messages of failing maintainer scripts

Ralf Treinen writes ("error messages of failing maintainer scripts"): > do we require that a maintainer script that exits with an error gives > a useful error message? I couldn't find anything about this in policy, > but I think that we should require, or at least

error messages of failing maintainer scripts

Hi, do we require that a maintainer script that exits with an error gives a useful error message? I couldn't find anything about this in policy, but I think that we should require, or at least recommend, useful error messages. A concrete example that we found in our current project

Processed (with 1 error): your mail

Processing commands for cont...@bugs.debian.org: > forcemerge 815037 922665 Bug #815037 [firmware-iwlwifi] "Microcode SW error detected. Restarting ..." every few seconds Unable to merge bugs because: package of #922665 is 'general' not 'firmware-iwlwifi' Fai

Bug#921171: ITP: liblogger-simple-perl -- Simran-Log-Log and Simran-Error-Error modules

: Perl Description : Simran-Log-Log and Simran-Error-Error modules This module provides an easier interface for functionality known from the Simran::Log::Log and Simran::Error::Error modules.

Processed (with 1 error): reassign bug

Processing commands for cont...@bugs.debian.org: > reassign 919045 linux-image-4.9.0-8-amd64 Bug #919045 [general] general: System frozen when either soft power-off or unplug USB3.0 harddisk after proper umount Bug reassigned from package 'general' to 'linux-image-4.9.0-8-amd64'. Ignoring request

Re: Reproducible builds error: libQt5Core.so.5: cannot open shared object file: No such file or directory

gt; The message is always the same: > > /usr/lib/qt5/bin/uic: error while loading shared libraries: > > libQt5Core.so.5: cannot open shared object file: No such file or > > directory [0] > > The (IMHO) misleading message is instead a linker bug, that I don't > thin

Re: Reproducible builds error: libQt5Core.so.5: cannot open shared object file: No such file or directory

On Mon, Jul 09, 2018 at 08:34:54PM +0200, Mattia Rizzolo wrote: > I agree. I haven't been mad about it only because it affects i386 only, > and we have 3 other architectures, I agree too. > but we'll need to figure a workaround > soon. and/or exclude these results from showing up on tracker.d.

  1   2   3   4   5   6   7   8   >