Package: cryptsetup
Version: 2:2.6.1-4
Severity: normal
Hey.
When askpass is running (and waiting) while it's terminal gets somehow
killed/HUPed/etc. ... it's process goes to 100% utilisation from where
it doesn't seem to recover anymore.
Reproducer:
Shell 1:
echo $$
/lib/crypts
Hey Daniel.
On Sun, 2 Apr 2023 15:57:13 +0200 Daniel Swarbrick
wrote:
> A sample run of dh-make-golang against github.com/thanos-io/thanos
> reveals the following missing build-deps:
>
> * github.com/chromedp/chromedp
> * github.com/efficientgo/core
> * github.com/efficientgo/e2e
> * gi
Hey.
Just for the records and those who stumble over this and are interested
in the outcome.
upstream clarified fstab syntax in:
https://github.com/util-linux/util-linux/commit/43a6b183d8945cc91307f21adc8070254eb925b5
- whether the 4th field is mandatory is now in kind of a limbo... the
manpag
Package: wnpp
Severity: wishlist
* Package name: btrfs-diff-go
Version : git
Upstream Contact: Michael Bideau
* URL : https://github.com/mbideau/btrfs-diff-go
* License : GPL 3
Programming Lang: Go
Description : analyze differences between two BTRFS sna
On Mon, 2023-04-03 at 10:38 +0400, Yadd wrote:
> > Causes that would also make it fix #977014.
> Sure, thanks for the link
You've marked it as fixed but haven't closed it.
Was that on purpose or should I close it?
> I saw in this issue that you were a little frustrated by the lack of
> respons
Hey.
Thanks for the fix.
Am I right that this *generally* does not longer enable apache2-
doc.conf per default (i.e. also on fresh installs)?
Causes that would also make it fix #977014.
Cheers,
Chris.
On Fri, 2023-03-31 at 22:53 +0200, Sven Joachim wrote:
> Or complain on upstream
> bug #62572[1] and ask for a revert of the '-n' exit failure if the
> destination exists.
Well -n isn't POSIX. But in strictly speaking their change seems even
POSIX compliant to me as that says for both tools:
>
Package: mdadm
Version: 4.2-5
Severity: normal
Hey.
I've noted that my:
/etc/systemd/system/sysinit.target.wants/mdadm-shutdown.service
is a dangling symlink to:
/usr/lib/systemd/system/mdadm-shutdown.service
This may be because my system is not yet usr-merged and the package
actually places th
On Wed, 2023-03-29 at 15:46 +0200, Cyril Brulebois wrote:
> Closing as not a bug. If you want an actual bug to get fixed, please
> file a specific bug report, describing what's not working correctly.
Well you could call usage of a non-documented option a bug, but if
improvement is apparently not d
On Wed, 2023-03-29 at 03:38 +, David wrote:
> I think the formal specification of the fstab format would be
> 'man 3 getfsent' because that is the canonical method to
> parse /etc/fstab.
Uhm, but that doesn't really describe which fields are necessary
either. So it would be the actual code whi
On Wed, 2023-03-29 at 02:25 +, David wrote:
> My thought process is as follows:
> Field 4 is for mount options. This is just the same as providing
> options to the 'mount' command issued at the command line.
> And it is ok to use the 'mount' command without options.
Well that's clear and it pr
On Wed, 2023-03-29 at 01:41 +, David wrote:
> Yes, for many years using Debian stable, my swap lines in
> /etc/fstab look like this:
> none swap
Hmm, I'm not sure whether strictly speaking it's allowed to skip the
4th field.
The manpage explicitly documents so for the 5th and the 6th, but n
On Wed, 2023-03-29 at 00:49 +, David wrote:
> In that situation, field 4 has to be non-blank, which is when setting
> it
> to "defaults" becomes useful.
>
> Otherwise, putting "defaults" in field 4 achieves nothing, because
> defaults
> are defaults so there is no reason to specify them.
Does
Source: debian-installer
Version: 20230217
Severity: minor
Hey.
In the end this is probably anyway completely ignored, so consider this
just a cosmetic issue:
AFAICS, the installer cretes swap entries in fstab as:
none swap sw 0 0
https://salsa.debian.org/installer-team/partman-basicfilesyst
Hey.
I rather think now that even my hack with the swapfile isn't really
save.
The idea with that was that it's just the file, but not activated as
swap of course. But who knows for sure that in this case the file is
never moved.
Anyway, @Guilhem, would you agree to close this as wontfix and add
Hey.
I recently considered to do the same, i.e.:
- have a passphrase only for the dm-crypt encrypted rootfs
- have a separate dm-crypt encrypted swap device for hibernate only
- use a high-entropy key-file on the rootfs to decrypt the swap device
My understanding of the initramfs-tools boot is a
Package: coreutils
Version: 9.1-1
Severity: wishlist
Hey.
9.2 is out :-)
Cheers,
Chris.
Package: firefox
Version: 110.0.1-1
Severity: important
Hey.
I've seen that 111.0 (which contains numerous security updates)
is haning in the new queue.
Is this because of the freeze?
If so, could you upload it at least into experimental so that people
using sid can get the current version?
Package: sshpass
Version: 1.09-1+b1
Severity: wishlist
Hey.
1.10 seems to be out :-)
Cheers,
Chris.
Package: wnpp
Severity: wishlist
* Package name: thanos
Version : 0.30.2
Upstream Contact: thanos...@googlegroups.com
* URL : https://github.com/thanos-io/thanos
* License : Apache 2.0
Programming Lang: Go
Description : highly available Prometheus setup
On Thu, 2023-03-09 at 01:14 +0100, Guilhem Moulin wrote:
> so please confirm :-)
hehe,... just that very minute I've written a dummy hook script that
simply includes libgcc so that I can upgrade my kernel ;-)
Applied your patch, and at least it causes libgcc to be included. So
I'd call that confi
On Wed, 2023-03-08 at 14:04 +0100, Guilhem Moulin wrote:
> No please don't, #-1 is RC so that would block transitioning into
> Bookworm which only supports merged-usr… Will fix that later during
> the
> freeze, but ATM the priority is to get -2 into Bookworm ASAP, not
> further delay the transitio
Control: reopen -1
On Wed, 2023-03-08 at 08:16 +0100, Milan Broz wrote:
> Just upstream is no longer responding here...
Seems upstream is dead... I also have some minor PRs open against
argon2, but no response. Tried to get directly in contact with some of
them, but the same.
@Guilhem, I'm reope
Hey Guilhem.
Is it possible that your fix doesn't work on not-yet-usr-merged
systems?
I get here:
$ env --unset=LD_PRELOAD ldd /sbin/cryptsetup | sed -nr
'/.*=>\s*(\S+)\/libargon2\.so\..*/ {s//\1/p;q}'
/usr/lib/x86_64-linux-gnu
but:
$ dpkg -L libgcc-s1
/lib/x86_64-linux-gnu
/lib/x86_64-linux-
Package: prometheus-node-exporter
Version: 1.1.2+ds-2.1
Severity: important
Hey.
Since Debian seems to set a default falue to --collector.netdev.device-exlude,
--collector.netdev.device-include can never be used, as the two are mutually
exclusive and when setting the latter in /etc/default/prome
On Fri, 2023-03-03 at 08:38 +0100, Gürkan Myczko wrote:
> I have some packaging of it here, but I'm not yet sure how to fix
> remaining lintian problems,
> their manpages are of non optimal quality:
>
> http://sid.ethz.ch/debian/openseachest/
Looks nice... have you asked a sponsor for help with
Package: network-manager
Version: 1.42.0-1
Severity: normal
Hey.
Just wanted to file this as a bug against ifupdown, but while writing I found
out
that actually the upgrade from 1.40.10-1 to 1.42.0-1 causes this:
Ssince around the 10th of Feburary (and I've updated NM on the 11th) my
dns-searc
Hey Salvatore.
On Wed, 2023-02-15 at 07:12 +0100, Salvatore Bonaccorso wrote:
> Just to be sure, that I understood you correctly. That is if on the
> current system with the issue you roll back just only the kernel back
> to 6.1.8-1, then the issue dissaper?
Exactly, and the roll back even only
Source: linux
Version: 6.1.11-1
Severity: normal
Hey.
Over the year this has unfortunately happened numerous times, either by changes
in the Xorg driver, or libinput... and now it seems the kernel caused the
same:
After upgrading from linux-image-6.1.0-3-amd64 to linux-image-6.1.0-4-amd64 and
a
Package: wnpp
Severity: wishlist
* Package name: carbonyl
Version : git
Upstream Contact: Fathy Boundjadj
* URL : https://github.com/fathyb/carbonyl
* License : BSD
Programming Lang: Rust, C++
Description : a Chromium based browser built to run in a ter
Package: apt
Version: 2.5.5
Severity: normal
X-Debbugs-Cc: Debian Security Team
Hey.
It seems that apt only gives a warning (and exit status 0) in case a section
has been specified in sources.list, which doesn't exist.
E.g. aptitde doesn't seem to even show that warning.
Isn't that kind of a
Control: severity -1 normal
Hey Sébastien.
On Sat, 2023-01-14 at 15:19 +0100, Sébastien Villemot wrote:
> As far as I can tell, it’s not that the font rendering has changed,
> but
> that the default monospace font has changed (it was previously DejaVu
> Mono Book on my system, now it’s Noto Sans
Package: digikam
Version: 4:7.9.0-1+b1
Severity: important
Hey.
Every time when starting digikam, a dialog pops up asking to download
some engines for redeye removal and face detection from the internet,
which would cause them to be stored in /home/calestyo/.local/share/digikam/
Could that ple
Package: kismet-plugins
Version: 2016.07.R1-1+b1
Severity: grave
Justification: renders package unusable
Hey.
libssl1.1 has been removed from unstable and thus kismet-plugins is no
longer installable.
Cheers,
Chris.
Control: tags -1 - ftbfs
Control: severity -1 important
Still not used to reportbug's new numbering...
Package: vim
Version: 2:9.0.1000-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hey.
The following probably still worked with 2:9.0.1000-1, but definitely works
again
when going back to the version in testing (2:9.0.0813-1+b1).
Wh
Hey.
Seems that https://gitfreak.com/CyberShadow/btdu is dead.
I guess https://github.com/CyberShadow/btdu might be the new upstream.
Cheers,
Chris.
On Sun, 2022-12-25 at 10:42 +, Joachim Falk wrote:
> https://salsa.debian.org/debian-remote-team/tigervnc/-/commit/5a92b4e3a8d405a6b7d4ac161b59e7150d9ac324
Thanks :-)
Hey.
Is this still followed up or already supported to some extent in the
meantime?
I've looked through the previous messages and suggested patches and
some notes on these:
- Auto-detection of resume device, when resuming happens, is most
likely a security hole, as I've described previously in
Package: usbguard-notifier
Version: 0.0.6-1+b1
Severity: wishlist
Hey.
There's a new upstream version out which seems to have some really nice
new feature, namely adding buttons to the notifications that actually
allow to accept/reject new USB devices.
I think feature actually makes the whole t
Hey Russell
On Wed, 2022-12-14 at 08:45 +1100, Russell Coker wrote:
> I think this is an upstream bug for misusing an existing config file.
While I agree on that... I'm not sure whether it's good to have two
separate config files for more or less the same thing.
This might open up all kinds of pr
Package: libpam-cap
Version: 1:2.66-1
Severity: normal
Hey.
On installation there is a file conflict:
Unpacking libpam-cap:amd64 (1:2.66-1) over (1:2.63-1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-B9lzYA/08-libpam-cap_1%3a2.66-1_amd64.deb (--unpack):
trying to overwrite '/usr/s
Package: usbguard-notifier
Version: 0.0.6-1+b1
Severity: normal
Hey.
I see this in the kernel logs when usbguard-notifier starts:
Dec 11 21:47:20 heisenberg kernel: process 'data/usr/bin/usbguard-notifier'
started with executable stack
Could this be something with the build?
Cheers,
Chris.
The first patch seems to have been buggy, a v2 was posted:
https://lore.kernel.org/dash/y5btwr28ngvmm...@gondor.apana.org.au/
Cheers,
Chris.
Just for the records, meanwhile I've also opened a proper ticket about
this over at BusyBox regarding the same bug in their sh at:
https://bugs.busybox.net/show_bug.cgi?id=15171
Just for the records, meanwhile I've also opened a proper ticket about
this over at BusyBox regarding the same bug in their sh at:
https://bugs.busybox.net/show_bug.cgi?id=15171
Hey Ben.
On Sun, 2022-11-27 at 17:51 +0100, Ben Hutchings wrote:
> I don't think I will work on this in klibc until there's a fix in
> upstream dash. If you're still watching upstream dash, please let me
> know when there's a fix I can pick.
A patch has now been posted for dash at:
https://lore.
Control: tags -1 + patch
Hey.
For the records:
A patch (for dash) was posted at:
https://lore.kernel.org/dash/y47zlpwkqy+ji...@gondor.apana.org.au/
and is scheduled to be merged into upstream’s git.
Cheers,
Chris.
Hey Pierre.
On Tue, 2022-12-06 at 23:08 +0100, Pierre Gruet wrote:
> Thanks for the bug report (and the follow-up precisions you sent)!
>
> Yet I fail to reproduce it on testing. I installed zookeeper and
> zookeeperd on testing, then ran
>
> $ /usr/share/zookeeper/bin/zkCli.sh
> specifying not
Package: wnpp
Severity: wishlist
* Package name: terminal-markdown-viewer
Version : 1.6.3
Upstream Contact: i...@axiros.com
* URL : https://github.com/axiros/terminal_markdown_viewer
* License : BSD
Programming Lang: Python
Description : Styled Terminal
Source: tigervnc
Version: 1.12.0+dfsg-5
Severity: minor
Hey.
tigervncserver(1) manpage mentions:
/etc/tigervnc/vncserver-config-defaults
~/.vnc/tigervnc.conf
/etc/tigervnc/vncserver-config-mandatory
tigervncsession(8) manpage mentions:
/etc/tigervnc/vncserver-config-defaults
$HOME
Source: tigervnc
Version: 1.12.0+dfsg-5
Severity: normal
Hey.
It seems that tigervncserver creates differen PID/log file names, depending
on whether it's listening on inet or unix sockets:
For UNIX sockets it uses:
kronecker.scientia.org:1.{log,pid}
with 1 being the display ID
For inet sockets
Source: tigervnc
Version: 1.12.0+dfsg-5
Severity: wishlist
Hey.
I have a use case here I start a VNC server via SSH as normal user and
using systemd’s --user service manager.
For that to work, systemd needs to know the PID file, which I thus need
to know in the SSH command I'm executing on the
Package: remmina
Version: 1.4.27+dfsg-2
Severity: wishlist
Hey.
1.4.28 seems to be out, which also contains a number of nice
fixes for usage of VNC with UNIX sockets.
Thanks,
Chris.
Source: zookeeper
Version: 3.8.0-10
Severity: wishlist
Hey.
While trying out the new packaging of 3.8, I've noticed a number
of things, which seem at least a bit unusual:
1) Using updates-alternatives mechanism, to set up the config.
That seems quite unsual, and updates-alternatives is even
Hey.
Just a side note on this:
One further problem with the sysvinit script, when via the virtual
systemd units, seems to be, that stopping that unit via systemd does no
necessarily work.
Namely if a connection to zookeeper is still open (e.g. via zkCli) the
daemon continued to run, and closed o
Control: tags -1 + patch
I've made a simple PR at:
https://salsa.debian.org/java-team/zookeeper/-/merge_requests/8
Cheers,
Chris.
Package: zookeeperd
Version: 3.8.0-10
Severity: important
Hey.
The init.d script doesn't require networking, therefore it may happen.
that e.g. systemd starts zookeeper before the network is brought up,
in which case zookeeper crashes, as it cannot bind to the configured
server.N-option address.
And here we go:
CLASSPATH="/etc/zookeeper/conf:/usr/share/java/zookeeper.jar:/usr/share/java/slf4j-log4j12.jar:/usr/share/java/log4j-1.2.jar"
Seems to do the trick to get logging to /var/log/zookeeper/foobar .
The zkCli shows still no prompt, though.
It also needs the /usr/share/java/log4j-1.2.ja
I got a bit further:
Setting:
CLASSPATH="/etc/zookeeper/conf:/usr/share/java/zookeeper.jar:/usr/share/java/slf4j-simple.jar"
i.e. adding the ":/usr/share/java/slf4j-simple.jar" helps a bit...
The server seems to start now, and via zkCli, I can `ls` my paths and
`get` values.
But there's still no
I should perhaps add, that I have installed the zookeeper packages
(zookeeper zookeeperd libzookeeper-java) from testing into stable
(bullseye), all other dependencies were already met with bullseye
versions.
Also, according to https://www.slf4j.org/codes.html#StaticLoggerBinder
and there the ques
Package: zookeeper
Version: 3.8.0-10
Severity: grave
Justification: renders package unusable
Hey.
I've tried the new packagin, but while all my config and data files are in
place,
and while the server "runs", there is no logging (neither to stdout/err for
systemd
nor /var/log/zookeeper .. not
Hey.
I've just installed this again on some node, and for some reason apt-
listbugs still shows it as open:
# aptitude
Performing actions...
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
grave bugs of liblog4j1.2-java (→ 1.2.17-10+deb11u1)
b1 - #1004482 - liblog4j1.2-jav
Hey again.
I think I also managed to reproduce the first error:
$ git clone g...@github.com:calestyo/btrbk.git
$ cd btrbk
$ git checkout improve-ssh_filter_btrbk.sh
$ git rebase --interactive 53b3290e14ea9c8df6288bec981d8b28655c8fa7
This shows:
pick 9819fdc ssh_filter_btrbk.sh: convert to POSI
On Fri, 2022-11-25 at 07:42 +0100, Andrej Shadura wrote:
>
> I’ve just run those commands, and it worked without an error. Given
> that I use git-crecord daily, I’d have caught the breakage this basic
> — are you sure it’s not something with your gitconfig?
Hmm I just tried with moving my ~/.conf
Hey Andrej
On Mon, 2022-11-21 at 08:42 +0100, Andrej Shadura wrote:
> Can you try these things please:
> 1) Try the latest Git version
That's a bit difficult right now in my setup.
> 2) If it still fails, run with --debug, it’s going to print the patch
> 3) If possible, send me your working tree
Just for the records, the same issue (as well as some other variant)
also exists in other ash bashed shells:
klibc:
https://lists.zytor.com/archives/klibc/2022-November/004694.html
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024735
busybox:
http://lists.busybox.net/pipermail/busybox/2022-N
Package: klibc-utils
Version: 2.0.11-1
Severity: normal
Tags: upstream
Hey there.
There’s a bug in ash-bashed shells, including the one shipped with
klibc.
The original variant is described here (for dash):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024635
respectively
https://lore.kern
On Tue, 2022-11-22 at 21:11 -0800, tony mancill wrote:
> Yes, totally. I didn't mean to imply that the bug shouldn't be here.
Sure... just wanted to point out, that I don't consider it your fault
or so :-)
> > I had evolution running, while I've upgraded. And didn't restart it
> > afterwards (
Hey Tony.
On Tue, 2022-11-22 at 20:40 -0800, tony mancill wrote:
> Thank you for the bug report. libphonenumber 8.12.57+ds-1 has been
> in
> testing for longer than a month at this point [1]. Has it been
> broken
> all of this time? If not, I suspect this is related the protobuf
> transition [2
Package: libphonenumber8
Version: 8.12.57+ds-1+b2
Severity: serious
Hey.
After the upgrade, evolution crashes when started:
$ evolution
evolution: symbol lookup error:
/usr/lib/x86_64-linux-gnu/libebook-contacts-1.2.so.4: undefined symbol:
_ZN4i18n12phonenumbers11PhoneNumberC1EPN6google8protob
Package: dash
Version: 0.5.11+git20210903+057cd650a4ed-9
Severity: normal
Tags: upstream
Control: forwarded -1
https://lore.kernel.org/dash/b2e298215b3d51d8284296484caa138faddaa0e4.ca...@scientia.org/
Hey.
I've already forwarded this upstream, but there doesn't seem to be any
bug tracker, so re
Package: git-crecord
Version: 20220324.0-1
Severity: important
Hey.
I wanted to selectively stage (or commit) just two lines.
In both cases it fails with the same error:
$ git crecord
error: patch fragment without header at line 16: @@ -171,8 +171,8 @@ while [
"$#" -ge 1 ]; do
On branch improve
Hey Jonas :-)
On Thu, 2022-11-17 at 18:45 +0100, Jonas Smedegaard wrote:
> sorry if I was too terse previously
No worries... all is fine :-)
> but I disagree that introducing another prefix/suffix helps
> much.
I guess you're right...
> What helps the most, and also seems possibly, is to nam
forcemerge 661485 988384
stop
These two bugs are really identical, and as the reporter of the 2nd
already indicated in:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988384#10
they should be made duplicates.
Control: tags -1 + patch
Hey.
I've made a number of PRs in salsa, which fixes this issue:
https://salsa.debian.org/debian/smartmontools/-/merge_requests/5
and do some more improvements:
https://salsa.debian.org/debian/smartmontools/-/merge_requests/6
The latter would need to be coordinated wit
Control: tags -1 + patch
Hey.
I've made a number of PRs in salsa, which fixes this issue:
https://salsa.debian.org/debian/smartmontools/-/merge_requests/5
and do some more improvements:
https://salsa.debian.org/debian/smartmontools/-/merge_requests/6
The latter would need to be coordinated wit
On Thu, 2022-11-17 at 06:51 +0100, Jonas Smedegaard wrote:
> This has already been discussed upstream
Ah ok...
> upstream nowadays mention
> in their documentation that several distros name it "git-delta".
I had seen that, but it rather seems like a "some distros do that" -
not like a "we call
Hey.
Just some cosmetic point:
Should this really be called git-delta? It seems it's not just for git,
and upstream names it just "delta" (which is however already used by
some other package).
What about diff-delta? Or perhaps color-delta?
Or ideally asking upstream to pick a better name!? ;-)
Hey Craig.
On Tue, 2022-11-15 at 08:01 +1100, Craig Small wrote:
> >
> It can, but what we think the string is is not what the string
> actually is, I suspect.
> Each one of those 0x0 are delimiters, so if there was two of them at
> the end we would have:
> argv[0] DELIM argv[1] DELIM argv[2]
>
Hey Craig
On Mon, 2022-11-14 at 19:25 +1100, Craig Small wrote:
> I'm not sure why it is not matching, my test script above works fine.
> That was with 3.3.17-5
I also just tried again, with 2:3.3.17-7.1, and oddly enough it worked
again.
$ ps ax | grep mux
19557 ?Ss 0:00 ssh:
/h
On Sat, 2022-11-12 at 16:38 +0100, Axel Burri wrote:
> Have a look at the deb package, and location looks fine for me:
> ./etc/btrbk/btrbk.conf.example
Well but my point is, that I think in Debian it shouldn't be there, but
rater in:
/usr/share/doc/examples/btrbk.conf (no .example then).
> Th
Source: btrbk
Version: 0.32.5-1
Severity: wishlist
Hey Axel.
Actually I'm not even sure myself whether that's worth it ;-) ...
but what would you think about splitting off ssh_filter_btrbk
in a separate package?
I mean it's typically never used on the same host where btrbk runs,
unless perhaps
Package: btrbk
Version: 0.32.5-1
Severity: wishlist
Hey.
Typically, most package seem to put example configuration
like /etc/btrbk/btrbk.conf.example rather into
/usr/share/doc//examples
Cheers,
Chris.
Hey Diederik and Bastian
On Thu, 2022-11-10 at 13:07 +0100, Bastian Blank wrote:
> Those symlinks are included in linux-headers-6.0.0-3-amd64, see
> https://packages.debian.org/sid/amd64/linux-headers-6.0.0-3-amd64/filelist
>
> Did you remove that package as well?
You are both right, I have lin
Just noted, that part of what I wrote is probably bollocks. ^^
On Thu, 2022-11-10 at 03:37 +0100, Christoph Anton Mitterer wrote:
> $ ls -al 6.0.0-3-amd64/build 6.0.0-3-amd64/source
> lrwxrwxrwx 1 calestyo calestyo 36 Nov 5 14:41 6.0.0-3-amd64/build ->
> /usr/src/linux-headers-6
Source: linux
Version: 6.0.7-1
Severity: normal
Hey.
When I tried out some recent patch from the intel folks for i915,
I built a custom kernel as described in:
https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#s-common-official
Now before I installed the custom built de
Package: debian-kernel-handbook
Version: 1.0.20
Severity: normal
Hey.
Chapter 4.2.1.1. Disk space requirements explains how to disable debug info
during, build:
> You can disable debug info by changing the value of debug-info to false in
> debian/config/arch/defines, if it's set there, or in deb
Package: findimagedupes
Version: 2.19.1-1+b2
Severity: wishlist
Hey.
Version 2.20.1 is out :-)
Thanks,
Chris.
Package: libdvd-pkg
Version: 1.4.3-1-1
Severity: wishlist
Hey.
Just a minor thing, but I think /usr/src/libdvd-pkg/build/ could
always be removed after the script ran.
The /usr/src/libdvd-pkg/libdvdcss* files (especially
libdvdcss_1.4.3.orig.tar.bz2) I would however keep (unless of course the
p
Package: libdvd-pkg
Version: 1.4.3-1-1
Severity: wishlist
Hi.
AFAIU, right now we have libdvd-pkg, which is both:
- the package building the actual packages
- a "provider" package (for libdvdcss2 and libdvdcss-dev)
I think this removes quite some flexibility and it would be nice
to have these s
Actually, I noted that things are even more weird:
The first 0x0 should likely act as a string terminator anyway... so the matched
string shouldn't see any trailing newlines.
But even even these non-anchored patterns don't match:
$ pgrep --full --exact --euid "${LOGNAME}" --list-full -- "^ssh:
Package: procps
Version: 2:3.3.17-7.1
Severity: wishlist
Hey.
I have a script that matches on any ssh channel multiplexing process
(and then kills it) after printing them.
It basically does:
pgrep --full --exact --euid "${LOGNAME}" --list-full -- "^ssh:
${HOME}/\.ssh/mux/.+ \[mux]$"
Package: subnetcalc
Version: 2.4.19-1+b1
Severity: wishlist
Hey.
2.4.20 seems to be out :-)
Thanks and best wishes,
Chris
Package: firmware-iwlwifi
Version: 20221012-1
Severity: normal
Hey there.
My new Fujitsu Lifebook U7512 has some Intel USB Bluetooh device:
# lsusb -v -d 8087:0033
Bus 001 Device 009: ID 8087:0033 Intel Corp.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB
Package: openjdk-17-jre-headless
Version: 17.0.5+8-2
Severity: normal
Hey.
IIRC, this has happened with (all)? previous openjdk versions, when
transitioning from one major version to another, and presumably
also when simply purging openjdk.
The entries for update-binfmts are not correctly remov
Package: firmware-iwlwifi
Version: 20221012-1
Severity: normal
Hey there.
There possibly is a firmware file missing. In the kernel log I see:
# dmesg | grep -i wifi
[ 158.112234] Intel(R) Wireless WiFi driver for Linux
[ 158.114662] iwlwifi :00:14.3: firmware: failed to load
iwlwifi-so-a0
Hey.
Just for the records and the case that this group should ever be
removed:
usbguard uses it as one mean of authorizing users.
So should there be any change, one should probably visit usbguard, too.
Cheers,
Chris.
On Sun, 2022-10-30 at 19:00 +, Debian FTP Masters wrote:
> * Initial packaging (Closes: #995749)
Awesome... thanks! :-)
Cheers,
Chris.
On Sat, 2022-10-29 at 09:44 +0200, Salvatore Bonaccorso wrote:
> We do similar with intel-microcode updates, so maybe this is
> something
> we should consider to. But I think it's to early to think about a
> potential 20220913-1~deb11u1 via a bullseye point release.
It's just that for any bullseye
201 - 300 of 3723 matches
Mail list logo
