Package: git-doc
Version: 1:2.39.1-0.1
Followup-For: Bug #1027132
X-Debbugs-Cc: t...@mirbsd.de
This is still pertinent. In addition, the file is named weirdly;
I suspect a broken rename or something. In bpo, the file is named
properly but the same error presents:
$ install-docs --verbose --check
Debian FTP Masters dixit:
>Changed-By: Sebastian Andrzej Siewior
>Changes:
> xz-utils (5.4.1-0.1) unstable; urgency=medium
> .
> * Non-maintainer upload.
> * Update pt_BR translations.
> * Add lintian overrides and an override for blhc.
This is missing the updated Breaks+Replaces for
Helge Kreutzmann dixit:
>> >odler than stable. It also shipped them in every backport until
>> >4.16.0-3~bpo11+1. It is also in the upcoming 4.17.0-2~bpo11+1.
>> >
>> >But I wonder if I should remove them there.
>>
>> Yes, please. Otherwise it’s impossible to do the package
>Done in the upcoming
Hi,
did anyone ever test whether the tests that failed before succeeded
with the patch applied?
I have a reason to believe that the patch may be needed but the
comment on top is incorrect:
In https://lists.zytor.com/archives/klibc/2023-January/004705.html
a problem with klibc on mips64el was
Helge Kreutzmann dixit:
>odler than stable. It also shipped them in every backport until
>4.16.0-3~bpo11+1. It is also in the upcoming 4.17.0-2~bpo11+1.
>
>But I wonder if I should remove them there.
Yes, please. Otherwise it’s impossible to do the package
relationships right. This will leave
Hi Andreas,
a bit out of order, but easier to respond (I’m a bit under the
weather so excuse any issues ahead of time):
>By 'disabled' I assume you mean 'Never', right?
Uhm, short walkthrough:
• Native
• Full
• Never
• Yes
>Did it also create 10-no-sub-pixel.conf ?
Sebastian Andrzej Siewior dixit:
>It is bpo but if you look I'd you look at the files for the same
>version in bpo and sid you will see that sid skipped a few man pages
>while bpo created them.
Ouch!
That adds to the problems, of course. That makes fully resolving
this in all possible
Sebastian Andrzej Siewior dixit:
>Then I will update the versions as suggested. My understanding was the
>problem persists because the bpo version was not yet updated. The
>version in sid did not ship the man-pages.
The bpo version was once in both sid and testing and this
is therefore a problem
Sebastian Andrzej Siewior dixit:
>Okay. So I do nothing and just wait for the bpo package to appear which
>will then solve the problem?
No, you must fix the problem in xz-utils in bookworm/sid as well.
It also exists outside of backports.
bye,
//mirabilos
--
22:20⎜ The crazy that persists in
Helge Kreutzmann dixit:
>The problem is that we both upload (conflicting) packages to
>backports. I'm not sure a good solution exists here.
No, you need to fix the package relationships for incremental
and partial upgrades in sid anyway.
As far as I can tell, manpages-fr had the first version
Sebastian Andrzej Siewior dixit:
>> As far as I can tell it must be (<< 4.17.0-1~) instead.
>> (Also do note the tilde, it breaks bpo otherwise.)
>
>Okay. So I add this new suggested version and close 1028375?
I think so. 4.17.0-1 was the first version of -fr to not
ship it any more (from
reopen 1028375
found 1028375 5.4.1-0.0
thanks
Patrice Duroux dixit:
>Was this supposed to be closed? Or will it be with another manpages-fr bpo?
5.4.1-0.0 only conflicts with manpages-fr (<< 4.1.0-1)
so the upload did not fix the problem.
As far as I can tell it must be (<< 4.17.0-1~) instead.
Package: fontconfig
Version: 2.14.1-3
Severity: serious
Justification: Policy 10.7.3
X-Debbugs-Cc: t...@mirbsd.de
> * local changes must be preserved during a package upgrade, and
After an upgrade, etckeeper reports that
/etc/fonts/conf.d/10-sub-pixel-rgb.conf
shows up again, despite the local
On Thu, 26 Jan 2023, Yadd wrote:
> could you try attached patch ? It keeps related paths where needed.
Tested now (only one build, but should suffice), and yes, it does
the job.
Thanks,
//mirabilos
--
15:41⎜ Somebody write a testsuite for helloworld :-)
found 925358 1:7.2+dfsg-1+b2
thanks
Ben Hutchings dixit:
>and it certainly has been buggy on some architectures in the past. It
>seems to be solid now on real hardware.
It probably is. All tests now pass on ARAnyM, even using the mksh
binary built under qemu-user-static (and failing tests
Package: qa.debian.org
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
I’ve been seeing an FTBFS in the “Rep” column for a few days now
for a package that is merely unreproducible but does build twice
(dygraphs).
The same bad info shows up on tracker.d.o if that helps.
Package: snapshot.debian.org
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Packages from dpo used to show up¹ but now don’t²; I did check the
corresponding buildd status page to verify that there are Installed
build results, e.g. for riscv64 (and others).
①
Yadd dixit:
> could you try attached patch ? It keeps related paths where needed.
Not easily/right now, but it looks as if it does the job as well.
Thanks,
//mirabilos
--
15:41⎜ Somebody write a testsuite for helloworld :-)
Package: node-browser-pack
Version: 6.1.0+ds+~6.1.1-2
Severity: normal
User: reproducible-bui...@lists.alioth.debian.org
Usertags: buildpath toolchain
X-Debbugs-Cc: t...@mirbsd.de
Control: affects -1 src:dygraphs
var preludePath = opts.preludePath ||
path.relative(basedir,
Hi,
this is just to know that dygraphs (libjs-dygraphs) is now in Debian.
bye,
//mirabilos
--
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Package: snapshot.debian.org
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
The list of binary packages used to be sorted and no longer is,
making finding the right architecture more of a chore than
necessary.
Hi,
sorry for the late answer, only this afternoon I was in a
position to be able to test this.
I upgraded from libvirt* 6.9.0-4 to 7.0.0-3+deb11u1 from
bullseye-p-u, and python3-libvirt 6.1.0-1+b3 to 7.0.0-2,
and now things work for me.
Thank you,
//mirabilos
--
Infrastrukturexperte • tarent
On Mon, 9 Jan 2023, Mark Hindley wrote:
>Yes, That is the debootstrap one. However on a new installation, partconf then
>fills in the entries for the newly partitioned system[1]
Then you’ve identified which tool is responsible for ensuring that
either the respective fsck is installed or the
On Mon, 9 Jan 2023, Mark Hindley wrote:
>Yes, although I think the default fstab has pass=1 for root.
Nope. The default fstab is precisely this:
>> # UNCONFIGURED FSTAB FOR BASE SYSTEM
The person-or-thing which enters a line with pass ≠ 0 is
responsible for ensuring (first!) that the fsck
On Mon, 9 Jan 2023, Mark Hindley wrote:
>> fsck is util-linux, not e2fsprogs.
>
>Yes, but fsck.ext4 is e2fsprogs and that is what is missing in #1028181.
But that’s ⓐ the user’s problem and ⓑ not necessarily an error
as there exist filesystems for which no fsck binary exists.
(If the user has
On Mon, 9 Jan 2023, Lorenzo Puliti wrote:
>This package "only" recommands e2fsprogs, so I think it should just
fsck is util-linux, not e2fsprogs.
bye,
//mirabilos
--
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: t...@mirbsd.de, team+postgre...@tracker.debian.org
* Package name: pguint
Version : 1.20220601
Upstream Author : Peter Eisentraut
* URL : https://github.com/petere/pguint
* License : The PostgreSQL License
Package: vrms
Version: 1.32
After “apt-get purge vrms”, the new check-dfsg-status package is
free’d for autoremoval. This is because the vrms package is not
a transitional package as it’s not in Section oldlibs (at least;
may be other reasons but I cannot find where it says the conditions
right
Package: linux-headers-5.10.0-20-common
Version: 5.10.158-2
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
I think I reported the same thing against experimental some time ago,
but it now is a regression in stable. Building kernel modules shows:
tglase@tglase-edge:~/lnx/master/janz $ make
make -C
Donald Buczek dixit:
> To be fair, this daemon doesn't use /proc/pid/stat for that, but
> /proc/pid/comm
Yes, and that’s proper. The field in /proc/pid/stat is size-limited
and so not necessarily distinct.
> As /proc/pid/stat is also used in many places, it could as well use
> that to avoid
Donald Buczek dixit:
>No, Escaping would break existing programs which parse the line by
>searching for the ')' from the right.
Huh? No!
The format is "(" + string + ") " after all, and only the string
part would get escaped.
The only visible change would be that programs containing a
On Sat, 26 Nov 2022, Alexey Dobriyan wrote:
>/proc never escaped "comm" field of /proc/*/stat.
Yes, that’s precisely the bug.
>To parse /proc/*/stat reliably, search for '(' from the beginning, then
>for ')' backwards. Everything in between parenthesis is "comm".
That’s not guaranteed to stay
Package: ksh93u+m
Version: 1.0.4-2
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
The manpage documents the time construct but it does
not seem to be available.
ksh_2020.0.0+really93u+20120801-9 is also affected.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
# this is for a nōn-release architecture
severity 1026002 important
# this is a bug in the imake buildsystem, not xlax which merely uses it
reassign 1026002 xutils-dev
retitle 1026002 xutils-dev: imake support for riscv64 vanished?
affects 1026002 src:xlax
thanks
sun min dixit:
>xlax failed to
Andres Salomon dixit:
> youtube-dl was a bad idea, and we should instead have a users and packages
> manually switch.
How do you consider making users do so?
Add an otherwise empty youtube-dl binary package to src:yt-dlp
with both README.Debian and NEWS.Debian (for apt-listchanges)
telling them
Andreas Tille dixit:
>it at all. I'm also wondering whether the string
>
> 2021.12.17+really-yt-dl-2022.11.11-1
>
>is a better version number than just increasing the Debian revision.
Why not just use the upstream version? It’s newer after all:
2022.11.11-1
What are the respective
Dixi quod…
>I also had a grml-efi VM lying around, which incidentally already
>had a virtio-scsi configured, so I did the same thing: drop the
>SATA CD, re-add it as an SCSI HDD, change the boot order, start.
>It switches from “the guest has not initialised the display yet”
>to “viewer was
dann frazier dixit:
>Sure, I thought that was implied since this is a UEFI firmware bug. To
>be clear, my testing was with UEFI boot enabled.
Ah okay. That was not clear to me, because you only referred to
the SCSI part.
>Do you believe it is new/different because you assumed I was not using
>a
Hi dann,
>OK, then I think there may be multiple conflated issues here. Let's
>focus on the original use case you described - a VM created with
>virt-manager using a SCSI controller doesn't work. You tried
Nonono, not quite.
The original use case: an *EFI* VM with a SCSI controller does not
Package: lintian
Version: 2.115.3
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
The update-debian-copyright tag gives bad advice:
N: The most recent copyright year mentioned for files in ./debian lags behind
N: the year in the timestamp for the most recent changelog entry.
This is a fully
severity 1017760 normal
retitle 1017760 linux: possible data corruption on µSD card, might be the
hardware though?
thanks
Dixi quod…
>I have somewhat reason to at least suspect the µSD card this was
>installed on. But there was never anything in syslog/dmesg about
>it, so the Linux kernel
Hi dann,
> Could you confirm the last version that worked for you - perhaps
I have never booted an EFI system before; this VM was the first
time for me, so I do not have a “last version” either way.
As I said, this does work with BIOS (or at least used to).
bye,
//mirabilos
--
[...] if maybe
Paul Eggert dixit:
> Although you sent your email to 36...@debbugs.gnu.org /
> 930247@bugs.debian.9org, your email is reporting a separate bug
Oh OK, I wasn’t aware, it sounded similar enough.
> I fixed it in the development version of GNU grep by installing the
> attached patch. This patch
be on a ramdisc and which,
iff leaving around at all, I’d have expected on /var/tmp/
instead (especially during composition time, i.e. before
sending). Might want to move that.
-- Package-specific info:
** Environment settings:
EDITOR="/usr/bin/sensible-editor"
VISUAL="/usr/bin/jupp"
Package: grep
Version: 3.6-1
Followup-For: Bug #930247
X-Debbugs-Cc: t...@mirbsd.de
Control: found 930247 3.8-3
Control: severity 930247 serious
Control: retitle 930247 grep: does not handle backreferences correctly,
violating POSIX
I’m running into this, in stable and unstable both:
Hi Paul,
> I looked at the results of the autopkgtest of your package. I noticed that it
> regularly fails. Also the failures on arm64 seem consistent now in testing
> (but
> it has a pass in unstable).
thanks for bringing this to my attention. This is a bug in the
autopkgtest script in that it
block 1024984 by 686777
thanks
Hello Bo YU,
>The package can be built on riscv64 arch and this is tested on my
>local real riscv64 machines.
the package can even be built on big endian architectures, but it
won’t work right there at the moment.
The current situation is that we have to use
close 930522
thanks
Salvatore Bonaccorso dixit:
>Is this issue still reproducible with a recent kernel?
I haven’t seen it in a while, indeed.
Package: linux-headers-amd64
Version: 6.0.8+1
Severity: minor
X-Debbugs-Cc: t...@mirbsd.de
apt-listchanges: Reading changelogs...
Calling ['apt-get', '-qq', 'changelog', 'linux-headers-amd64=6.0.8+1'] to
retrieve changelog
apt-listchanges: Unable to retrieve changelog for package
Dixi quod…
>The effect is that /proc/[pid]/stat cannot be parsed the way it is
>documented, as it does not escape embedded whitespace characters;
… nor parenthesēs:
tglase@x61w:~ $ ./mk\)sh -c 'echo $$; sleep 10' &
[1] 13375
tglase@x61w:~ $ 13375
tglase@x61w:~ $ cat /proc/13375/stat
13375
Package: src:linux
Version: 5.10.149-2
Severity: normal
Tags: upstream
X-Debbugs-Cc: t...@mirbsd.de, adobri...@gmail.com
tglase@x61w:~ $ cp /bin/mksh mk\ sh
tglase@x61w:~ $ ./mk\ sh -c 'echo $$; sleep 10' &
[1] 12862
tglase@x61w:~ $ 12862
cat /proc/12862/stat
12862 (mk sh) S 12649 12862 12649
Mike Hommey dixit:
>Neither Chromium nor Firefox currently implement RFC6874.
That’s the point of this bugreport. It works in lynx, but lynx
was not sufficient to configure this picky network device. The
link-local IP address was the only way to reach it without a
full factory reset, due to…
Mike Hommey dixit:
>> >Try removing that %eth0 from the ipv6 address.
>>
>> That would invalidate said address and is therefore impossible.
>
>Why would it? Is your setup so complex that the network stack can't find
>the right interface to send packets through?
It’s a link-local address. These
Mike Hommey dixit:
>Try removing that %eth0 from the ipv6 address.
That would invalidate said address and is therefore impossible.
It works in lynx, if knowing that helps.
bye,
//mirabilos
--
> emacs als auch vi zum Kotzen finde (joe rules) und pine für den einzig
> bedienbaren
Package: firefox-esr
Version: 102.5.0esr-1~deb11u1
Severity: serious
Justification: violates a Debian Etch release goal
X-Debbugs-Cc: t...@mirbsd.de
see attached screenshot
-- Package-specific info:
-- Addons package information
-- System Information:
Debian Release: 11.5
APT prefers
tags 749603 + pending
thanks
I managed to solve the last remaining problem tonight, to port it and
make it build using node-babel 7, which we have in Debian. I expect to
upload a package soonish, although a lot of testing is needed still…
bye,
//mirabilos
--
Infrastrukturexperte • tarent
Package: wnpp
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de, d...@debian.org
Control: affects -1 src:jamulus
I intend to orphan the jamulus package. I am reducing my involvement
in post-bullseye Debian.
The package description is:
Jamulus, a low-latency audio client and server, enables
Package: wnpp
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Control: affects -1 src:antimicro
I intend to orphan the antimicro package. I am reducing my involvement
in post-bullseye Debian.
The package description is:
AntiMicroX is a graphical program used to map keyboard keys and mouse
On Fri, 21 Oct 2022, Rene Engelhard wrote:
> Maybe time to get hardware from this or last century even?
Excuse me! That’s so totally not acceptable.
Debian runs on such machines, and I personally also have an EeePC,
and, to reduce electronic waste, reusing of older machines is
perfectly fine.
tags 1021766 unreproducible
thanks
Hi madduck,
>Wanting to replace xscreensaver with something better, I took a look
>at xidle. Unfortunately, the simple call
>
>```
>xidle -program /usr/bin/xsecurelock -timeout 5
>```
>
>doesn't cause `xsecurelock` to be spawned after 5 seconds. According
I
Package: firefox-esr
Version: 102.3.0esr-1~deb11u1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de, t...@security.debian.org
Since the upgrade to 102 in bullseye, Ctrl-Shift-T does not work any more.
Upon looking in the menu, “Recently Closed Tabs” is greyed out instead of
listing these as before.
Vagrant Cascadian dixit:
> succeeded-tested[1_(1_ignored)f/576p]·lksh_musl=✓
Oh right… another occurrence, I had only looked for the reported one.
Thanks for noticing,
//mirabilos
--
Gestern Nacht ist mein IRC-Netzwerk explodiert. Ich hatte nicht damit
gerechnet, darum bin ich
László Böszörményi (GCS) dixit:
> Please note that src:sqlite and its binary packages are not part of
>Bullseye. The package you have installed on your system is a leftover
Oh, hmm.
>probably from Buster. For this reason I can't change a non-existing
That or from sid; this used to be a sid
Package: libsqlite0
Version: 2.8.17-15
Severity: important
X-Debbugs-Cc: t...@mirbsd.de
This library package lacks the Multi-Arch: same annotation
but looks like it could easily get it.
I have legacy applications that are hard to recompile for which I
need libsqlite0:i386, but to install that
On Thu, 6 Oct 2022, Emmanuel Bourg wrote:
> It appears that this idea has been implemented last year with the
> orphan-sysvinit-scripts package, under the Debian sysvinit maintainers
> umbrella. It was released with Bullseye and already contains an init script
> for tomcat9.
A very broken init
For the record, -hpn is a contemporary patchset for high-performance
SSH throughput and actively maintained, from what I gather from the
OpenSSH mailing list.
And the bug isn’t restricted to that… I had the corresponding Launchpad
bug subscribed, so it must have hit me at some point.
I agree
Hi Chris,
> -| FAIL ../../check.t:heredoc-tmpfile-8 (ignored)
> -| Total failed: 1 (1 ignored)
this test is unfortunately fragile. It occasionally fails depending
on system “load” (but not load average), and I haven’t found a way to
make the fragility go away. (If someone does, by all means,
Package: devscripts
Version: 2.21.3+deb11u1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
(shortened a bit)
u@u:~/Projekte $ dget -d
http://deb.debian.org/debian/pool/main/t/tomcat9/tomcat9_9.0.67-1.dsc
dget: retrieving
http://deb.debian.org/debian/pool/main/t/tomcat9/tomcat9_9.0.67-1.dsc
%
Hi Aurelien,
>Starting with glibc 2.35, we do not patch the glibc to add C.UTF-8
>support, instead we use the upstream code which comes with the following
>NEWS entry [1]:
[…]
Thanks for the extra info.
>> They are as mandated by POSIX for the C locale. I believe I said
>> in my original 2013
Also, where’s the NEWS entry apt-listchanges would have mailed me
to document this change in behaviour?
(Might as well place the documentation I requested in the previous
eMail there, so others will also find it.)
bye,
//mirabilos
--
22:20⎜ The crazy that persists in his craziness becomes a
Kurt Roeckx dixit:
>On Sat, Sep 24, 2022 at 10:34:19PM +0200, Thorsten Glaser wrote:
>> $ openssl s_client -CApath /etc/ssl/certs -connect www.mirbsd.org:443
>> -legacy_renegotiation -tls1
>
>TLS 1.0 is not supported by default because it's insecure. You need
>to change
Package: locales
Version: 2.35-1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
While adjusting my localedata patch script to the latest glibc uploads
I discovered a surprising difference in some categories — for example:
(sid-amd64)tglase@tglase:~ $ LC_ALL=C ./tstspc
U+0009
U+000A
U+000B
U+000C
Package: openssl
Version: 3.0.5-4
Severity: serious
Justification: does not work any more
X-Debbugs-Cc: t...@mirbsd.de
$ openssl s_client -CApath /etc/ssl/certs -connect www.mirbsd.org:443
-legacy_renegotiation -tls1
CONNECTED(0003)
depth=2 C = US, O = Internet Security Research Group, CN =
tags 1020464 - unreproducible
thanks
Paul Wise dixit:
>Perhaps your browser or an extension is adding the cookie?
It’s lynx, so… no ☻
>Searching for the name indicates this is a GitLab/salsa cookie,
>but I would expect that would set the cookie on salsa.d.o not d.o.
>
Package: www.debian.org
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Why does the website set this cookie, or a cookie at all?
These are, preferences or logins aside, normally a sign of
bad behaviour like user tracking, and I’d say frowned upon
in the project.
severity 1020367 minor
thanks
fab...@debian.org dixit:
>you are receiving this bug report, because your package declares a
>relationship with the gsfonts and/or gsfonts-x11 packages. Both
>packages have been replaced by fonts-urw-base35 since version
>20200910-2 and are now merely transitional
tags 1020058 + pending
thanks
Hi Lucas,
>Relevant part (hopefully):
>> /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=.
>> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
>> -D_FORTIFY_SOURCE=2 -std=c++0x -g -fPIC -fPIE -Wl,-z,relro -Wl,-z,now
>> -Wl,--as-needed -rdynamic
Package: lintian
Version: 2.115.3
Followup-For: Bug #1019235
X-Debbugs-Cc: t...@mirbsd.de
Spotted this too, please fix it, licence is proper English spelling,
not oversea barbarian dialect.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500,
On Sun, 11 Sep 2022, Samuel Thibault wrote:
> The problem is that apparently debootstrap doesn't handle Replaces, and
Apparently, it also doesn’t handle Provides (which would fix this).
Sad.
bye,
//mirabilos
--
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn •
Thorsten Glaser dixit:
>I’ve recently been getting filesystem corruption on this system, which,
>incidentally, is a fresh-ish installation since I’ve been hit by the
I have somewhat reason to at least suspect the µSD card this was
installed on. But there was never anything in syslog/dmesg
Package: qa.debian.org
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
Look at https://packages.qa.debian.org/b/bash.html
bugs
all [93]bug history graph
[94]406 ([95]433)
RC
[96]0
I
[97]275 ([98]295)
M
[99]131 ([100]138)
F
close 95165
thanks
herb...@gondor.apana.org.au dixit:
>CVS is too strict on errors writing to stdout, e.g., if I do a cvs log
>piped to less, and then quit before reading the complete result, cvs says:
>
>cvs [log aborted]: received broken pipe signal
>Write failed flushing stdout buffer.
>
>and
close 67895
thanks
I’d very much prefer to close this debbugs item, since it’s not a bug,
works both as designed and documented, with the submitter having been
quiet for well over a decade, and it just sitting here attracting spam;
archival will take care of the latter, for new spam anyway.
retitle 749603 ITP: libjs-dygraphs -- fast and flexible JavaScript charting
library
owner 749603 t.gla...@tarent.de
thanks
Against, probably, better knowledge, I’ll try to package this.
I have an experiment for a customer in which I can probably use
it, and might even fix minor bugs.
The
Package: src:linux
Version: 5.10.136-1
Severity: important
X-Debbugs-Cc: t...@mirbsd.de
My network just ceased working, and I can’t get it back up,
even with rmmod.
More log follows. Notes (more inline):
• those “Microcode SW error detected” seem to be normal,
I’m getting those all the time
On Sat, 3 Sep 2022, Helge Kreutzmann wrote:
> The upload of manpages-l10n (manpages-fr) was just accepted in
> unstable.
OK, thanks.
AIUI we now need another upload of src:sysvinit in which bin:bootlogd
gets a Replaces and Breaks on manpages-fr (<< 4.15.0-9~), correct?
I can do that this
Hi Helge,
[…]
> Yes, that would be the best option. A few days ago I informed all
> translation teams about the transfer of translations to sysvinit, so
> if the French team could integrate the translation of bootlogd there,
> that'll be great.
ok, great!
> For Debian, as stated above, I can
On Wed, 31 Aug 2022, Mark Hindley wrote:
> > there seems to be one manpage (in bootlogd) missing conflict handling:
> >
> > /usr/share/man/fr/man8/bootlogd.8.gz
>
> Thanks. I was under the impression that manpages-i10n had changed to
> systemd versions (which doesn't have bootlogd.8) but
On Wed, 31 Aug 2022, S. wrote:
> laptop. It would be great if the 20210818-1 firmware version could be offered
> in Backports.
Backports are not to fix bugs in stable. Issues like this should
be fixed via the normal stable channels if possible and the normal
bugtracker is used to track that.
Package: linux-headers-5.19.0-trunk-amd64
Version: 5.19-1~exp1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
In building an out-of-tree kernel module I wrote on 5.19 (to test
compatibility), I noticed a new error message.
/usr/lib/linux-kbuild-5.19/scripts/Makefile.modfinal emits the
message,
Package: qa.debian.org
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
There used to be a box (or something, I mostly use this with lynx)
for testing migration status, but it’s apparently now missing.
I know tracker.d.o has it, but that site’s appalling in UI/UX and
looks awful and it’s much
outlook 1017537 some armel buildds are misconfigured and lack SWP emulation
thanks
Dixi quod…
># if __ARM_ARCH__ < 6
> swp r0, r1, [r2]
># else
And this, after some research, is it. This is needed for armel, which
is v5. Apparently, Linux has SWP emulation for v7/v8 hosts, but at
Dixi quod…
>In case this makes anyone immediately think of whatever it is:
Code looks right enough (with an explanation of why this only
fails on armel but not on armhf which is perfectly fine):
$ cat arm/__testandset.S
#include "arm-features.h"
FUNC_START __testandset
mov r2,
>but it ALSO fails in a bullseye chroot, so this is possibly not related
In case this makes anyone immediately think of whatever it is:
(gdb) r
Starting program: /home/tg/dietlibc-0.34~cvs20160606-el-11/debian/unittests/ttt
Program received signal SIGILL, Illegal instruction.
__testandset () at
outcome 1017537 fails on porterbox/bullseye as well, suspect 64-bit host to be
an issue
tags 1017537 + help
thanks
In contrast to armhf, which works fine on the porterbox (amdahl; abel,
which I normally use, is currently down) for me, this one also fails,
but it ALSO fails in a bullseye chroot,
tags 1017538 + unreproducible
thanks
This builds fine in a sid-armhf chroot on amdahl.
Markus Koschany dixit:
>The --add-opens error message was misleading and it turned out the underlying
>root cause for the FTBFS was a different one. Gradle currently fails to build
>because of a different jansi bug.
OK, so keep that one open and close this one?
>There is still some work to do
Markus Koschany dixit:
>The newly added --add-opens option is only valid for OpenJDK 17. I
>understand that we switch to it for Debian 12 but it currently breaks
>all packages that are built with OpenJDK 11. I am currently in the
Is this true? AFAIK --add-opens is for 11+ (probably even 9+). It
Package: src:linux
Version: 5.10.136-1
Severity: grave
Justification: causes non-serious data loss
X-Debbugs-Cc: t...@mirbsd.de
I’ve recently been getting filesystem corruption on this system, which,
incidentally, is a fresh-ish installation since I’ve been hit by the
“forgot LUKS password for
Arnd Bergmann dixit:
>The way the FPU type gets selected in gcc changed with recent versions,
>this was intentional and won't be reverted but it did break packages that
>used the old method.
Hmph.
>In most cases, it's sufficient to pass
>-march=armv7-a+fp instead of -march=armv7-a to pick the
301 - 400 of 4542 matches
Mail list logo
