Bug#1072216: reuse: Rejects annotating .taprc file
On Thu, May 30, 2024 at 08:26:26AM -0400, Wesley Schwengle wrote: > I'm unable to use `reuse annotate' on a `.taprc' file (from node-tap). I did a bit of digging, this is resolved by commit 8b2282e87e2a47b84874e397380f3b649b94d3b0 in the repo at https://github.com/fsfe/reuse-tool. Which is available via tags v3.0.2 and v3.1.0a1. It would be much appreciated to bump the version to either of those tags. Cheers, Wesley
Bug#1072216: reuse: Rejects annotating .taprc file
Package: reuse
Version: 3.0.1-1
Severity: important
X-Debbugs-Cc: wes...@schwengle.net
Dear Maintainer,
I'm unable to use `reuse annotate' on a `.taprc' file (from node-tap).
$ cat .taprc
---
color: false
#coverage: false
disable-coverage: true
allow-incomplete-coverage: true
allow-empty-coverage: true
debug: false
reporter: tap
reporter-arg: []
include:
- t/*.@([mc]js|[jt]sx?)
$ reuse annotate --copyright "Wesley Schwengle" --license MIT --style python
.taprc
usage: reuse annotate [-h] [--copyright COPYRIGHT] [--license LICENSE]
[--contributor CONTRIBUTOR] [--year YEAR]
[--style
{applescript,aspx,bat,bibtex,c,csingle,css,f,ftl,handlebars,haskell,html,jinja,julia,lisp,m4,ml,f90,plantuml,python,rst,semicolon,tex,vst,vim,xquery}]
[--copyright-style
{spdx,spdx-c,spdx-symbol,string,string-c,string-symbol,symbol}]
[--template TEMPLATE] [--exclude-year]
[--merge-copyrights]
[--single-line | --multi-line] [--recursive]
[--no-replace]
[--force-dot-license | --fallback-dot-license |
--skip-unrecognised]
[--skip-existing]
path [path ...]
reuse annotate: error: The following files do not have a recognised file
extension. Please use --style, --force-dot-license, --fallback-dot-license, or
--skip-unrecognised:
.taprc
Please notice the --style python in the annotate function and thus should work.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (900, 'unstable'), (500, 'testing'), (100, 'experimental'), (10,
'stable-updates'), (10, 'stable-security'), (10, 'oldstable-security'), (10,
'oldoldstable'), (10, 'stable'), (10, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.7.9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages reuse depends on:
ii python3 3.11.8-1
ii python3-binaryornot 0.4.4+git20230412.ac4f56e+dfsg-2
ii python3-boolean 4.0-4
ii python3-debian 0.1.49
ii python3-jinja2 3.1.3-1
ii python3-license-expression 30.3.0-1
reuse recommends no packages.
reuse suggests no packages.
-- no debconf information
Bug#1068008: rustc: Please package rust 1.75 or higher
Hello all, On Tue, Apr 23, 2024 at 06:32:04AM +0900, Mike Hommey wrote: > On Mon, Apr 22, 2024 at 10:24:09PM +0200, Fabian Grünbichler wrote: > > > > > I am sorry to say that I don't expect us to be caught up with 1.75 > > (which is 5 trips through bin-NEW, one of them bigger than usual cause > > of the merge, and probably 20-40h of rebasing and testing work on my > > end) until at least the end of May :( I will make sure to include the > > requirements of thunderbird/firefox if things get stuck in NEW for too > > long. > > And by end of May, we'll be close to the upstream release of rustc 1.79... > > Is there anything we can do to make things better? Presumably, the > src:cargo merge should help here, at least a little (because cargo being > outdated has also been another source of recurring problems). I second the "Is there anything we can do the make things better?". Are there things we can do now already, that might speed up packaging rust to 1.77/1.78/1.79 besides waiting the t64 migration to be completed? I can offer a day a week in help if needed. Cheers, Wesley
Bug#1069114: apt installs package without confirmation
Package: apt Version: 2.9.1 Severity: important X-Debbugs-Cc: wes...@schwengle.net Dear Maintainer, Testing the new apt UI with freeplane showed a rather interesting bug. Apt will now install a package without confirmation if all the deps are met. I triggered this like so: apt install freeplane # shows confirmation y/n apt remove freeplane # shows confirmation y/n apt install freeplane # doesn't ask for confirmation and just starts installing See https://asciinema.org/a/3KX3A1hshGiHL0qx42QFsMJQ5 for the behavior in action. -- Package-specific info: -- (/etc/apt/preferences present, but not submitted) -- -- (/etc/apt/preferences.d/buster present, but not submitted) -- -- (/etc/apt/preferences.d/chrome present, but not submitted) -- -- (/etc/apt/preferences.d/docker-ce present, but not submitted) -- -- (/etc/apt/preferences.d/firewalld present, but not submitted) -- -- (/etc/apt/preferences.d/kernel present, but not submitted) -- -- (/etc/apt/preferences.d/libssl present, but not submitted) -- -- (/etc/apt/preferences.d/mozilla present, but not submitted) -- -- (/etc/apt/preferences.d/nodejs present, but not submitted) -- -- (/etc/apt/preferences.d/oldstable present, but not submitted) -- -- (/etc/apt/preferences.d/steam present, but not submitted) -- -- (/etc/apt/sources.list present, but not submitted) -- -- (/etc/apt/sources.list.d/docker.sources present, but not submitted) -- -- (/etc/apt/sources.list.d/endpoint-verification.sources present, but not submitted) -- -- (/etc/apt/sources.list.d/google-chrome.sources present, but not submitted) -- -- (/etc/apt/sources.list.d/mozilla.sources present, but not submitted) -- -- (/etc/apt/sources.list.d/nodesource.sources present, but not submitted) -- -- (/etc/apt/sources.list.d/signal-xenial.sources present, but not submitted) -- -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'testing'), (100, 'experimental'), (10, 'stable-updates'), (10, 'stable-security'), (10, 'oldstable-security'), (10, 'oldoldstable'), (10, 'stable'), (10, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.9-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages apt depends on: ii adduser 3.137 ii base-passwd 3.6.3 ii debian-archive-keyring 2023.4 ii gpgv2.2.40-3 ii libapt-pkg6.0t642.9.1 ii libc6 2.37-17 ii libgcc-s1 14-20240330-1 ii libgnutls30t64 3.8.5-2 ii libseccomp2 2.5.5-1 ii libstdc++6 14-20240330-1 ii libsystemd0 255.4-1+b1 Versions of packages apt recommends: ii ca-certificates 20240203 Versions of packages apt suggests: ii apt-doc 2.9.1 ii aptitude0.8.13-6 ii dpkg-dev1.22.6 ii gnupg 2.2.40-3 ii powermgmt-base 1.37 -- debconf-show failed
Bug#1068848: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1
Hi On Fri, Apr 12, 2024 at 09:04:23AM +0200, Jan Katins wrote: > Subject: cryptsetup: Fails to unlock the filesystem with missing libgcc_s.so.1 > Package: cryptsetup > Version: 2:2.7.2-1 > Severity: normal > > After a recent apt upgrade, my system failed to unlock. After a > ctrl-alt-del, I got to the console and there it showed an error about > libgcc_s.so.1 not available and aborting. > > Thankfully, I still had a other initrd around (I guess due to > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065698, yay for > bugs!). > > I snooped around in the source code a bit and found that libgcc_s > seems to be dlopened and is special cased: > https://salsa.debian.org/kernel-team/initramfs-tools/-/blob/master/hook-functions?ref_type=heads#L248-249 > (original bugreport: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950254). So my guess > is that nothing depends on libpthread either anymore, and this is the > case: `lsinitramfs initrd.img-6.7.9-amd64 |grep thread` shows no > libpthread (actually nothing). I fixed it now by installing a > update-initramfs hook (thanks to > https://groups.google.com/g/linux.debian.bugs.dist/c/4fi2HaOEC_M): I had the same issue a while back, because of the t64 transitioning I chaulked it up to that. I fixed it as described in Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958594 Cheers, Wesley
Bug#1068616: libanyevent-i3-perl: Version is outdated compared to the gitrepo
Package: libanyevent-i3-perl Version: 0.17-3 Severity: important Tags: upstream X-Debbugs-Cc: wes...@schwengle.net Dear Maintainer, See: https://github.com/i3/i3/issues/5986 The version of AnyEvent::I3 is 0.17 on CPAN while the git repo has version 0.18. Could you grab the version from the git repo? Many thanks! -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'testing'), (100, 'experimental'), (10, 'stable-updates'), (10, 'stable-security'), (10, 'oldstable-security'), (10, 'oldoldstable'), (10, 'stable'), (10, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.7-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libanyevent-i3-perl depends on: ii libanyevent-perl 7.170-2+b5 ii libjson-xs-perl 4.030-2+b3 ii perl 5.38.2-3.2 libanyevent-i3-perl recommends no packages. libanyevent-i3-perl suggests no packages. -- debconf-show failed
Bug#940151: unattended-upgrades: i configure my unattended-upgrade conf with following Origins:
Hi,
> Unattended-Upgrade::Allowed-Origins {
> "o=Debian, a=stable";
> "o=Debian Backports, a=buster-backports"; };
The problem with the example is that it uses a=CODENAME-backports and not
a=stable-backports. The a= should be n= or codename= when using the CODENAME.
I've created PR https://github.com/mvo5/unattended-upgrades/pull/359 for this.
Cheers,
Wesley
Bug#1068047: Suspicious commit merged in 2021 from account responsible for xz backdoor
On Fri, Mar 29, 2024 at 07:24:13PM -0700, Russ Allbery wrote: > So far it looks like no one has been able to figure out an obvious way > for this to be exploitable, but I wanted to make sure that you were > aware of this upstream issue: > > https://github.com/libarchive/libarchive/pull/1609 > > The author of this commit is the same GitHub account that was used to > create the xz backdoor. Upstream has merged a revert of this change at: > > https://github.com/libarchive/libarchive/pull/2101 > > It may be worth expediting getting this change into Debian in case the > potential attacker knows something that we don't. However, I don't have > any reason to currently believe that this is a security vulnerability, > so I've kept the severity at important and not applied the security tag. I also noticed this, I send an e-mail to secur...@debian.org about it, 921847da-a715-42c4-b87d-e8a1f0fb5...@schwengle.net. FWIW, this also impacts Debian stable. The commit can be found in tags: v3.7.2 v3.7.1 v3.7.0 v3.6.2 v3.6.1 v3.6.0. Debian stable ships 3.6.2-1 Cheers, Wesley
Bug#1068008: rustc: Please package rust 1.75 or higher
Package: rustc Version: 1.70.0+dfsg1-9 Severity: wishlist X-Debbugs-Cc: wes...@schwengle.net Dear Maintainer, I was trying to build a rust package from source when I noticed they use traits. Async traits are supported as of 1.75. It would be beneficial to Debian that we can start developing rust with these traits. Currently upstream sits at 1.77.x, it would be nice if we could get at least to 1.75 , but 1.77.x would be preferred. https://blog.rust-lang.org/2023/12/21/async-fn-rpit-in-traits.html Many thanks and cheers, Wesley -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'testing'), (100, 'experimental'), (10, 'stable-updates'), (10, 'stable-security'), (10, 'oldstable-security'), (10, 'oldoldstable'), (10, 'stable'), (10, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.7-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages rustc depends on: ii binutils 2.42-4 ii gcc 4:13.2.0-7 ii libc6 2.37-15.1 ii libc6-dev [libc-dev] 2.37-15.1 ii libgcc-s1 14-20240315-1 ii libstd-rust-dev 1.70.0+dfsg1-9 Versions of packages rustc recommends: ii cargo0.70.1+ds1-3 ii llvm-16 1:16.0.6-24 Versions of packages rustc suggests: ii clang-16 1:16.0.6-24 pn lld-16 -- debconf-show failed
Bug#847983: apt: Sid Apt-Pinning ignoring other Release than Experimental
On Tue, Dec 13, 2016 at 08:43:35AM +, Adam D. Barratt wrote: > On 2016-12-12 20:25, Perl wrote: > >* What led up to the situation? > >I noticed, since long time ago, that I was not anymore able to use > >Apt-Pinning for installing packages from Stable and Testing Releases. > >* What exactly did you do (or not do) that was effective (or > > ineffective)? > > Everytime I try to use "APT-Pinning", I do not get what I want. > > Even if I try /testing or -t testing, or any Release other than > > Experimental, I only get error or Experimental list of packages. > > Finally, apt-cache policy only return Sid and Experimental > > packages. > >* What was the outcome of this action? > > If I try > > "apt-cache show -t testing linux-image-amd64" > > OR > > "apt-cache show linux-image-amd64/testing" > > I get this with apt-get: > > E: Release 'testing' for 'linux-image-amd64' was not found > > E: No packages found > > Well, the only testing sources.list entries listed in your report are: > > > #Testing > > deb-src http://ftp.fr.debian.org/debian/ testing main non-free contrib > > deb-src http://ftp2.fr.debian.org/debian/ testing main contrib non-free > > So I'm not sure where you're expecting apt to find information about > *binary* packages in testing from. I agree with this statement and I think we can close this bug because of it. Cheers, Wesley
Bug#1066856: apt: please update the URLs in the man pages
Hi, > In the apt-cache(8) man page: > > http://www.research.att.com/sw/tools/graphviz/ gives a "Page Not Found" > error. > > http://rw4.cs.uni-sb.de/users/sander/html/gsvcg1.html should be > changed to > https://www.rw.cdl.uni-saarland.de/people/sander/private/html/gsvcg1.html I fixed these URI's in git, see merge commit 1c1d8b26f067e7a1f7740718c0ded84ec8a386cb and i I didn't put closes: #number in one of the commit messages. Anyways, its fixed and released in apt 2.7.14. Thanks for reporting the bug. Cheers, Wesley
Bug#1067472: firefox-esr: Firefox and Firefox ESR should implement update-alternatives and provide a seperate binary
Package: firefox-esr
Version: 115.9.0esr-2
Severity: wishlist
X-Debbugs-Cc: wes...@schwengle.net
Dear Maintainer,
I went digging for how firefox works on Debian because I want to make a partial
switch from Google Chrome to firefox. There are some things that could be
improved I think. Mainly by starting to make use of update-alternatives.
I want to start of with by saying this bug is more or less a combination of
bugs #1001724 and #1033594. They both address why I have this wish, for
different reasons.
/usr/bin/firefox is a wrapper script to which looks for $FIREFOX.real, where
$FIREFOX is assuming, firefox. It looks for command firefox, which may be
something else if the user has a wrapper script itself in their PATH and this
than misses its target, #1001724 in short.
The easy way to solve this is IMO a update-alternatives group for firefox like
Google Chrome does (via the Google repo). They have an update-alternatives
group, aptly named `google-chrome', which provides `/usr/bin/google-chrome' and
as a user you can change this to have google-chrome-{unstable,beta,stable} as
your google-chrome. Instead of the wrapper script, firefox-esr should provide
firefox-esr. The firefox package should provide firefox-stable (or similar) and
install itself at a higher level than firefox-esr. This way the firefox binary
"overrides" the ESR. At least, that is my take on it, feel free to swap the
priorities around.
It would be nice if the upstream firefox packages, also adhere to this, eg,
firefox-nightly is already installed as firefox-nightly, but doesn't add an
update-alternatives.
Another reason, besides the wrapper script, is that firefox doesn't really put
profiles in a different path, eg, `~/.config/firefox-nightly',
`~/.config/firefox', etc etc. They however in their compatibility.ini, eg in
`~/.mozilla/firefox/rqowq6li.default-esr/compatibility.ini', you can see a
LastPlatformDIr, which is for the nightly version:
LastPlatformDir=/usr/lib/firefox-esr
Now, when I run `readlink -m /usr/bin/firefox-nightly' it returns
`/usr/lib/firefox-nightly/firefox'. The LastPlatformDir is the dirname of the
binary. Now, with a propper update-alternative I can also do this on the binary
`/usr/bin/firefox', as this will point to `/etc/alternatives/firefox', which in
turn links to `/usr/bin/firefox-nightly', which is
`/usr/lib/firefox-nightly/firefox'. I can do a little bit of magic with some
shell scripts to startup firefox profiles for different versions.
The wrapper script blocks this from working:
$ readlink -m /usr/bin/firefox
/usr/bin/firefox
I hope to see this wish become reality :)
Cheers,
Wesley
-- Package-specific info:
-- Extensions information
Name: Add-ons Search Detection
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Bing
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Dark theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled
Name: DuckDuckGo
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Firefox Alpenglow theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled
Name: Firefox Screenshots
Location: /usr/lib/firefox-esr/browser/features/screensh...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: Form Autofill
Location: /usr/lib/firefox-esr/browser/features/formautof...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: Google
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Light theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled
Name: Picture-In-Picture
Location: /usr/lib/firefox-esr/browser/features/pictureinpict...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: System theme — auto theme
Location: /usr/lib/firefox-esr/omni.ja
Package: firefox-esr
Status: enabled
Name: Web Compatibility Interventions
Location: /usr/lib/firefox-esr/browser/features/webcom...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: WebCompat Reporter
Location:
/usr/lib/firefox-esr/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox-esr
Status: user-disabled
Name: Wikipedia (en)
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
-- Addons package information
ii firefox-esr115.9.0esr-2 amd64Mozilla Firefox web browser -
Extended Support Release (ESR)
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (900, 'unstable'), (500, 'testing'), (100, 'experimental'), (10,
'stable-updates'), (10, 'stable-security'), (10, 'oldstable-security'), (10,
'oldoldstable'), (10, 'stable'), (10, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.7.7-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE,
Bug#1067441: chromium: Unable to sync profile
Package: chromium Version: 122.0.6261.128-1 Severity: important X-Debbugs-Cc: wes...@schwengle.net Dear Maintainer, I've started up Chromium and want to sync my Google account. * Create new profile * Login to Google (succesfully) Within Google.com you are known, myaccount.google.com shows your details * Click on the profile button of your browser * Clock on "Turn sync on" * Follow the login sequence * Notice error in the console: [29150:29150:0321/112903.702701:ERROR:turn_sync_on_helper.cc(256)] Cannot turn Sync On for invalid account. [29150:29150:0321/112950.431580:ERROR:turn_sync_on_helper.cc(256)] Cannot turn Sync On for invalid account. Doing the same action with the builds of Google itself everything works fine, tested this with the browsers listed below. The bug is also present on bookworm, where I tested it with 122.0.6261.128-1~deb12u1 Cheers, Wesley google-chrome-stable: Installed: 123.0.6312.58-1 Candidate: 123.0.6312.58-1 Version table: *** 123.0.6312.58-1 900 900 https://dl.google.com/linux/chrome/deb stable/main amd64 Packages 100 /var/lib/dpkg/status google-chrome-beta: Installed: 123.0.6312.46-1 Candidate: 123.0.6312.46-1 Version table: *** 123.0.6312.46-1 900 900 https://dl.google.com/linux/chrome/deb stable/main amd64 Packages 100 /var/lib/dpkg/status google-chrome-unstable: Installed: 124.0.6356.2-1 Candidate: 124.0.6356.2-1 Version table: *** 124.0.6356.2-1 900 900 https://dl.google.com/linux/chrome/deb stable/main amd64 Packages 100 /var/lib/dpkg/status -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'testing'), (100, 'experimental'), (10, 'stable-updates'), (10, 'stable-security'), (10, 'oldstable-security'), (10, 'oldoldstable'), (10, 'stable'), (10, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.7-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages chromium depends on: ii chromium-common 122.0.6261.128-1 ii libasound2t641.2.11-1+b1 ii libatk-bridge2.0-0t642.51.90-4 ii libatk1.0-0t64 2.51.90-4 ii libatomic1 14-20240315-1 ii libatspi2.0-0t64 2.51.90-4 ii libc62.37-15.1 ii libcairo21.18.0-2 ii libcups2t64 2.4.7-1.2+b1 ii libdbus-1-3 1.14.10-4+b1 ii libdouble-conversion33.3.0-1+b1 ii libdrm2 2.4.120-2 ii libevent-2.1-7t642.1.12-stable-8.1+b1 ii libexpat12.6.2-1 ii libflac12t64 1.4.3+ds-2.1 ii libfontconfig1 2.15.0-1.1 ii libfreetype6 2.13.2+dfsg-1+b2 ii libgbm1 24.0.3-1 ii libgcc-s114-20240315-1 ii libglib2.0-0t64 2.78.4-5 ii libgtk-3-0t64 [libgtk-3-0] 3.24.41-3 ii libjpeg62-turbo 1:2.1.5-2+b2 ii libjsoncpp25 1.9.5-6+b2 ii liblcms2-2 2.14-2+b1 ii libminizip1t64 1:1.3.dfsg-3.1 ii libnspr4 2:4.35-1.1+b1 ii libnss3 2:3.99-1 ii libopenh264-72.4.1+dfsg-1 ii libopenjp2-7 2.5.0-2+b3 ii libopus0 1.4-1+b1 ii libpango-1.0-0 1.52.1+ds-1 ii libpng16-16t64 1.6.43-3 ii libpulse016.1+dfsg1-3+b1 ii libsnappy1v5 1.1.10-1+b1 ii libstdc++6 14-20240315-1 ii libwebp7 1.3.2-0.4+b1 ii libwebpdemux21.3.2-0.4+b1 ii libwebpmux3 1.3.2-0.4+b1 ii libwoff1 1.0.2-2+b1 ii libx11-6
Bug#1067060: kde-spectacle: Typo in man page, fixed upstream
Package: kde-spectacle Severity: minor X-Debbugs-Cc: wes...@schwengle.net Dear Maintainer, someone on #debian on libera noticed a small typo in the man page. It is fixed upstream: https://github.com/KDE/spectacle/commit/992d197d34a0f04ac259e34b2e1e7a821eaff519 Cheers, Wesley -- System Information: Debian Release: 12.5 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'oldstable-security'), (500, 'stable'), (10, 'oldoldstable'), (10, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-18-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kde-spectacle depends on: pn kio ii libc6 2.36-9+deb12u4 pn libkf5configcore5 pn libkf5configgui5 pn libkf5configwidgets5 pn libkf5coreaddons5 pn libkf5dbusaddons5 pn libkf5globalaccel-bin pn libkf5globalaccel5 pn libkf5guiaddons5 pn libkf5i18n5 pn libkf5kiocore5 pn libkf5kiogui5 pn libkf5kiowidgets5 pn libkf5newstuff5 pn libkf5notifications5 pn libkf5purpose-bin pn libkf5purpose5 pn libkf5service-bin pn libkf5service5 pn libkf5waylandclient5 pn libkf5widgetsaddons5 pn libkf5windowsystem5 pn libkf5xmlgui5 pn libkimageannotator0 pn libqt5core5a pn libqt5dbus5 pn libqt5gui5 | libqt5gui5-gles pn libqt5printsupport5 pn libqt5widgets5 pn libqt5x11extras5 ii libstdc++612.2.0-14 pn libxcb-cursor0 pn libxcb-image0 pn libxcb-util1 ii libxcb-xfixes01.15-1 ii libxcb1 1.15-1 pn qdbus-qt5 kde-spectacle recommends no packages. kde-spectacle suggests no packages.
Bug#626251: apt-get source gets confused by multiple versions in a list
Hi all, I'm looking at bug reports to try and clean some up and I noticed this one. I think we can close it, see my reasoning below your message and if you don't agree feel free to reopen the bug. On Tue, May 10, 2011 at 08:14:24AM +, Simon Cozens wrote: > After upgrading from lenny to squeeze, trying to build packages from unstable, > apt-get source sometimes works: > > simon@dealer ~ % apt-get source apt > ... > Get:1 http://ftp.de.debian.org/debian/ unstable/main apt 0.8.14.1 (dsc) > [1,363 B] > ... > > (That is, correctly, fetching the unstable version.) And sometimes fails > spectacularly: > > simon@dealer ~ % apt-get source duplicity > ... > E: Ignore unavailable version '0.6.08b-1' of package 'duplicity' > E: Unable to find a source package for duplicity > > Wait, 0.6.08b-1 is the *stable* version. I don't want the stable version, > that's the whole point. Oh, maybe I need to say "-t unstable": > > simon@dealer ~ % apt-get -t unstable source duplicity > Reading package lists... Done > Building dependency tree > Reading state information... Done > E: Ignore unavailable target release 'unstable' of package 'duplicity' > E: Unable to find a source package for > > But clearly there is an entry for duplicity in the sources list: > > simon@dealer ~ % grep duplicity_ /var/lib/apt/lists/*Sources > a35f37d3a519b51be903c3f71588f487 1032 duplicity_0.6.12-1.dsc > 9b84c984054550bbb2ba29b553567b7b 296045 duplicity_0.6.12.orig.tar.gz > 17ecd266d7b7307512ab969c8fbd2669 13272 duplicity_0.6.12-1.diff.gz > ... > > In fact, there are *two different versions*: > > ... > b73a68286bc79140aab950ed13747a49 1033 duplicity_0.6.13-1.dsc > b3d627f35fc527b00121925840d5cca7 296955 duplicity_0.6.13.orig.tar.gz > ee420e83778e7a8dda731ed848cf84ab 13635 duplicity_0.6.13-1.diff.gz > > Obviously that's not an ideal scenario but apt-get source should *not* > throw its hands up and say "obviously you wanted the stable version which > I can't find". We have multiple source files for dovecot: $ grep dovecot_ /var/lib/apt/lists/*Sources | grep dsc /var/lib/apt/lists/deb.debian.org_debian_dists_stable_main_source_Sources: c305facad2b3785986e470397df410f3 4166 dovecot_2.3.19.1+dfsg1-2.1.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_stable_main_source_Sources: 6e55d7ce048a613f00562e32a51e19d6503c9da9ae5d34d5692cca636c518d2b 4166 dovecot_2.3.19.1+dfsg1-2.1.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources: 3d1fa5b58612668cb578df2e04f36002 4076 dovecot_2.3.21+dfsg1-2.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_testing_main_source_Sources: 33a22aa897249f9600e7fdf95a4e96c11611ba3385cb8a5f8c87561d33c67f06 4076 dovecot_2.3.21+dfsg1-2.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources: 3d1fa5b58612668cb578df2e04f36002 4076 dovecot_2.3.21+dfsg1-2.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources: 33a22aa897249f9600e7fdf95a4e96c11611ba3385cb8a5f8c87561d33c67f06 4076 dovecot_2.3.21+dfsg1-2.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources: ca294cabc50b51d197c2b33777073078 4090 dovecot_2.3.21+dfsg1-3.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources: 13dd3e6c39b752f0925ec880ff4c1d807b6346a22bea1c4677dd6fd978f6ae74 4090 dovecot_2.3.21+dfsg1-3.dsc $ grep dovecot_ /var/lib/apt/lists/*Sources | grep unstable | grep dsc /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources: 3d1fa5b58612668cb578df2e04f36002 4076 dovecot_2.3.21+dfsg1-2.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources: 33a22aa897249f9600e7fdf95a4e96c11611ba3385cb8a5f8c87561d33c67f06 4076 dovecot_2.3.21+dfsg1-2.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources: ca294cabc50b51d197c2b33777073078 4090 dovecot_2.3.21+dfsg1-3.dsc /var/lib/apt/lists/deb.debian.org_debian_dists_unstable_main_source_Sources: 13dd3e6c39b752f0925ec880ff4c1d807b6346a22bea1c4677dd6fd978f6ae74 4090 dovecot_2.3.21+dfsg1-3.dsc We try to get the source package: $ apt-get source dovecot Reading package lists... Done NOTICE: 'dovecot' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/debian/dovecot.git Please use: git clone https://salsa.debian.org/debian/dovecot.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 9598 kB of source archives. Get:1 https://deb.debian.org/debian unstable/main dovecot 1:2.3.21+dfsg1-3 (dsc) [4090 B] $ apt-get source dovecot/unstable Reading package lists... Done Selected version '1:2.3.21+dfsg1-3' (unstable) for dovecot NOTICE: 'dovecot' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/debian/dovecot.git Please use: git clone https://salsa.debian.org/debian/dovecot.git to retrieve the latest
Bug#607999: 'apt-get source $src' fails
Hi all, On Wed, Feb 28, 2024 at 11:01:53AM +0800, Tianyu Chen wrote: > In apt-get(8): > The arguments are interpreted as binary and source package names. See the > --only-source option if you want to change that. > I think this bug should be closed now? > Best regards, > Tianyu Chen @ deepin I think this bug can be closed indeed. In apt 2.6.1 (bookworm) 2.7.13+b1 (sid) this seems to be fixed. On bookworm: $ apt-get source --only-source dovecot -t oldstable Reading package lists... Done Selected version '1:2.3.13+dfsg1-2+deb11u1' (oldstable) for dovecot NOTICE: 'dovecot' packaging is maintained in the 'Git' version control system at: $ apt-get source --only-source dovecot Reading package lists... Done NOTICE: 'dovecot' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/debian/dovecot.git Please use: git clone https://salsa.debian.org/debian/dovecot.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 9499 kB of source archives. Get:1 https://deb.debian.org/debian bookworm/main dovecot 1:2.3.19.1+dfsg1-2.1 (dsc) [4166 B] $ apt-get source dovecot Reading package lists... Done NOTICE: 'dovecot' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/debian/dovecot.git Please use: git clone https://salsa.debian.org/debian/dovecot.git to retrieve the latest (possibly unreleased) updates to the package. Skipping already downloaded file 'dovecot_2.3.19.1+dfsg1-2.1.dsc' Need to get 9495 kB of source archives. Get:1 https://deb.debian.org/debian bookworm/main dovecot 1:2.3.19.1+dfsg1-2.1 (tar) [1637 kB] On sid: $ apt-get source dovecot -t testing Reading package lists... Done Selected version '1:2.3.21+dfsg1-2' (testing) for dovecot NOTICE: 'dovecot' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/debian/dovecot.git apt-get source dovecot-core Reading package lists... Done Picking 'dovecot' as source package instead of 'dovecot-core' NOTICE: 'dovecot' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/debian/dovecot.git Please use: git clone https://salsa.debian.org/debian/dovecot.git to retrieve the latest (possibly unreleased) updates to the package. Skipping already downloaded file 'dovecot_2.3.21+dfsg1.orig-pigeonhole.tar.gz' Need to get 7910 kB of source archives. Get:1 https://deb.debian.org/debian unstable/main dovecot 1:2.3.21+dfsg1-3 (dsc) [4090 B] $ apt-get source --only-source dovecot -t stable Reading package lists... Done Selected version '1:2.3.19.1+dfsg1-2.1' (stable) for dovecot NOTICE: 'dovecot' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/debian/dovecot.git $ apt-get source dovecot-core -t stable Reading package lists... Done Picking 'dovecot' as source package instead of 'dovecot-core' Selected version '1:2.3.19.1+dfsg1-2.1' (stable) for dovecot I think this all works as intended. If you feel this is incorrect, feel free to reopen the bug. Cheers, Wesley
Bug#1043465: reportbug: apt install produces errors when run from a non-existing directory
Control: reassign 1.21.22 debconf On Fri, Aug 11, 2023 at 04:07:11PM +, t3atwv+9rzw960a1ydj0@cs.email wrote: > Dear Maintainer, > > It doesn't matter which package you try to install, I'm using 'hello' as an > example of a very simple package with no dependencies. > > If you try to run an `apt install` command while you are in a directory that > has been deleted, you will get error messages. > > Example command: > $ mkdir /tmp/hello; cd /tmp/hello; rmdir /tmp/hello; sudo apt install hello > > You get an output that includes these lines: > sh: 0: getcwd() failed: No such file or directory > sh: 0: getcwd() failed: No such file or directory > sh: 0: getcwd() failed: No such file or directory > sh: 0: getcwd() failed: No such file or directory > sh: 0: getcwd() failed: No such file or directory > cannot fetch initial working directory: No such file or directory at > /usr/sbin/dpkg-preconfigure line 73. > cannot fetch initial working directory: No such file or directory at > /usr/sbin/dpkg-preconfigure line 159. > > The package installs successfully, but the messages are still not something > the user should see. This is actually a debconf bug as the warnings/errors are emitted by /usr/sbin/dpkg-preconfigure. I don't fully agree that this is a bug but I'll let the debconf folks decide over that. I think it is quite useful to have this information in case things would go wrong because being in a non-existent directory might not be a normal situation. The reproduction path can be slightly adjusted to: mkdir /tmp/hello; cd /tmp/hello; rmdir /tmp/hello; sudo /usr/sbin/dpkg-preconfigure hello I can verify that the behavior is present on bookworm and unstable. Cheers, Wesley
Bug#1065831: document package specifiers for `upgrade`
On Wed, Mar 13, 2024 at 09:44:02AM +0100, Miguel Angel Rojas wrote: > Hi there, > > > If "apt upgrade" is saying that it removes packages, that is a bug, yes. > > @david: it is not a bug, apparently. > > To put everything in a nutshell: > >- "apt upgrade" can remove packages No. Without a package as an argument it won't. >- "apt upgrade" accepts specific packages to be upgraded To be installed if not installed yet, removed, downgraded or upgraded if already installed depending on your arguments. For example `apt upgrade foo- bar+ baz=version toto/archive' will remove foo, add bar, install, up- or downgrade baz and the same for toto and it will upgrade packages where it can. > Therefore, this behaviour is expected and documentation needs to be > modified. > > In the meantime, while the documentation is modified, can some developer > provide some explanation to the current "apt upgrade" behaviour? (*) Julian provided an explanation in #74, 20240312113620.ga1944...@debian.org > whereas `apt upgrade foo` first does the normal install argument handling and > then runs an upgrade, so `foo` could also be a new package that is not > currently installed to hint the solver if it is unable to find a solution. > (*) I'm a bit confused because I don't know which of the people involved in > this bug are actually a developer of the apt package ;) I'm not a Debian developer, never been. Just someone who submitted a patch or two. Cheers, Wesley
Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)
On Tue, Mar 12, 2024 at 11:40:01AM +0100, Julian Andres Klode wrote: > On Mon, Mar 11, 2024 at 10:12:33PM -0400, Wesley Schwengle wrote: > > I do not know what the bug here is, it could be one of these options: > > > > 1) apt-get/apt upgrade accepts packages to upgrade where the docs state it > >doesn't. The behaviour needs to change to not accept packages. > > > > 2) apt-get/apt upgrade accepts packages and removes packages to satisfy deps > >where the docs state it doesn't. The behaviour need to change to not > > remove > >any packages. There is a small edge case where you can say: `apt upgrade > > foo > >bar-'. Technically, it shouldn't remove packages, yet you want and > > instruct > >it to remove bar. > > The behavior is correct if potentially unexpected, but it should be > documented better. Thanks, it was option 3) Works as intended, documentation needs to be updated. > > FWIW, aptitude does not remove packages where you call `aptitude > > safe-upgrade > > foo'. It does remove packages when you call `aptitude full-upgrade foo'. It > > also removes bar when you run `aptitude safe-upgrade foo bar-'. > > That is an entirely different command; `aptitude safe-upgrade foo` > upgrades (only) `foo`, whereas `apt upgrade foo` first does the normal > install argument handling and then runs an upgrade, so `foo` could also > be a new package that is not currently installed to hint the solver if > it is unable to find a solution. Ahhh. I was under the impression that they had a similar intent. On a related note: While debugging I also noticed apt's update and apt-get's update are also slightly different. apt-get will not allow for new packages to be installed whereas apt's version does allow this. You get apt's behaviour with the --with-new-pkgs switch in apt-get's version of upgrade. Cheers, Wesley
Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)
On Mon, Mar 11, 2024 at 11:32:24PM +0100, Miguel Angel Rojas wrote: > > I see. It looks like `apt upgrade ' behaves as `apt install > > '. Which (to me) is unexpected behaviour, as the man page is > quite > >clear on its behaviour (man 8 apt-get): > > Well, clearly it shouldn’t. To begin with, “apt install” should mark a > package as manual installed while “apt upgrade” shouldn’t (my assumption). > And you’re right that “apt install” can remove a package if needed to > satisfy dependencies. > > On top of that, documentation clearly states that “apt upgrade” should not > remove any package, but it does when you specify an individual package to > upgrade. > > If this is not the expected behavior, maybe this is a bug (unless I am > missing something here). I do not know what the bug here is, it could be one of these options: 1) apt-get/apt upgrade accepts packages to upgrade where the docs state it doesn't. The behaviour needs to change to not accept packages. 2) apt-get/apt upgrade accepts packages and removes packages to satisfy deps where the docs state it doesn't. The behaviour need to change to not remove any packages. There is a small edge case where you can say: `apt upgrade foo bar-'. Technically, it shouldn't remove packages, yet you want and instruct it to remove bar. FWIW, aptitude does not remove packages where you call `aptitude safe-upgrade foo'. It does remove packages when you call `aptitude full-upgrade foo'. It also removes bar when you run `aptitude safe-upgrade foo bar-'. I'll leave this for the maintainers to answer. Cheers, Wesley
Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)
On Mon, Mar 11, 2024 at 10:48:53PM +0100, Miguel Angel Rojas wrote: > Hi Wesley, David, > > > You keep saying `apt upgrade' yet your command was `apt full-upgrade'. > > Yes, maybe it didn't express itself properly. After your suggestion about > not using "apt full-upgrade" during this t64 migration, I followed your > advice and used only "apt upgrade" for individual upgrades. I was referring > to this comment you made below: Ah, and I meant upgrading as individually installing packages ala: `apt install foo'. I get the confusion now :) > Now, If I type"apt upgrade" doesn't give me any option to update anything: Ok, that is expected behaviour. > But, in some situations, as you mentioned, individual package upgrades can > work and remove some problems. So what I did was to try some "apt upgrade" > on individual packages from that list. This time I try the ppp package: > > # apt upgrade ppp > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Calculating upgrade... Done > The following packages were automatically installed and are no longer > required: > linux-headers-6.6.15-amd64 linux-headers-6.6.15-common > linux-image-6.6.15-amd64 linux-kbuild-6.6.15 > Use 'apt autoremove' to remove them. > The following packages will be REMOVED: <--- PACKAGE TO BE REMOVED > libpcap0.8 > The following NEW packages will be installed: > libpcap0.8t64 > > [snip] > > The following packages will be upgraded: > ppp > 1 upgraded, 1 newly installed, 1 to remove and 22 not upgraded. > Need to get 511 kB of archives. > After this operation, 15.4 kB disk space will be freed. > , > > As you can see here, I'm typing "apt upgrade ppp" and it removes a package > in this case: libpcap0.8 (sometimes more packages are removed). > > Which is good, because libpcap0.8 is replaced by libpcap0.8t64 (as expected > in this t64 migration) but "apt upgrade ppp" is REMOVING a package (which > contradicts the specification). I see. It looks like `apt upgrade ' behaves as `apt install '. Which (to me) is unexpected behaviour, as the man page is quite clear on its behaviour (man 8 apt-get): upgrade upgrade is used to install the newest versions of **all** (emphasis mine) packages currently installed on the system from the sources enumerated in /etc/apt/sources.list. It shouldn't accept the arguments you feed it, apt-get has the same "feature". And with an install you do remove packages to satisfy the deps. Cheers, Wesley
Bug#1066056: vokoscreen-ng: Change depends to allow pipewire/pipewire-pulse
Package: vokoscreen-ng Version: 3.7.0-1 Severity: wishlist X-Debbugs-Cc: wes...@schwengle.net Dear Maintainer, apt-cache depends vokoscreen-ng [snip] Recommends: pulseaudio [snip] Could you add an OR here with pipewire and/or pipewire-pulse? Many thanks! -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'experimental'), (500, 'testing'), (10, 'stable-updates'), (10, 'stable-security'), (10, 'oldstable-security'), (10, 'oldoldstable'), (10, 'stable'), (10, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vokoscreen-ng depends on: ii gstreamer1.0-plugins-good 1.24.0-1 ii libc6 2.38-6 ii libgcc-s1 14-20240303-1 ii libglib2.0-0t64 [libglib2.0-0] 2.78.4-4 ii libgstreamer1.0-0 1.24.0-1 ii libpulse0 16.1+dfsg1-3+b1 ii libqt5core5t64 [libqt5core5a] 5.15.10+dfsg-7.2 ii libqt5dbus5t64 [libqt5dbus5]5.15.10+dfsg-7.2 ii libqt5gui5t64 [libqt5gui5] 5.15.10+dfsg-7.2 ii libqt5multimedia5 5.15.10-2+b2 ii libqt5network5t64 [libqt5network5] 5.15.10+dfsg-7.2 ii libqt5widgets5t64 [libqt5widgets5] 5.15.10+dfsg-7.2 ii libqt5x11extras55.15.10-2+b1 ii libstdc++6 14-20240303-1 ii libwayland-client0 1.22.0-2.1+b1 ii libx11-62:1.8.7-1 Versions of packages vokoscreen-ng recommends: ii gstreamer1.0-libav 1.24.0-1 ii gstreamer1.0-pulseaudio1.24.0-1 ii libqt5multimedia5-plugins 5.15.10-2+b2 pn pulseaudio Versions of packages vokoscreen-ng suggests: ii gstreamer1.0-plugins-bad 1.24.0-1 ii gstreamer1.0-plugins-ugly 1.24.0-1 ii gstreamer1.0-vaapi 1.24.0-1 ii intel-media-va-driver 24.1.0+dfsg1-1 -- no debconf information
Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)
Hi Miguel, On Mon, Mar 11, 2024 at 05:09:47PM +0100, Miguel Angel Rojas wrote: > > I do not know, at times I'm also wondering why it doesn't do it, but I > didn't > > take time to look at the code to understand what the resolver is doing. > Also, > > it was sort of expected. I think we can probably solve this is a more > > controlled manner. With the current t64 transitioning in unstable it is > > difficult to track down. Many updates so the situation now may differ > from the > > situation in an hour from now. > > Yes, it is confusing for me too. Without considering this t64 migration, > “apt upgrade” should *NOT* remove any package (just upgrading a package to > a newer version or install new dependencies). But it is removing packages > right now! i.e. again, with this t64 migration, it makes the old libraries > to be uninstalled and install the new *t64 version. > > Any thoughts why “apt upgrade” is removing packages even when documentation > says it shouldn’t? or is it a bug? You keep saying `apt upgrade' yet your command was `apt full-upgrade'. As said earlier, full-upgrade does indeed remove packages to be able to perform an upgrade. I haven't seen `apt upgrade' do that. So I cannot comment on apt doing something wrong when it isn't :) Cheers, Wesley
Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)
Hello Miguel, On Mon, Mar 11, 2024 at 09:50:12AM +0100, Miguel Angel Rojas wrote: > >This problem isn't because of apt, the problem is that gdb-minimal/gdb > > dependencies cannot be satified. A full-upgrade is the equivalent of a > > dist-upgrade which will remove packages to resolve the dependencies. The > > problem you are facing is the t64 transition[1][2] where not all packages > are > > transitioned. > > I haven't detected any "gdb | gdb-minimal dependencies that can't be > satisfied at this point. Everything seems to be OK with those packages. No, there is (or was) something going on with the dependencies of gdm-minimal for sure. I think it is related to libdebuginfod1, which has a t64 variant. This one has a dependency to libelf1 and libdw1. Now the libdebuginfod1t64 depends on libelf1t64 and libdw1t64. These two replace libelf1 and libdw1, the former having a relative high count of reverse dependencies. > > My advice to you is: don't expect full-upgrade to work until the > transitioning > > is done. > > You nail it here! I have managed to upgrade package by package but it is a > tedious process until the whole transition is completed. Some of them yes, but often after doing one, you can use `apt upgrade' to see if it resolved other problems (which in my case it does from time to time). > But "apt upgrade" > should not remove any packages according to its documentation (man apt) That is correct, but you were executing full-upgrade: > > On Sun, Mar 10, 2024 at 02:13:34PM +0100, Miguel Angel wrote: > > > > > # apt full-upgrade > > > Reading package lists... Done > > > Building dependency tree... Done > > > Reading state information... Done > > > Calculating upgrade... Error! > > > Some packages could not be installed. This may mean that you have > > > requested an impossible situation or if you are using the unstable > > > distribution that some required packages have not yet been created > > > or been moved out of Incoming. > > > The following information may help to resolve the situation: > Why is this t64 upgrade working then as it is removing deprecated packages > for *t64 packages? I do not know, at times I'm also wondering why it doesn't do it, but I didn't take time to look at the code to understand what the resolver is doing. Also, it was sort of expected. I think we can probably solve this is a more controlled manner. With the current t64 transitioning in unstable it is difficult to track down. Many updates so the situation now may differ from the situation in an hour from now. > > This seems to be an more of an actual issue where dependencies are > declared but > >apt doing something weird. But that is an issue on bookworm where we > aren't > >getting poluted results because of a transitioning. > > I'm glad you were able to replicate in bookworm (stable) it but I don't > think (at least in this case) it is related to the t64 transition. Same > errors on both distributions and I checked that gdb dependencies were > satisfied in unstable (I don't have a system running stable). I disagree (or agree) to some extent. The gdb-minimal has been held back on my system for a long time. I removed it after I saw it was a remnant of a KDE experiment I did. The fact that I can install it now is a change from a couple of days ago. The bug may be the same, but with how unstable it is now with this big transition, it's wise to leave it where we are now and break it down into a more controlled reproduction path, where we don't have so many moving pieces. > Appreciate your support. Yw and good luck! Cheers, Wesley
Bug#1065831: apt tries to uninstall kde & plasma (full-upgrade)
On Sun, Mar 10, 2024 at 02:13:34PM +0100, Miguel Angel wrote: > # apt full-upgrade > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Calculating upgrade... Error! > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > plasma-workspace : Depends: gdb-minimal but it is not going to be installed > or > gdb > E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by > held packages. > This problem isn't because of apt, the problem is that gdb-minimal/gdb dependencies cannot be satified. A full-upgrade is the equivalent of a dist-upgrade which will remove packages to resolve the dependencies. The problem you are facing is the t64 transition[1][2] where not all packages are transitioned. My advice to you is: don't expect full-upgrade to work until the transitioning is done. You can do `apt upgrade' without too much hassle. If you feel like it you can inspect individual upgrades possibilities via `apt list --upgradable' and upgrade each package individually. That has worked well for me in the past week with aptitude, but it requires going through many offered solutions. > I've seen other users are experimenting the same issue: > https://groups.google.com/g/linux.debian.user/c/7gpQImSH-Cs This seems to be an more of an actual issue where dependencies are declared but apt doing something weird. But that is an issue on bookworm where we aren't getting poluted results because of a transitioning. It differs from yours because your apt output says "gdb-minimal but it is not going to be installed or gdb" so apt sees the alternative, but cannot install it either. IMHO, that should be filed as a seperate bug against apt on bookworm. And if possible checked on testing as well. FWIW, I can reproduce it on bookwork with apt, apt-get and aptitude, where the latter offers a solution to install gdb and not deinstall plasma-workspace. > I don't know why plasma-workspace depends on gdb I don't know either and that question should be redirected to the plasma-workspace maintainer. Cheers, Wesley [1] https://lists.debian.org/debian-devel-announce/2024/02/msg0.html [2] https://www.reddit.com/r/debian/comments/1b2ncdn/64bit_time_t_transition_in_progress_in_unstable/
Bug#1064969: apt: can't upgrade with aptitude
ing, unstable)] 5) libglib2.0-0 [2.78.4-1 (now, testing, unstable)] 6) libglib2.0-0:i386 [2.78.4-1 (now, testing, unstable)] 7) libpam0g [1.5.2-9.1+b1 (now, testing, unstable)] 8) libxmlsec1 [1.2.38-1+b1 (now, testing, unstable)] Install the following packages: 9) libapt-pkg6.0t64 [2.7.12+nmu1 (unstable)] 10) libatk1.0-0t64 [2.50.0-1.1 (unstable)] 11) libdb5.3t64 [5.3.28+dfsg2-4.1 (unstable)] 12) libevdocument3-4t64 [45.0-2 (unstable)] 13) libevview3-3t64 [45.0-2 (unstable)] 14) libglib2.0-0t64 [2.78.4-2 (unstable)] 15) libglib2.0-0t64:i386 [2.78.4-2 (unstable)] 16) libpam0t64 [1.5.3-4 (unstable)] 17) libxmlsec1t64 [1.2.39-4 (unstable)] 18) libxmlsec1t64-openssl [1.2.39-4 (unstable)] Keep the following packages at their current version: 19) libgspell-1-2 [1.12.2-1+b1 (now, testing, unstable)] 20) libgspell-1-common [1.12.2-1 (now, testing, unstable)] I haven't committed yet to any solution it gives me, but the last one feels like it should be the best Cheers, Wesley -- Wesley Schwengle E: wes...@schwengle.net
Bug#1064919: vokoscreen-ng: Prompts for updates on startup
Package: vokoscreen-ng Version: 3.7.0-1 Severity: normal Tags: patch X-Debbugs-Cc: wes...@schwengle.net Dear Maintainer, I started up vokoscreen and saw there was an update available for vokoscreen. When running this app from source that might be great information, but from a Debian point of view this is unwanted. I patched vokoscreen-ng with 3 patches, for version 3.5.0 (stable), v3.7.0 (unstable/testing) and v3.8.0, which would be nice to have in Debian unstable perhaps? Patches are attached. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'experimental'), (500, 'testing'), (10, 'stable-updates'), (10, 'stable-security'), (10, 'oldstable-security'), (10, 'oldoldstable'), (10, 'stable'), (10, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vokoscreen-ng depends on: ii gstreamer1.0-plugins-good 1.22.10-1 ii libc6 2.37-15 ii libgcc-s1 14-20240201-3 ii libglib2.0-0 2.78.4-1 ii libgstreamer1.0-0 1.22.10-1 ii libpulse0 16.1+dfsg1-3 ii libqt5core5a 5.15.10+dfsg-7 ii libqt5dbus55.15.10+dfsg-7 ii libqt5gui5 5.15.10+dfsg-7 ii libqt5multimedia5 5.15.10-2+b1 ii libqt5network5 5.15.10+dfsg-7 ii libqt5widgets5 5.15.10+dfsg-7 ii libqt5x11extras5 5.15.10-2+b1 ii libstdc++6 14-20240201-3 ii libwayland-client0 1.22.0-2.1+b1 ii libx11-6 2:1.8.7-1 Versions of packages vokoscreen-ng recommends: ii gstreamer1.0-libav 1.22.10-1 ii gstreamer1.0-pulseaudio1.22.10-1 ii libqt5multimedia5-plugins 5.15.10-2+b1 pn pulseaudio Versions of packages vokoscreen-ng suggests: ii gstreamer1.0-plugins-bad 1.22.10-1 ii gstreamer1.0-plugins-ugly 1.22.10-1 ii gstreamer1.0-vaapi 1.22.10-1 ii intel-media-va-driver 24.1.0+dfsg1-1 -- debconf-show failed >From eac5373d61b1984b1da8b5a1f019631ff46b4dd2 Mon Sep 17 00:00:00 2001 From: Wesley Schwengle Date: Tue, 27 Feb 2024 14:01:25 -0400 Subject: [PATCH] Don't show update information The application tells a user that an update is available. This is the opposite of what we want in Debian. We want users to only update when Debian ships a new .deb. Remove the bits from source. Signed-off-by: Wesley Schwengle --- src/formMainWindow.ui | 34 -- src/information/QvkInformation.cpp | 29 + src/information/QvkInformation.h | 2 -- 3 files changed, 1 insertion(+), 64 deletions(-) diff --git a/src/formMainWindow.ui b/src/formMainWindow.ui index 7e17f8cb..e59a4dc3 100644 --- a/src/formMainWindow.ui +++ b/src/formMainWindow.ui @@ -2042,40 +2042,6 @@ - - - - - - Look for updates - - - - - - - TextLabel - - - true - - - - - - - Qt::Horizontal - - - -40 -20 - - - - - - diff --git a/src/information/QvkInformation.cpp b/src/information/QvkInformation.cpp index 282a587d..82de9555 100644 --- a/src/information/QvkInformation.cpp +++ b/src/information/QvkInformation.cpp @@ -66,11 +66,8 @@ QvkInformation::QvkInformation( QvkMainWindow *vkMainWindow, connect( ui->pushButtonPause,SIGNAL( clicked( bool ) ), timerRecord, SLOT( stop() ) ); connect( ui->pushButtonContinue, SIGNAL( clicked( bool ) ), timerRecord, SLOT( start() ) ); -// Update +// Debian doesn't need the updates because of the release model ui->label_Upate_tab_1->clear(); -ui->label_Upate_tab_4->clear(); -connect( , SIGNAL( signal_newVersionAvailable( QString ) ), this, SLOT( slot_newVersionAvailable( QString ) ) ); -connect( ui->checkBoxLookForUpdates, SIGNAL( toggled( bool ) ), , SLOT( slot_doDownload( bool ) ) ); // Frames, Format, Codecs connect( ui->comboBoxFormat, SIGNAL( currentTextChanged( QString ) ), this, SLOT( slot_Format
Bug#1064534: rofi as dmenu replacement
Package: rofi Version: 1.7.5-0.1+b1 Severity: wishlist X-Debbugs-Cc: wes...@schwengle.net Dear Maintainer, I saw a cool thing on /r/unixporn on reddit and it made me look at rofi. I want to replace it for the dmenu call to dmenu of suckless-tools. However there is an issue. rofi states that it is a drop-in replacement for dmenu. If you call rofi as dmenu, eg by linking it ln -s /usr/bin/rofi /usr/bin/dmenu you get to have all the toys. This works pretty well as long as you have suckless-tools installed. Without suckless-tools i3 for example doesn't work correctly. This is because i3 calls dmenu_run, which is provided by suckless-tools. dmenu_run calls /usr/bin/dmenu_path which is also provided by suckless-tools. My question is as follows, is there a way that both suckless-tools and rofi start providing dmenu (as an update-alternatives) and that both suckless-tools and rofi depend on a package that is called dmenu-data which provides dmenu_run and dmenu_path? I filed this against rofi, because rofi is the one not providing some of the crucial infra to be a replacement for dmenu. $ apt-cache depends i3 i3 Depends: i3-wm Recommends: i3lock Recommends: suckless-tools Recommends: dunst By implementing the dmenu_path and dmenu_run scripts from suckless-tools the i3 recommends can be either suckless-tools or rofi. Many thanks! Wesley -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'experimental'), (500, 'testing'), (10, 'stable-updates'), (10, 'stable-security'), (10, 'oldstable-security'), (10, 'oldoldstable'), (10, 'stable'), (10, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages rofi depends on: ii libc6 2.37-15 ii libcairo2 1.18.0-1+b1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3+b1 ii libglib2.0-0 2.78.4-1 ii libpango-1.0-01.51.0+ds-4 ii libpangocairo-1.0-0 1.51.0+ds-4 ii libstartup-notification0 0.12-6+b1 ii libxcb-cursor00.1.4-1+b1 ii libxcb-ewmh2 0.4.1-1.1+b1 ii libxcb-icccm4 0.4.1-1.1+b1 ii libxcb-randr0 1.15-1 ii libxcb-util1 0.4.0-1+b1 ii libxcb-xinerama0 1.15-1 ii libxcb-xkb1 1.15-1 ii libxcb1 1.15-1 ii libxkbcommon-x11-01.6.0-1 ii libxkbcommon0 1.6.0-1 rofi recommends no packages. rofi suggests no packages. -- no debconf information
Bug#1062772: apt: apt.conf(5) should document all options
Hi Thorsten, I would expect apt.conf(5) to document any and all configuration items one can do to apt*, either directly or by other manpages referenced from “SEE ALSO”. The man page of apt.conf shows the following: EXAMPLES /usr/share/doc/apt/examples/configure-index.gz is a configuration file showing example values for all possible options. The file location is incorrect (on Debian sid), this should be /usr/share/doc/apt/examples/configure-index. It documents all the options you can find. Cheers, Wesley -- Wesley Schwengle E: wes...@schwengle.net
Bug#1064354: steam-installer: Unable to install steam-installer
Package: steam-installer Severity: important X-Debbugs-Cc: wes...@schwengle.net Dear Maintainer, I wanted to install the steam-installer package, this fails: $ sudo apt-get install steam-installer/unstable Reading package lists... Done Building dependency tree... Done Reading state information... Done Selected version '1:1.0.0.79~ds-2' (Debian:unstable, Debian:testing [amd64]) for 'steam-installer' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: steam-installer : Depends: steam-libs-i386 (= 1:1.0.0.79~ds-2) but it is not installable E: Unable to correct problems, you have held broken packages. I don't have steam-libs-i386, but I do see steam-libs: $ apt-cache policy steam-libs steam-libs: Installed: (none) Candidate: 1:1.0.0.79~ds-2 Version table: 1:1.0.0.79~ds-2 900 900 https://deb.debian.org/debian unstable/main amd64 Packages 500 https://deb.debian.org/debian testing/main amd64 Packages 1:1.0.0.75+ds-6 10 10 https://deb.debian.org/debian stable/main amd64 Packages Which I can also install: $ sudo apt-get install steam-libs Reading package lists... Done Building dependency tree... Done Reading state information... Done Suggested packages: libudev0 nvidia-driver-libs nvidia-vulkan-icd Recommended packages: libasound2-plugins libva-glx2 mesa-vulkan-drivers steam-devices zenity The following NEW packages will be installed: steam-libs 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 18.9 kB of archives. After this operation, 38.9 kB of additional disk space will be used. Get:1 https://deb.debian.org/debian unstable/main amd64 steam-libs amd64 1:1.0.0.79~ds-2 [18.9 kB] Fetched 18.9 kB in 1s (32.1 kB/s) Selecting previously unselected package steam-libs:amd64. (Reading database ... 474365 files and directories currently installed.) Preparing to unpack .../steam-libs_1%3a1.0.0.79~ds-2_amd64.deb ... Unpacking steam-libs:amd64 (1:1.0.0.79~ds-2) ... Setting up steam-libs:amd64 (1:1.0.0.79~ds-2) ... I tried reinstalled steam-installer, but this failed (as expected, but tried it none the less): $ sudo apt-get install steam-installer/unstable Reading package lists... Done Building dependency tree... Done Reading state information... Done Selected version '1:1.0.0.79~ds-2' (Debian:unstable, Debian:testing [amd64]) for 'steam-installer' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: steam-installer : Depends: steam-libs-i386 (= 1:1.0.0.79~ds-2) but it is not installable E: Unable to correct problems, you have held broken packages. I cannot seem to install it for ANY version of the steam-installer: $ sudo apt-get install steam-installer/testing Reading package lists... Done Building dependency tree... Done Reading state information... Done Selected version '1:1.0.0.79~ds-2' (Debian:unstable, Debian:testing [amd64]) for 'steam-installer' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: steam-installer : Depends: steam-libs-i386 (= 1:1.0.0.79~ds-2) but it is not installable E: Unable to correct problems, you have held broken packages. $ sudo apt-get install steam-installer/stable Reading package lists... Done Building dependency tree... Done Reading state information... Done Selected version '1:1.0.0.75+ds-6' (Debian:12.5/stable [amd64]) for 'steam-installer' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: steam-installer : Depends: steam-libs (= 1:1.0.0.75+ds-6) but 1:1.0.0.79~ds-2 is to be installed Depends: steam-libs-i386 (>= 1:1.0.0.75+ds-6) but it is not installable E: Unable to correct problems, you have held broken packages. I've also tried to install it by executing: sudo dpkg --add-architecture i386 to no avail. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'experimental'),
Bug#1063775: initramfs-tools, and cp: warning: behavior of -n is non-portable and may change in future; use --update=none instead
Small update on the previous message. It's the same as Debian #1055694, which is upstream bug https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62572 Cheers, Wesley -- Wesley Schwengle E: wes...@schwengle.net
Bug#1061790: gerbera: Missing files JS files prevent UI from working
Package: gerbera Version: 2.0.0+dfsg-1 Severity: important X-Debbugs-Cc: wes...@schwengle.net Dear Maintainer, I was trying to see how gerbera does m3u playlist support so I installed it from the repo and tried to access the web UI. What happens is that you only get to see a login button. Once you click that you get an 404 Not Found error on http://my.ip:49152/? When you open http://my.ip:49152 with a developer tool the following files seem to be missing: * vendor/tether/tether.min.js * vendor/md5.min.js * vendor/font-awesome/fonts/fontawesome-webfont.woff2?v=4.7.0 * vendor/font-awesome/fonts/fontawesome-webfont.woff?v=4.7.0 * vendor/font-awesome/fonts/fontawesome-webfont.ttf?v=4.7.0 I compiled Gerbera from source in $HOME/.local/gerbera and with the same configuration (abeit a minor change to reflect the change of webroot) the app works as intented: When enabling the UI and the account you get the user/password textblocks and you can login. It seems that the build is not placing the files where one expects them to be. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'experimental'), (500, 'testing'), (10, 'stable-updates'), (10, 'stable-security'), (10, 'oldstable-security'), (10, 'oldoldstable'), (10, 'stable'), (10, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.11-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gerbera depends on: ii adduser 3.137 ii fonts-font-awesome 5.0.10+really4.7.0~dfsg-4.1 ii fonts-lato 2.015-1 ii init-system-helpers 1.66 ii libavcodec-extra60 [libavcodec60] 7:6.1.1-1 ii libavformat60 7:6.1.1-1 ii libavutil58 7:6.1.1-1 ii libc6 2.37-14 ii libcurl3-gnutls 8.5.0-2 ii libduktape207 2.7.0-2+b1 ii libebml51.4.5-1 ii libexif12 0.6.24-1+b1 ii libexiv2-27 0.27.6-1+b1 ii libffmpegthumbnailer4v5 2.2.2+git20220218+dfsg-2+b1 ii libfmt9 9.1.0+ds1-2 ii libgcc-s1 14-20240127-1 ii libixml11 1:1.14.18-1 ii libjs-bootstrap44.6.1+dfsg1-4 ii libjs-jquery3.6.1+dfsg+~3.5.14-1 ii libjs-jquery-ui 1.13.2+dfsg-1 ii libjs-popper.js 1.16.1+ds-6 ii libjs-prototype 1.7.3-1 ii libmagic1 1:5.45-2+b1 ii libmariadb3 1:10.11.6-2 ii libmatroska71.7.1-1 ii libpugixml1v5 1.14-0.1 ii libspdlog1.12 [libspdlog1.12-fmt9] 1:1.12.0+ds-2 ii libsqlite3-03.45.0-1 ii libstdc++6 14-20240127-1 ii libtag1v5 1.13.1-1 ii libupnp17 1:1.14.18-1 ii libuuid12.39.3-6 ii node-js-cookie 3.0.1+~3.0.0-3 gerbera recommends no packages. Versions of packages gerbera suggests: ii chromium [www-browser]121.0.6167.85-1 ii firefox-esr [www-browser] 115.7.0esr-1 ii gerbera-doc 2.0.0+dfsg-1 ii google-chrome-beta [www-browser] 122.0.6261.6-1 ii google-chrome-stable [www-browser]121.0.6167.85-1 ii google-chrome-unstable [www-browser] 123.0.6262.5-1 ii lynx [www-browser]2.9.0rel.0-2 ii w3m [www-browser] 0.5.3+git20230121-2+b2 -- Configuration Files: /etc/gerbera/config.xml changed [not included] -- no debconf information
Bug#1061478: apt: Internal Error, AutoRemover broke stuff, unmet dependencies: linux-headers-6.6.9-amd64
Hi,
TL;DR
One can currently reproduce this behavior on unstable by doing:
```
apt-get install linux-headers-6.6.9-amd64
dpkg -r --force-depends linux-image-6.6.9-amd64-unsigned
apt-get full-upgrade
```
You can fix it by either running:
```
apt-get remove linux-headers-6.6.9-amd64
# or
apt-mark auto linux-headers-6.6.9-amd64
# or but it doesn't make sense
apt --fix-broken install
```
I came across this scenario myself as well and on Reddit. This is my
take on it.
Around the 11th, linux-image-6.6.9-amd64 was installed. And around the
18th, linux-image-6.6.11-amd64. During the .9 install I saw similar
things, I chose to keep everything as is. This caused me to keep running
on the 6.6.8 kernel at the time.
I think something went wrong with the linux-headers-6.6.9-amd64 and/or
linux-image-6.6.9-amd64 package. For instance, I didn't have the
linux-headers-6.6.9-amd64 installed while I had
linux-headers-6.6.8-amd64 and linux-headers-6.6.11-amd64 installed. The
package linux-image-6.6.9-amd64 isn't available in the repositories
(anymore):
```
$ apt-cache policy linux-image-6.6.9-amd64
linux-image-6.6.9-amd64:
Installed: (none)
Candidate: (none)
Version table:
6.6.9-1 -1
100 /var/lib/dpkg/status
```
The dependency tree is sorta broken of 6.6.9. The headers have these
dependencies:
```
$ apt-cache depends linux-headers-6.6.9-amd64
linux-headers-6.6.9-amd64
Depends: linux-headers-6.6.9-common
|Depends: linux-image-6.6.9-amd64
Depends: linux-image-6.6.9-amd64-unsigned
Depends: linux-kbuild-6.6.9
Depends: gcc-13
```
Your linux-image-amd64 package depends on:
```
$ apt-cache depends linux-image-amd64
linux-image-amd64
Depends: linux-image-6.6.13-amd64
```
So now one of your packages is broken. I think it is warrants a look
into your /var/log/apt/history.log to try to figure out what happened to
your linux-{image,headers}-* packages around the 11th, 18th and later on.
Cheers,
Wesley
--
Wesley Schwengle
E: wes...@schwengle.net
Bug#1060649: minidlna: Typo in debian/minidlna.default
Package: minidlna Version: 1.3.3+dfsg-0.2+b1 Severity: minor Tags: patch X-Debbugs-Cc: wes...@schwengle.net Dear Maintainer, I was looking into some things regarding minidlna and saw a small typo. Patch is attached. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'experimental'), (500, 'testing'), (10, 'stable-updates'), (10, 'stable-security'), (10, 'oldstable-security'), (10, 'oldoldstable'), (10, 'stable'), (10, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.8-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages minidlna depends on: ii adduser 3.137 ii init-system-helpers 1.66 ii libavformat607:6.1.1-1 ii libavutil58 7:6.1.1-1 ii libc62.37-13 ii libexif120.6.24-1+b1 ii libffmpegthumbnailer4v5 2.2.2+git20220218+dfsg-2+b1 ii libflac121.4.3+ds-2+b1 ii libid3tag0 0.15.1b-14 ii libjpeg62-turbo 1:2.1.5-2+b2 ii libogg0 1.3.5-3 ii libsqlite3-0 3.44.2-1 ii libvorbis0a 1.3.7-1 minidlna recommends no packages. minidlna suggests no packages. -- Configuration Files: /etc/minidlna.conf changed [not included] -- no debconf information >From 11cebcbcfbd245590a95e31af4375478e780c880 Mon Sep 17 00:00:00 2001 From: Wesley Schwengle Date: Thu, 11 Jan 2024 21:17:57 -0400 Subject: [PATCH] Fix typo in debian/minidlna.default: change systerm to system Signed-off-by: Wesley Schwengle --- debian/minidlna.default | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/debian/minidlna.default b/debian/minidlna.default index a4eeaf2..c3b5f38 100644 --- a/debian/minidlna.default +++ b/debian/minidlna.default @@ -22,5 +22,5 @@ # Additional options that are passed to the daemon # We pass -r option to do soft non-destructive rebuild on every start-up. -# If your systerm restarts often, you might want to remove this. +# If your system restarts often, you might want to remove this. #DAEMON_OPTS="-r" -- 2.42.0.1031.ga492c6355c
Bug#1059382: kitty: Text rendering change
Hi Nilesh On 12/24/23 03:19, Nilesh Patra wrote: Thanks for reporting it and taking the time to bisect it as well! The issue is that on a dark background with light text everything is made bold, whereas previously this was not bold. I think it is wise to inform users that `text_composition_strategy legacy` restores the old defaults (similar to the version in stable) and/or refer to the manual page: https://sw.kovidgoyal.net/kitty/conf/#opt-kitty.text_composition_strategy If kitty can read a system-wide config it might be set there. It can, but honestly I don't want to diverge from upstream here. Everyone may not like the said change and enforcing a system wide config for a composition change isn't something that I'm willing to do. If you could, please consider opening up an upstream issue to see if we can reach a common ground. If not, I'll just add a d/NEWS entry informing users/sysadmin about this change. I'm fine with adding a d/NEWS entry, that is mainly the reason why I reported the bug. I think it's worth a mention because it confused me quite a bit :) Cheers, Wesley -- Wesley Schwengle E: wes...@schwengle.net
Bug#1059382: kitty: Text rendering change
Package: kitty Version: 0.31.0-3 Severity: normal X-Debbugs-Cc: wes...@schwengle.net Dear Maintainer, On Debian stable version 0.26.5 of kitty is running, on testing/unstable this is 0.31.0. In 0.28.0 a change in text rendering is made by upstream, this is mentioned in the changelog. Text rendering change: Use sRGB correct linear gamma blending for nicer font rendering and better color accuracy with transparent windows. See the option text_composition_strategy for details. The obsolete macos_thicken_font will make the font too thick and needs to be removed manually if it is configured. (#5969) I didn't spot it and went in full bisect mode to figure out which commit caused it. I found it and could relate it to the Changelog entry. The issue is that on a dark background with light text everything is made bold, whereas previously this was not bold. I think it is wise to inform users that `text_composition_strategy legacy` restores the old defaults (similar to the version in stable) and/or refer to the manual page: https://sw.kovidgoyal.net/kitty/conf/#opt-kitty.text_composition_strategy If kitty can read a system-wide config it might be set there. Cheers, Wesley -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'experimental'), (500, 'testing'), (10, 'stable-updates'), (10, 'stable-security'), (10, 'oldstable-security'), (10, 'oldoldstable'), (10, 'stable'), (10, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 6.6.8-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kitty depends on: ii kitty-shell-integration 0.31.0-3 ii kitty-terminfo 0.31.0-3 ii libc62.37-13 ii libdbus-1-3 1.14.10-3 ii libharfbuzz0b8.0.1-1 ii liblcms2-2 2.14-2 ii libpng16-16 1.6.40-2 ii libpython3.113.11.7-2 ii libssl3 3.1.4-2 ii libwayland-client0 1.22.0-2.1 ii libx11-6 2:1.8.7-1 ii libx11-xcb1 2:1.8.7-1 ii libxcursor1 1:1.2.1-1 ii libxkbcommon-x11-0 1.6.0-1 ii libxkbcommon01.6.0-1 ii libxxhash0 0.8.2-2 ii python3 3.11.6-1 ii python3.11 3.11.7-2 ii zlib1g 1:1.3.dfsg-3 Versions of packages kitty recommends: ii kitty-doc 0.31.0-3 ii libcanberra0 0.30-11 Versions of packages kitty suggests: pn imagemagick -- no debconf information
Bug#1011079: kitty: New upstream release
Package: kitty Version: 0.21.2-1+b1 Followup-For: Bug #1011079 Dear Maintainer, The kitty release of 0.21.2 is from a year ago (release 2021-06-28) per https://sw.kovidgoyal.net/kitty/changelog/ Could we get a bump to 0.25.2 released 2022-06-07? Many thanks! Wesley
Bug#964934: cookiecutter: Upgrade to version 1.7.x
Hello Vincent, On 7/13/20 1:08 AM, Vincent Bernat wrote: ❦ 12 juillet 2020 16:14 -04, Wesley Schwengle: In December 2019 version 1.7.0 was released and in April 2020 1.7.1 and 1.7.2 were released. It adds a very useful feature: https://cookiecutter.readthedocs.io/en/1.7.2/advanced/directories.html I would like to make use of this. Could you bump the version the debian unstable branch? I am missing a recent enough version of python3-recommonmark due to bug #955180. It seems that bug has been resolved. Could you perhaps see if the version bump is now possible? Many thanks! Wesley -- Wesley Schwengle E: wes...@schwengle.net
Bug#972293: linux-image-5.8.0-1-amd64: kernel seems to break pulseaudio HDMI sound
On 2020-10-15 19:13, Wesley Schwengle wrote: When booting with the linux-image-5.8.0-2-amd64 kernel I don't have sound on my HDMI output. The pulseaudio config hasn't changed yet it suddenly stopped working after a reboot. When booting linux-image-5.8.0-1-amd64, the whole setup works again without fail. linux-image-5.8.0-1-amd64: Installed: 5.8.7-1 Candidate: 5.8.7-1 Version table: *** 5.8.7-1 100 100 /var/lib/dpkg/status linux-image-5.8.0-2-amd64: Installed: 5.8.10-1 Candidate: 5.8.10-1 Version table: *** 5.8.10-1 500 500 http://deb.debian.org/debian testing/main amd64 Packages 100 /var/lib/dpkg/status The issue seems to be fixed in sid: linux-image-5.8.0-3-amd64: Installed: 5.8.14-1 Candidate: 5.8.14-1 Version table: *** 5.8.14-1 300 300 http://deb.debian.org/debian sid/main amd64 Packages 100 /var/lib/dpkg/status This works Cheers, Wesley -- Wesley Schwengle E: wes...@schwengle.net
Bug#972293: linux-image-5.8.0-1-amd64: kernel seems to break pulseaudio HDMI sound
Package: src:linux Version: 5.8.7-1 Severity: important Dear Maintainer, When booting with the linux-image-5.8.0-2-amd64 kernel I don't have sound on my HDMI output. The pulseaudio config hasn't changed yet it suddenly stopped working after a reboot. When booting linux-image-5.8.0-1-amd64, the whole setup works again without fail. linux-image-5.8.0-1-amd64: Installed: 5.8.7-1 Candidate: 5.8.7-1 Version table: *** 5.8.7-1 100 100 /var/lib/dpkg/status linux-image-5.8.0-2-amd64: Installed: 5.8.10-1 Candidate: 5.8.10-1 Version table: *** 5.8.10-1 500 500 http://deb.debian.org/debian testing/main amd64 Packages 100 /var/lib/dpkg/status -- Package-specific info: ** Version: Linux version 5.8.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.0-6) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.8.7-1 (2020-09-05) ** Command line: BOOT_IMAGE=/vmlinuz-5.8.0-1-amd64 root=/dev/mapper/neptune--vg-root ro quiet ** Not tainted ** Kernel log: [ 22.358969] iwlwifi :01:00.0: loaded firmware version 36.79ff3ccf.0 8265-36.ucode op_mode iwlmvm [ 22.358983] iwlwifi :01:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2) [ 22.439723] audit: type=1400 audit(1602802327.623:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/haveged" pid=597 comm="apparmor_parser" [ 22.439725] audit: type=1400 audit(1602802327.623:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oopslash" pid=595 comm="apparmor_parser" [ 22.439727] audit: type=1400 audit(1602802327.623:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=598 comm="apparmor_parser" [ 22.439729] audit: type=1400 audit(1602802327.623:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=598 comm="apparmor_parser" [ 22.439795] audit: type=1400 audit(1602802327.623:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirtd" pid=593 comm="apparmor_parser" [ 22.439797] audit: type=1400 audit(1602802327.623:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libvirtd//qemu_bridge_helper" pid=593 comm="apparmor_parser" [ 22.439816] audit: type=1400 audit(1602802327.623:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ntpd" pid=599 comm="apparmor_parser" [ 22.440324] audit: type=1400 audit(1602802327.623:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="postgresql_akonadi" pid=601 comm="apparmor_parser" [ 22.442026] audit: type=1400 audit(1602802327.627:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="mariadbd_akonadi" pid=600 comm="apparmor_parser" [ 22.442752] audit: type=1400 audit(1602802327.627:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/x86_64-linux-gnu/lightdm/lightdm-guest-session" pid=594 comm="apparmor_parser" [ 22.454588] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [ 22.460583] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 22.479816] iwlwifi :01:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230 [ 22.485123] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (0c45:6717) [ 22.488069] iwlwifi :01:00.0: Applying debug destination EXTERNAL_DRAM [ 22.488351] iwlwifi :01:00.0: Allocated 0x0040 bytes for firmware monitor. [ 22.493796] uvcvideo 1-11:1.0: Entity type for entity Extension 4 was not initialized! [ 22.493798] uvcvideo 1-11:1.0: Entity type for entity Extension 3 was not initialized! [ 22.493799] uvcvideo 1-11:1.0: Entity type for entity Processing 2 was not initialized! [ 22.493800] uvcvideo 1-11:1.0: Entity type for entity Camera 1 was not initialized! [ 22.493852] input: Integrated_Webcam_HD: Integrate as /devices/pci:00/:00:14.0/usb1/1-11/1-11:1.0/input/input30 [ 22.493907] usbcore: registered new interface driver uvcvideo [ 22.493907] USB Video Class driver (1.1.1) [ 22.536119] Bluetooth: Core ver 2.22 [ 22.536128] NET: Registered protocol family 31 [ 22.536129] Bluetooth: HCI device and connection manager initialized [ 22.536132] Bluetooth: HCI socket layer initialized [ 22.536134] Bluetooth: L2CAP socket layer initialized [ 22.536136] Bluetooth: SCO socket layer initialized [ 22.536369] dell_laptop: Using i8042 filter function for receiving events [ 22.536372] intel_rapl_common: Found RAPL domain package [ 22.536374] intel_rapl_common: Found RAPL domain core [ 22.536375] intel_rapl_common: Found RAPL domain uncore [ 22.536375] intel_rapl_common: Found RAPL domain dram [ 22.542568] iwlwifi :01:00.0: base HW address: f8:63:3f:c8:77:15 [ 22.610828] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC3254: line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:line [
Bug#964934: cookiecutter: Upgrade to version 1.7.x
Package: cookiecutter Version: 1.6.0-4 Severity: normal Dear Maintainer, In December 2019 version 1.7.0 was released and in April 2020 1.7.1 and 1.7.2 were released. It adds a very useful feature: https://cookiecutter.readthedocs.io/en/1.7.2/advanced/directories.html I would like to make use of this. Could you bump the version the debian unstable branch? Many thanks, Wesley -- System Information: Debian Release: bullseye/sid APT prefers stable APT policy: (10, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.7.0-1-amd64 (SMP w/8 CPU cores) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cookiecutter depends on: ii python3 3.8.2-3 ii python3-cookiecutter 1.6.0-4 cookiecutter recommends no packages. Versions of packages cookiecutter suggests: pn python-cookiecutter-doc -- no debconf information
Bug#927470: zsh: Segfault on completion menu in large git repo's
Package: zsh
Version: 5.7.1-1
Severity: important
Tags: upstream
Dear Maintainer,
ZSH seems to segfault in the following scenario in larger git
repositories:
```
vi Zaaksysteem::Bar::voo::vooo::voo
# you'll receive the following message: Killed by signal in compadd after 0s
vi
# segfault
```
Steps to reproduce this:
* cd /tmp
* git clone g...@github.com:git/git.git
* cd git
* zsh -f
* Set the following options:
```
autoload -Uz compinit
zstyle ':completion:*' completer _complete _match _approximate
zstyle ':completion:*:match:*' original only
zstyle ':completion:*:approximate:*' max-errors 1 numeric
zstyle ':completion:*' menu select
zstyle -e ':completion:*:approximate:*' \
max-errors 'reply=($((($#PREFIX+$#SUFFIX)/3))numeric)'
zstyle ':completion:*' squeeze-slashes true
_ZCOMP=${ZDOTDIR:-$HOME}/.zcompdump
today=$(date --date '00:00 today' +%s)
if [[ ! -e $_ZCOMP || $today -gt $(stat --format %Y $_ZCOMP) ]];
then
compinit -i
touch ${_ZCOMP}
else
compinit -C;
fi
unset _ZCOMP
```
* now execute the following commands
```
vi Zaaksysteem::Bar::voo::vooo::voo
# you'll receive the following message: Killed by signal in compadd after 0s
vi
# segfault
```
I've submitted this bug already to upstream[1].
Cheers,
Wesley
[1]: http://www.zsh.org/mla/workers/2019/msg00251.html
-- Package-specific info:
Packages which provide vendor completions:
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++--===--
ii curl 7.64.0-2amd64command line tool
for transferring data with URL syntax
ii docker-ce-cli5:18.09.5~3-0~debian-buster amd64Docker CLI: the
open-source application container engine
ii git-buildpackage 0.9.14 all Suite to help
with Debian packages in Git repositories
ii lastpass-cli 1.3.2-1 amd64command line
interface to LastPass.com
ii mpv 0.29.1-1amd64video player
based on MPlayer/mplayer2
ii pulseaudio 12.2-4 amd64PulseAudio sound
server
ii systemd 241-3 amd64system and
service manager
ii udev 241-3 amd64/dev/ and hotplug
management daemon
ii vlc-bin 3.0.6-1 amd64binaries from VLC
ii youtube-dl 2019.01.17-1all downloader of
videos from YouTube and other sites
dpkg-query: no path found matching pattern /usr/share/zsh/vendor-functions/
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing'), (300, 'unstable'), (50, 'experimental'), (10,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages zsh depends on:
ii libc6 2.28-8
ii libcap2 1:2.25-2
ii libtinfo6 6.1+20181013-2
ii zsh-common 5.7.1-1
Versions of packages zsh recommends:
ii libc6 2.28-8
ii libncursesw6 6.1+20181013-2
ii libpcre3 2:8.39-12
Versions of packages zsh suggests:
pn zsh-doc
-- no debconf information
Bug#924736: zsh 5.7.1 segfaults when three setopt options are in play
Package: zsh Version: 5.7.1-1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Have a zshrc with the following setopts: setopt hist_reduce_blanks setopt hist_ignore_space setopt interactivecomments * Run zsh -f * Now enter ` #` * You get a command not found error * Now source your zshrc * Again entery ` #` * Segfault I've reproduced it with a docker image from debian testing. https://gist.github.com/waterkip/ab532e8dc65ad948046b6848dcfacffa It does work on Debian stable (zsh 5.3.1). Dockerfile contents: FROM debian:testing WORKDIR /root RUN apt-get update && apt-get install --no-install-recommends -y zsh COPY zsh/.zsh/minimal-zshrc .zshrc $ dpkg -l zsh Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii zsh5.7.1-1 amd64shell with lots of features -- Package-specific info: Packages which provide vendor completions: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-===-- ii curl 7.64.0-1amd64command line tool for transferring data with URL syntax ii docker-ce-cli 5:18.09.3~3-0~debian-buster amd64Docker CLI: the open-source application container engine ii mpv0.29.1-1amd64video player based on MPlayer/mplayer2 ii pulseaudio 12.2-4 amd64PulseAudio sound server ii systemd241-1 amd64system and service manager ii udev 241-1 amd64/dev/ and hotplug management daemon ii vlc-bin3.0.6-1 amd64binaries from VLC ii youtube-dl 2019.01.17-1all downloader of videos from YouTube and other sites dpkg-query: no path found matching pattern /usr/share/zsh/vendor-functions/ -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable'), (50, 'experimental'), (10, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages zsh depends on: ii libc6 2.28-8 ii libcap2 1:2.25-2 ii libtinfo6 6.1+20181013-2 ii zsh-common 5.7.1-1 Versions of packages zsh recommends: ii libc6 2.28-8 ii libncursesw6 6.1+20181013-2 ii libpcre3 2:8.39-11 Versions of packages zsh suggests: pn zsh-doc -- no debconf information
Bug#924050: poppler-utils: pdfsig segfaults on signed PDF
Package: poppler-utils Version: 0.71.0-3 Severity: important Dear Maintainer, $ /usr/bin/pdfsig ~/Downloads/bar.pdf Digital Signature Info of: /home/wesleys/Downloads/bar.pdf Internal Error (0): Input couldn't be parsed as a CMS signature zsh: segmentation fault /usr/bin/pdfsig ~/Downloads/bar.pdf Mar 8 22:28:30 neptune kernel: [ 8383.032122] pdfsig[13393]: segfault at 0 ip 7fb1e04c96a1 sp 7fffe6c20b48 error 4 in libc-2.28.so[7fb1e038f000+148000] I was hoping to see more information about bar.pdf I installed poppler from the git repo and then you get this: $ pdfsig ~/Downloads/bar.pdf Digital Signature Info of: /home/wesleys/Downloads/bar.pdf Internal Error (0): Input couldn't be parsed as a CMS signature Signature #1: - Signer Certificate Common Name: (null) - Signer full Distinguished Name: (null) - Signing Time: Mar 08 2019 11:10:19 - Signing Hash Algorithm: unknown - Signature Type: adbe.pkcs7.detached - Signed Ranges: [0 - 12877], [40303 - 123158] - Total document signed - Signature Validation: Unknown Validation Failure. $ pdfsig -v pdfsig version 0.74.0 Copyright 2005-2019 The Poppler Developers - http://poppler.freedesktop.org Copyright 1996-2011 Glyph & Cog, LLC Could you upgrade to the latest version? Many thanks. * ldd from Debian package $ ldd /usr/bin/pdfsig linux-vdso.so.1 (0x7ffd131f7000) libpoppler.so.82 => /usr/lib/x86_64-linux-gnu/libpoppler.so.82 (0x7fee16c4c000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7fee16ac8000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fee16907000) libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x7fee1684b000) libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x7fee16805000) libjpeg.so.62 => /usr/lib/x86_64-linux-gnu/libjpeg.so.62 (0x7fee1659c000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fee1637c000) libnss3.so => /usr/lib/x86_64-linux-gnu/libnss3.so (0x7fee1622e000) libsmime3.so => /usr/lib/x86_64-linux-gnu/libsmime3.so (0x7fee161ff000) libnspr4.so => /usr/lib/x86_64-linux-gnu/libnspr4.so (0x7fee161be000) libopenjp2.so.7 => /usr/lib/x86_64-linux-gnu/libopenjp2.so.7 (0x7fee16167000) liblcms2.so.2 => /usr/lib/x86_64-linux-gnu/liblcms2.so.2 (0x7fee1610a000) libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 (0x7fee160cf000) libtiff.so.5 => /usr/lib/x86_64-linux-gnu/libtiff.so.5 (0x7fee1605) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fee1602f000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fee15eac000) /lib64/ld-linux-x86-64.so.2 (0x7fee16f65000) libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x7fee15e92000) libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x7fee15e53000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fee15e4a000) libnssutil3.so => /usr/lib/x86_64-linux-gnu/libnssutil3.so (0x7fee15e18000) libplc4.so => /usr/lib/x86_64-linux-gnu/libplc4.so (0x7fee15e11000) libplds4.so => /usr/lib/x86_64-linux-gnu/libplds4.so (0x7fee15e0c000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fee15e07000) librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fee15dfb000) libwebp.so.6 => /usr/lib/x86_64-linux-gnu/libwebp.so.6 (0x7fee15b92000) libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 (0x7fee15af2000) liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fee15aca000) libjbig.so.0 => /usr/lib/x86_64-linux-gnu/libjbig.so.0 (0x7fee158bc000) * ldd from source $ ldd $HOME/.local/bin/pdfsig linux-vdso.so.1 (0x7ffcc1be8000) libpoppler.so.85 => /home/wesleys/.local/lib/libpoppler.so.85 (0x7f4091501000) libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x7f4091356000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f4091195000) libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x7f40910d9000) libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x7f4091093000) libjpeg.so.62 => /usr/lib/x86_64-linux-gnu/libjpeg.so.62 (0x7f4090e2a000) libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f4090c0a000) libcurl-gnutls.so.4 => /usr/lib/x86_64-linux-gnu/libcurl-gnutls.so.4 (0x7f4090b7c000) libopenjp2.so.7 => /usr/lib/x86_64-linux-gnu/libopenjp2.so.7 (0x7f4090b25000) liblcms2.so.2 => /usr/lib/x86_64-linux-gnu/liblcms2.so.2 (0x7f4090ac8000) libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 (0x7f4090a8f000) libtiff.so.5 => /usr/lib/x86_64-linux-gnu/libtiff.so.5 (0x7f4090a1) libnss3.so => /usr/lib/x86_64-linux-gnu/libnss3.so (0x7f40908c) libsmime3.so => /usr/lib/x86_64-linux-gnu/libsmime3.so (0x7f4090891000) libnspr4.so => /usr/lib/x86_64-linux-gnu/libnspr4.so (0x7f409085) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f409082f000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f40906ac000) /lib64/ld-linux-x86-64.so.2 (0x7f40917f5000) libgcc_s.so.1 =>
Bug#901574: pass: Security Vulnerability: Faulty GPG Signature Checking (CVE-2018-12356)
Package: pass Version: 1.6.5-7 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** I was reading https://lists.zx2c4.com/pipermail/password-store/2018-June/003308.html and checked my installation and saw the security fix wasn't applied yet. Please apply commit: https://git.zx2c4.com/password-store/commit/?id=8683403b77f59c56fcb1f05c61ab33b9fd61a30d See also: https://salsa.debian.org/security-tracker-team/security-tracker/commit/11310766438958f0166ac0ba0d77fe0174f6e937 *** End of the template - remove these template lines *** -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (999, 'stable'), (900, 'testing'), (400, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=en_US:en (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pass depends on: ii gnupg 2.1.18-8~deb9u2 ii gnupg2 2.1.18-8~deb9u2 ii pwgen 2.07-1.1+b1 ii tree1.7.0-5 Versions of packages pass recommends: ii git 1:2.11.0-3+deb9u3 ii gnupg2 2.1.18-8~deb9u2 ii xclip 0.12+svn84-4+b1 Versions of packages pass suggests: ii libxml-simple-perl 2.22-1 iu perl5.24.1-3+deb9u4 ii ruby1:2.3.3 -- no debconf information
Bug#567316: bsdmainutils: [ncal] -w week-numbers are off by one since version 8.0
Hi, If I change the locale (LANG) to nl_NL.utf8 it works as intented. However, when I set my LANG to en_US.utf8 and my LC_TIME to nl_NL.utf8 - or anything else like en_GB.utf8) it will still use the LANG setting and not respect the LC_TIME variable. Cheers, Wesley -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511547: yiff-server: installation fails
Hello, I can confirm this bug with 2.14.5-7 (testing/unstable) and 2.14.5-5 (stable). I did not have the problem with yiff-server 2.14.5-5.1. While I'm typing this e-mail the problem got solved (after I removed/purged yiff-server and reinstalled it). Hope this helps.. /var/log/aptitude: [UPGRADE] xserver-common 2:1.7.4-2 - 2:1.7.5-1 [UPGRADE] xserver-xorg-core 2:1.7.4-2 - 2:1.7.5-1 [UPGRADE] yiff-server 2.14.5-5.1 - 2.14.5-7 === Will install 1 packages, and remove 0 packages. 24.6kB of disk space will be freed === [UPGRADE] wpasupplicant 0.6.9-3 - 0.6.10-1 [UNCONFIGURED] yiff-server === Log complete. Aptitude 0.6.1.5: log report Sun, Feb 28 2010 15:01:19 +0100 IMPORTANT: this log only lists intended actions; actions which fail due to dpkg problems may not be completed. Will install 0 packages, and remove 0 packages. === [UNCONFIGURED] yiff-server === /var/log/dpkg: /var/log/dpkg.log:2010-02-28 14:50:07 upgrade yiff-server 2.14.5-5.1 2.14.5-7 /var/log/dpkg.log:2010-02-28 14:50:07 status half-configured yiff-server 2.14.5-5.1 /var/log/dpkg.log:2010-02-28 14:50:08 status unpacked yiff-server 2.14.5-5.1 /var/log/dpkg.log:2010-02-28 14:50:08 status half-installed yiff-server 2.14.5-5.1 /var/log/dpkg.log:2010-02-28 14:50:08 status half-installed yiff-server 2.14.5-5.1 /var/log/dpkg.log:2010-02-28 14:50:08 status half-installed yiff-server 2.14.5-5.1 /var/log/dpkg.log:2010-02-28 14:50:08 status unpacked yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 14:50:08 status unpacked yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 14:53:54 configure yiff-server 2.14.5-7 2.14.5-7 /var/log/dpkg.log:2010-02-28 14:53:54 status unpacked yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 14:53:54 status unpacked yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 14:53:54 status unpacked yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 14:53:54 status half-configured yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 14:57:58 configure yiff-server 2.14.5-7 2.14.5-7 /var/log/dpkg.log:2010-02-28 14:57:58 status half-configured yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:00:52 configure yiff-server 2.14.5-7 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:00:52 status half-configured yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:00:55 configure yiff-server 2.14.5-7 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:00:55 status half-configured yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:19 configure yiff-server 2.14.5-7 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:19 status half-configured yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:23 configure yiff-server 2.14.5-7 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:23 status half-configured yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:39 configure yiff-server 2.14.5-7 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:39 status half-configured yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:41 configure yiff-server 2.14.5-7 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:41 status half-configured yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:55 status half-configured yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:56 remove yiff-server 2.14.5-7 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:56 status half-configured yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:56 status half-installed yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:57 status half-installed yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:57 status config-files yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:57 purge yiff-server 2.14.5-7 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:57 status config-files yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:57 status config-files yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:57 status config-files yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:58 status config-files yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:58 status config-files yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:01:58 status not-installed yiff-server none /var/log/dpkg.log:2010-02-28 15:02:15 install yiff-server none 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:02:15 status half-installed yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:02:16 status half-installed yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:02:16 status unpacked yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:02:16 status unpacked yiff-server 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:02:18 configure yiff-server 2.14.5-7 2.14.5-7 /var/log/dpkg.log:2010-02-28 15:02:18 status
Bug#567316: bsdmainutils: [ncal] -w week-numbers are off by one since version 8.0
Michael Meskes wrote: severity 567316 normal thanks Severity: grave Justification: renders package unusable You're kidding right? I just don't get the joke. A calender which displays incorrect weeks is not usable, not to me at least. I've noticed it also with the testing version, upgraded to the unstable version and the same bug is present. ... Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Are you sure the week numbering is incorrect for that locale? If so please point me somewhere to find out what the right week numberiung is for en_US. Yes, this is an international standard (ISO-8601 standard). http://en.wikipedia.org/wiki/ISO_week_date http://en.wikipedia.org/wiki/ISO_8601 The first week of a year is the week that contains the first Thursday of a year. On my stable box I have the same locale. LANG=en_US.utf8 LC_CTYPE=en_US.utf8 LC_NUMERIC=en_US.utf8 LC_TIME=en_US.utf8 LC_COLLATE=en_US.utf8 LC_MONETARY=en_US.utf8 LC_MESSAGES=en_US.utf8 LC_PAPER=en_US.utf8 LC_NAME=en_US.utf8 LC_ADDRESS=en_US.utf8 LC_TELEPHONE=en_US.utf8 LC_MEASUREMENT=en_US.utf8 LC_IDENTIFICATION=en_US.utf8 LC_ALL= Cheers, Wesley -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#567316: bsdmainutils: [ncal] -w week-numbers are off by one since version 8.0
Package: bsdmainutils Version: 8.0.6 Severity: grave Justification: renders package unusable Hello, I have the same bug as reported here. Since that bug is marked as fix released I'm opening a new one. Feel free to merge them if needed. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556029 On Debian testing/unstable the problem has occurred again: $ apt-cache policy bsdmainutils bsdmainutils: Installed: 8.0.6 Candidate: 8.0.6 Version table: *** 8.0.6 0 990 ftp://ftp.nl.debian.org unstable/main Packages 100 /var/lib/dpkg/status 8.0.5 0 990 ftp://ftp.nl.debian.org testing/main Packages 8.0.1ubuntu1 0 200 http://archive.ubuntu.com lucid/main Packages 6.1.10ubuntu3 0 200 http://archive.ubuntu.com jaunty/main Packages 6.1.10 0 500 ftp://ftp.nl.debian.org lenny/main Packages I've noticed it also with the testing version, upgraded to the unstable version and the same bug is present. On stable: $ ncal -w January 2010 Mo 4 11 18 25 Tu 5 12 19 26 We 6 13 20 27 Th 7 14 21 28 Fr 1 8 15 22 29 Sa 2 9 16 23 30 Su 3 10 17 24 31 53 1 2 3 4 On testing/unstable: $ ncal -w January 2010 Mo 4 11 18 25 Tu 5 12 19 26 We 6 13 20 27 Th 7 14 21 28 Fr 1 8 15 22 29 Sa 2 9 16 23 30 Su 3 10 17 24 31 1 2 3 4 5 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (990, 'testing'), (500, 'stable'), (200, 'lucid'), (200, 'jaunty-updates'), (200, 'jaunty-security'), (200, 'jaunty') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bsdmainutils depends on: ii bsdutils 1:2.16.2-0 Basic utilities from 4.4BSD-Lite ii debianutils 3.2.2 Miscellaneous utilities specific t ii libc6 2.10.2-5 Embedded GNU C Library: Shared lib ii libncurses5 5.7+20090803-2 shared libraries for terminal hand bsdmainutils recommends no packages. Versions of packages bsdmainutils suggests: ii cpp 4:4.4.2-3 The GNU C preprocessor (cpp) pn vacation none (no description available) ii wamerican [wordlist] 6-3American English dictionary words ii whois 5.0.0 an intelligent whois client -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#223683: define temporary directory install/rm scripts
I have the same problem. Can't exec /tmp/sun-java5-jre.config.100721: Permission denied at /usr/share/perl/5.10/IPC/Open3.pm line 168. open2: exec of /tmp/sun-java5-jre.config.100721 configure failed at /usr/share/perl5/Debconf/ConfModule.pm line 59 sun-java5-jre failed to preconfigure, with exit status 255 Can't exec /tmp/sun-java5-bin.config.100723: Permission denied at /usr/share/perl/5.10/IPC/Open3.pm line 168. open2: exec of /tmp/sun-java5-bin.config.100723 configure failed at /usr/share/perl5/Debconf/ConfModule.pm line 59 sun-java5-bin failed to preconfigure, with exit status 255 I also have /tmp with noexec: tmpfs on /tmp type tmpfs (rw,noexec,nosuid) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#549192: fails at boot time: Unknown pcap error
Package: guessnet Version: 0.51-1 Severity: normal I can confirm the issue. I know there has been a change in the source to address this issue, this was closed not so long ago. From the changelog: + increased pcap timeout in netwatcher.cc. Closes: #529882. Thanks to Dietz Pröpper and Vincent Lefevre for digging this out. But I guess the increase isn't sufficient. sudo ifup eth0 guessnet: Added work-fixed guessnet: Added home-fixed2 guessnet: Added home-fixed guessnet: Added aruba-vrolijk guessnet: Added missing-cable guessnet: Added startable with priority 100 guessnet: Added startable with priority 200 guessnet: Added startable with priority 4294967295 guessnet: Added startable with priority 4294967295 guessnet: Added startable with priority 4294967295 guessnet: Added startable with priority 4294967295 guessnet: 4 candidates found in input guessnet: Guessnet 0.51 starting... guessnet: Trying MII detection guessnet: 0 candidate profiles guessnet: Added default test missing-cable guessnet: Trying MII detection guessnet: Initialized test subsystems guessnet: Starting all 3 startables guessnet: Starting elements with priority 100 guessnet: Starting elements with priority 200 guessnet: Starting net sender guessnet: Starting elements with priority 4294967295 guessnet: Sending 10 ARP probes, 1 every second... guessnet: Sending 10 ARP probes, 1 every second... guessnet: Sending 10 ARP probes, 1 every second... guessnet: Sending 10 ARP probes, 1 every second... guessnet: Started tests guessnet: 5 candidates Unknown pcap error. Context: getting a new packet from the network. Quitting NetWatcher thread. No such process. Context: Cancelling generic thread when shutting down NetWatcher Ignoring unknown interface eth0=missing-cable. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (600, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.31-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages guessnet depends on: ii libc6 2.10.2-2 GNU C Library: Shared libraries ii libgcc1 1:4.4.2-3 GCC support library ii libiw29 29-2 Wireless tools - library ii libnet1 1.1.4-2library for the construction and h ii libpcap0.81.0.0-5system interface for user-level pa ii libstdc++64.4.2-3The GNU Standard C++ Library v3 guessnet recommends no packages. Versions of packages guessnet suggests: ii ifplugd 0.28-16configuration daemon for ethernet pn pppoe none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550906: guessnet: Guessnet sees WPA2 network as open when wpa_supplicant is authenticated to the network
Package: guessnet Version: 0.51-1 Severity: important Situation: Mapping via guessnet in /etc/network/interfaces, network choosen should be home-wifi2 and not wifi-open at boot. The same problem is present on Ubuntu 9.10. The problem is now also present on Debian testing/unstable. The difference with Ubuntu is that a restart of all the network services the problem is not resolved. See also: https://bugs.launchpad.net/ubuntu/+source/guessnet/+bug/442083 The Ubuntu bug report has the interfaces file listed and some more logs. Oct 14 00:52:31 eniac ifplugd(eth0)[22255]: ifplugd 0.28 initializing. Oct 14 00:52:31 eniac ifplugd(eth0)[22255]: Using interface eth0/00:21:70:A5:35:EF with driver tg3 (version: 3.98) Oct 14 00:52:31 eniac ifplugd(eth0)[22255]: Using detection mode: SIOCETHTOOL Oct 14 00:52:31 eniac ifplugd(eth0)[22255]: Initialization complete, link beat not detected. Oct 14 00:52:31 eniac ifplugd(wlan0)[22263]: ifplugd 0.28 initializing. Oct 14 00:52:31 eniac ifplugd(wlan0)[22263]: Using interface wlan0/00:1F:3C:B1:66:62 Oct 14 00:52:31 eniac ifplugd(wlan0)[22263]: Using detection mode: wireless extension Oct 14 00:52:31 eniac ifplugd(wlan0)[22263]: Initialization complete, link beat not detected. Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: Link beat detected. Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: Executing '/etc/ifplugd/ifplugd.action wlan0 up'. Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Added work-wifi Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Added home-wifi Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Added home-wifi2 Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Added wifi-open Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Added missing-cable Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Added startable with priority 10 Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: 4 candidates found in input Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Guessnet 0.51 starting... Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Trying MII detection Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Link beat detection (mii) failed: Operation not supported Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Link beat detection (ethtool) failed: Operation not supported Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Link beat detection (priv) failed: Operation not supported Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: No working link beat detection function available for interface wlan0 Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: 0 candidate profiles Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Added default test missing-cable Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Initialized test subsystems Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Starting all 1 startables Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Starting elements with priority 10 Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Starting wireless scan Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Started tests Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: 5 candidates Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network AG Net Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network ABCCPWPA Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network Thomson9066CD Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network UPC012741 Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network Giulio Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network NEXUS-WIRELESS Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network SpeedTouch182F61 Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network DS Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network UPC38627 Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network SX551E7F2F1 Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network PYS Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network wnl2.opperschaap.net Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network SpeedTouch4B8460 Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network UPC019737 Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Found network Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet: Testing wireless open Oct 14 00:52:34 eniac ifplugd(wlan0)[22263]: client: guessnet:
Bug#497663: Tab completion for vim is broken
On 16.09.08 13:49 Wesley Germaine Schwengle wrote: I submitted a bugreport to Ubuntu about this issue: https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/264644 The bugreport includes patches for vim, less and diff_options. I also have setopt CSHJUNKIEQUOTES enabled in my .zshrc.. On zsh version 4.3.2 the autocompletion is working without the need to patch the completion files. The bug is introduced in either 4.3.3 or 4.3.4. Cheers, Wesley -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
