Bug#976678: dstat: upgrade warnings when upgrading from python3.8 to python3.9

[Cam Hutchison]

On Sun, 6 Dec 2020 16:31:18 -0500 Andres Salomon  wrote:
>
> --- /usr/share/dstat/dstat_squid.py.orig 2020-12-06 16:24:39.563332096 -0500
> +++ /usr/share/dstat/dstat_squid.py 2020-12-06 16:25:02.959555941 -0500
> @@ -45,7 +45,7 @@
>  if op.debug > 1: print('%s: lost pipe to squidclient, %s' % 
> (self.filename, e))
>  for name in self.vars: self.val[name] = -1
>  except Exception as e:
> -if op.debug > 1: print('%s: exception' (self.filename, e))
> +if op.debug > 1: print('%s: exception' % (self.filename, e))
>  for name in self.vars: self.val[name] = -1
>
>  # vim:ts=4:sw=4:et
> --- /usr/share/dstat/dstat_mysql_keys.py.orig 2020-12-06 16:24:48.231415192 
> -0500
> +++ /usr/share/dstat/dstat_mysql_keys.py 2020-12-06 16:25:22.959746212 -0500
> @@ -38,7 +38,7 @@
>  for name in self.vars: self.val[name] = -1
>
>  except Exception as e:
> -if op.debug > 1: print('%s: exception' (self.filename, e))
> +if op.debug > 1: print('%s: exception' % (self.filename, e))
>  for name in self.vars: self.val[name] = -1

These changes are not quite right. Adding the percent will work but
there is only one %s in the format string, so there should be only
one argument on the right-hand side of the percent. Possibly more
correct and useful is to change the print statement to

print('%s: exception: %s' % (self.filename, e))

That will print out the exception message too, which would probably be
useful.

Bug#938927: Bug#986435: ITP: libthrift-java -- Java language support for Thrift

[Andrius Merkys]

Hi Markus,

On 2021-04-06 00:33, Markus Koschany wrote:
> libthrift-java is a new build-dependency for apache-jena, the latest
> version of mediathekview and possibly cassandra (ITP: #585905). Since
> there was no reaction to #938927 for 1,5 years now, I intend to
> re-introduce the old libthrift-java package and maintain it within the
> Debian Java team.

Thank you for reintroducing libthrift-java. I think #938927 can now be
closed in favor of #986435.

Best,
Andrius

Bug#955493: network-manager-fortisslvpn: new upstream available

[Apostolos Kefalas]

Please package 1.3.9. I need the interactive connect (OTP via SMS)

Thanks!!!



On Wed, 1 Apr 2020 17:12:22 +0200 Mattia Rizzolo  wrote:
> Source: network-manager-fortisslvpn
> Version: 1.2.8-2
> Severity: wishlist
> 
> Dear maintainer,
> 
> There is a new upstream release that implements a few new things,
> amongst which it exposes the "realm" settings, which is required for
> some networks.
> 
> -- 
> regards,
> Mattia Rizzolo
> 
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> More about me:  https://mapreri.org : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

Bug#971956: (No Subject)

[Jaycee Santos]

Is it possible to also mention the bullet point on this page?
https://wiki.debian.org/CUPSDriverlessPrinting#vendor

"USB print queues previously set up with vendor drivers (HP, Brother,
Canon, Samsung etc) will amost certainly cease to work, so they become
candidates for deletion. In fact, a user could consider removing the
vendor software completely as it doesn't provide any useful function
unless it is intended to switch between IPP-over-USB and vendor
drivers."


Jaycee

Bug#986152: [Shorewall-devel] Bug#986152: RFH: shorewall -- Shoreline Firewall, netfilter configurator

[Thom M Eastep]

I can come out of retirement enough to fix the issues in upstream... It sure 
would be great if we could get the final stable Shorewall packages into Debian.

Tom

On March 30, 2021, at 7:09 AM, "Roberto C. Sanchez"  
wrote:

Package: wnpp
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I request assistance with maintaining the shorewall package.

The package description is:
 Shorewall allows firewall/gateway requirements to be described using
 entries in a set of configuration files. It reads those configuration
 files and, with the help of the iptables utility, configures
 netfilter to match these requirements.
 .
 Shorewall supports a wide range of router/firewall/gateway applications,
 traffic shaping and almost every type of VPN.

I have maintained the Shorewall packages in Debian for quite a few years
now, but my time to work on them has diminished.  The reality is that
there are several issues that require attention, which I cannot at the
moment attend to.  Over time the severity of these issues will likely
increase and the eventual result is that the Shorewall packages could be
removed from Debian.

If someone were to be able to devote some effort toward helping, I could
help with reviewing patches, sponsoring uploads, etc.  It is still my
hope that I will find additional time to work on the Shorewall Debian
packages, but I do not want to make my inability to find enough time now
cause users of Debian to lose out on access to good quality Shorewall
packages.

Note that this RFH really encompasses the shorewall, shorewall6,
shorewall-lite, shorewall6-lite, shorewall-doc, and shorewall-core
source packages.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEIYZ1DR4ae5UL01q7ldFmTdL1kUIFAmBjLvUACgkQldFmTdL1
kUI9pA/9FqVYHab6iWdVfUpMm8hzCDYLEs1SRk3cIDWyMWWkGS5Me/gXKi0tok+0
EIN/I6jjaTctM/atDFuq3u8c8exdqrCszeIrrjjPiS1uKhUwYPc0N+obu5RHohOt
ns2F2vhg9C/pSMH1J4g1JWwQA5sqjxXWoP4WxhS8H5JdcxBI48pPETFuG4dsJQQx
SiwmA53PqrBao8c1p3c0Z+efDhIZgUp5GRANS9lbzCtNsj0s7zH/tHqsjtP82Jy+
IKJccPv5u1X/ChRf6AITD7fI9Xsn3qcxikfZgD5O0Yd9/AGJtbsR590yw4jZHFYZ
qIYFEOGJslYOXx4brAq5Cweevw9VzvIyjPeBjtKoOGYbSadH7+A357UIOqBUWvji
ZEaMVeO2V0s29+2RYE4A1bvbqOSkuuDQ6WG9z1z8qE2UhN4G65sljw6tYPtDOGZ3
N2jkBHo1N+9+OuC2rjKkuCfF1yfgVNbvlSUjMidNnjWRiW+PA6o7cVK8c8fuYQK3
ML/Pvib2LvEoyeetTPWijcnePr/Wrw5U0OeRxCNAXxfFBw4/JSyqudF/wiuvEfUV
hqEjttomIEkcSF8bf81DvQoxzjBnnQjrFS566esUR71VAjGuqEk4WVaL0ENhPNxL
Fjkjt5xIckCJIdvmCDPaRz66MrSPMGY+JX3eBjvGp33wgKJLVsY=
=apRC
-END PGP SIGNATURE-


___
Shorewall-devel mailing list
shorewall-de...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/shorewall-devel

Bug#986396: lrzip: extreme low compression ratio in large files with latest program versions

[Con Kolivas]

This was fixed in 0.641. Urge everyone to update.

Thanks

On Mon, 5 Apr 2021 at 17:03, Jose Antonio Castro  wrote:
>
> Package: lrzip
> Version: 0.640-1
> Severity: normal
> X-Debbugs-Cc: tonio.cas...@gmail.com
>
> Dear Maintainer,
>
> I use lrzip for compress large (~5Gb) database dumps. With old versións (like 
> 0.631) i get a file over 400Mb, but with the lasts versións I get a ~3Gb file.
>
> Thanks and excuse my English.
>
>
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers testing-security
>   APT policy: (500, 'testing-security'), (500, 'testing'), (2, 'unstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 5.10.0-1-amd64 (SMP w/8 CPU threads)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not 
> set
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
>
> Versions of packages lrzip depends on:
> ii  bash5.1-2+b1
> ii  libbz2-1.0  1.0.8-4
> ii  libc6   2.31-11
> ii  libgcc-s1   10.2.1-6
> ii  liblz4-11.9.3-1
> ii  liblzo2-2   2.10-2
> ii  libstdc++6  10.2.1-6
> ii  zlib1g  1:1.2.11.dfsg-2
>
> lrzip recommends no packages.
>
> lrzip suggests no packages.
>
> -- no debconf information

Bug#986288: poke in Debian

[Sergio Durigan Junior]

On Monday, April 05 2021, Adam Borowski wrote:

> On Mon, Apr 05, 2021 at 11:59:00PM +0100, Sudip Mukherjee wrote:
>> On Fri, Apr 2, 2021 at 4:57 PM Hilko Bengen  wrote:
>> > Oh, I hadn't noticed because it was only uploaded to experimental. Will
>> > contact the packager.
>> 
>> I think that is because it is recommended not to upload anything to
>> unstable which is not meant for Bullseye.
>
> There's no difference for packages without a version in testing.

There isn't, but I'm not uploading anything to unstable until the freeze
is over, including packages that are new.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/


signature.asc
Description: PGP signature

Bug#986417: system-information kernel-resume

[l0f4r0]

I have the same kind of issue on stable with the backported kernel 
5.10.19-1~bpo10+1: black screen after resuming from sleep.
It happened with kernel 5.10.13-1~bpo10+1 as well.
The warkaround I found is to put down the lid, wait a little bit and reopen it 
one more time. No need to reboot.
It has never failed for me.

The issue is indeed somewhat random (it's KO around 50% of the time).

Bug#892275: Redshift under xfce4

[smarios]

Hi,

chipping in with my experience under xfce4. First, I'm using a manual 
config file with lat./long. information, so I can't comment on the 
geoclue part of the conversation. However, I had problems when trying to 
manually kill redshift, because systemd would restart the service, 
ending up with my screen getting progressively more red..


To summarize, my current solution is to deactivate the systemd service 
and use xfce4 specific session startup along with a manual config file. 
Hope this helps someone.

Bug#986441: mirror listing update for mmc.geofisica.unam.mx

[Antonio Carrillo Ledesma]

Package: mirrors
Severity: minor
User: mirr...@packages.debian.org
Usertags: mirror-list

Submission-Type: update
Site: mmc.geofisica.unam.mx
Type: leaf
Archive-architecture: ALL amd64 arm64 armel armhf hurd-i386 i386 kfreebsd-amd64 
kfreebsd-i386 mips mips64el mipsel powerpc ppc64el s390x
Archive-http: /debian/
Archive-rsync: debian/
Maintainer: Antonio Carrillo Ledesma 
Country: MX Mexico
Location: Instituto de Geofisica, UNAM
Sponsor: Grupo de Geofísica Computacional  http://mmc.geofisica.unam.mx/




Trace Url: http://mmc.geofisica.unam.mx/debian/project/trace/
Trace Url: 
http://mmc.geofisica.unam.mx/debian/project/trace/ftp-master.debian.org
Trace Url: 
http://mmc.geofisica.unam.mx/debian/project/trace/mmc.geofisica.unam.mx

Bug#986440: Please consider Recommends: gstreamer1.0-libav on libfaudio0

[Forest]

Package: faudio
Version: 21.02-1

Dear maintainer,

The WMA codec is critical to many games that rely on FAudio, which (in
recent versions) depends on GStreamer to handle that codec.
https://github.com/FNA-XNA/FAudio/commit/7f52bfb66b73cca2522537f45977886958a06324

Unfortunately, the GStreamer plugin that provides that codec is not
installed by default, which leaves gamers with broken sound and no obvious
path to fix it.  Also, folks who upgrade from an older libfaudio0 package
may find their formerly-working games suddenly without sound.

Adding Recommends: gstreamer1.0-libav to the libfaudio0 package would be
helpful here.  Would you please consider it?

Bug#985946: patch proposal

[David Bannon]

Topic : tomboy-ng not working on ppc64el

Frédéric, I have now done some testing using a more recent version of
qemu and results are somewhat mixed.  My plan was to install the Debian
versions of FPC and Lazarus, build my app and run it under the IDE
debugger. However, I encountered several problems long before I un-tared
my source.  Now, I am a new qemu user and have not worked on POWER for a
very long time, but I believe I found first a Lazarus packaging problem,
then I built Lazarus from source (my prefered model) and found more
issues that relate, I think, to LCL, particularly under Qt5.  So, in my
very uneducated opinion, Lazarus is not yet ready for ppc64el and as its
not on the Lazarus's supported list, they won't be very interested in
finding out why that is.  They would definitely accept patches but a bug
report with no solution will not attract a lot of attention.

I suggest its not really a very good idea to list Lazarus as a supported
Debian package on ppc64el. FPC is fine, but not Lazarus. Just my opinion.

Given the Debian Testing feature freeze, is there scope to address the
Lazarus problems I have found ?

Davo

Bug#237410: Attn:💖 We rounded up the best and unique gift ideas for each member of the group.

[Trần Ngọc Nam - Kiến Tạo Tuổi 20]

[image: Amazing Gift Ideas For You And Familly]


Shop Canvas Shoes for Women & Men discover the latest styles at Temogear.
[image: New Spring Fashion Women Canvas Shoes]

ORDER YOURS NOW 

Shop our collection of sneakers, shoes . Find your fit for the field or the
street at the Temogear.
You may also like:
[image: Woman Platform Shoes] 
BUY NOW 
[image: Canvas Shoes Woman] 
BUY NOW 
If you no longer wish to receive our emails, click the link below: Unsubscribe

Zolatee Store - 234 Front Street, Floor 3, San Francisco, CA 94111

Bug#986408: lsb-release: ValueError: could not convert string to float: '6.06 LTS' (was Re: Bug#986408: mali-midgard-dkms: Fail to install/build)

[Thorsten Glaser]

Christian Marillat dixit:

>A patch is available here :
>
>https://itectec.com/ubuntu/ubuntu-ubuntu-18-04-stuck-on-verbose-screen-on-startup/

You could have attached it so it’s easier for the maintainers.
I’m hereby doing that.

begin 644 986408.patch
M+2TM(&QS8E]R96QE87-E+G!Y"3(P,3DM,#,M,#D@,3DZ,S`Z-3(N,#`P,#`P
M,#`P("LP,3`P"BLK*R!L0DR,#(Q+3`T+3`V(#`R.C`S
M.C0W+C(W-#DU,#0Y-"`K,#(P,`I`0"`M-#4L-R`K-#4L-R!`0`H@("`@(&=L
M;V)A;"!214Q%05-%7T-/1$5.04U%7TQ/3TM54"P@4D5,14%315-?3U)$15(L
M(%1%4U1)3D=?0T]$14Y!344*("`@("!214Q%05-%7T-/1$5.04U%7TQ/3TM5
M4"`]('L@3UL86UB9&$@;CH@9FQO870H;ELP
M72YS<&QI="@I6S!=*2D*("`@("!214Q%05-%4U]/4D1%4B`](&QI

Bug#986408: mali-midgard-dkms: Fail to install/build

[Wookey]

On 2021-04-05 14:32 +0200, Christian Marillat wrote:
> Package: mali-midgard-dkms
> Version: 16.0+pristine-4
> Severity: serious
> 
> Dear Maintainer,
> 
> This package fail to install/build with :

Hmm. I meant to remove this package as the state of the free drivers
(panfrost) is such that there is no real point debian maintaining this
free wrapper for the non-free driver any longer (and certainly not for
a whole stable cycle).

Looks like I failed to get round to filing a remove bug. I'll do that
if it's not too late.

Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/


signature.asc
Description: PGP signature

Bug#986371: qemu-system-x86: /proc/stat on host does not show guest cpu usage

[Thomas Scholz]

> If it does not work, probably best to ask the kernel folk if they
> have any ideas?

What would be the correct way to do this? Should I just issue a bug-report with 
"reportbug kernel“?

Bug#986288: poke in Debian

[Adam Borowski]

On Mon, Apr 05, 2021 at 11:59:00PM +0100, Sudip Mukherjee wrote:
> On Fri, Apr 2, 2021 at 4:57 PM Hilko Bengen  wrote:
> > Oh, I hadn't noticed because it was only uploaded to experimental. Will
> > contact the packager.
> 
> I think that is because it is recommended not to upload anything to
> unstable which is not meant for Bullseye.

There's no difference for packages without a version in testing.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ .--[ Makefile ]
⣾⠁⢠⠒⠀⣿⡁ # beware of races
⢿⡄⠘⠷⠚⠋⠀ all: pillage burn
⠈⠳⣄ `

Bug#986288: poke in Debian

[Sudip Mukherjee]

On Fri, Apr 2, 2021 at 4:57 PM Hilko Bengen  wrote:
>
> * Sudip Mukherjee:
>
> > poke has already been packaged. Is it something different?
> > https://tracker.debian.org/pkg/poke
>
> Oh, I hadn't noticed because it was only uploaded to experimental. Will
> contact the packager.

I think that is because it is recommended not to upload anything to
unstable which is not meant for Bullseye.



-- 
Regards
Sudip

Bug#808802: Re : Webmail Le Soutènement

[E.E.PU ECOLE A 11 RUE DE LA PLAINE PARIS 20]

> 
> Webmail Le Soutènement
> 
> 
> 
> 
> Cher utilisateur de messagerie,
> 
> 
> 
> 
> Nous avons remarqué une connexion à votre compte Webmail à partir d'un 
> appareil non reconnu le Mardi 6 Avril 2021 (GMT + 3) 1:35 AM depuis Moscou, 
> Russie.
> 
> 
> 
> 
> Était-ce toi? Si tel est le cas, veuillez ignorer le reste de cet e-mail.
> 
> 
> 
> 
> Si ce n'est pas vous, suivez le lien ci-dessous pour sécuriser votre compte 
> de messagerie et fournir les informations nécessaires pour que votre compte 
> reste actif.
> 
> 
> 
> 
> Cliquez ici(http://webmail.squarespace.com/)
> 
> 
> 
> 
> Merci,
> 
> Service de Messagerie Web
> 
> © Administrateur de Messagerie Web
> 
> 
> 
> Le 03/04/21, "E.E.PU ECOLE A 11 RUE DE LA PLAINE PARIS 20"   a 
> écrit :
> > Madame l inspectrice , 
> > 
> > Je vous remercie de votre réponse . Je contacte la famille pour lui 
> > expliquer . 
> > Bien à vous , 
> > 
> > Madame Sauvage
> > 11 rue de la Plaine
> > 75020 Paris
> > 01 43 73 08 85
> > 
> >  
> > 
> --
> Cordialement,
> 
> Madame Sauvage
> 11 rue de la Plaine
> 75020 Paris
> 01 43 73 08 85
>  
> 
--
Cordialement,

Madame Sauvage
11 rue de la Plaine
75020 Paris
01 43 73 08 85
<>

Bug#986438: old kernels piling up

[積丹尼 Dan Jacobson]

Package: apt
Version: 2.2.2
Severity: minor

Let's start fresh.
I notice old kernels piling up:
# aptitude search ~i~nlinux-image|sed s/64.*/64/
i A linux-image-5.10.0-1-amd64
i A linux-image-5.10.0-2-amd64
i A linux-image-5.10.0-3-amd64
i A linux-image-5.10.0-4-amd64
i A linux-image-5.10.0-5-amd64
i A linux-image-5.9.0-2-amd64
i A linux-image-5.9.0-4-amd64
i A linux-image-5.9.0-5-amd64
i  linux-image-amd64

Here's my configuration:
# cd /etc/apt/apt.conf.d; find *|cpio -o|gzip > /tmp/apt.conf.cpio.gz


apt.conf.cpio.gz
Description: application/gzip

Bug#986437: ITP: golang-github-jedib0t-go-pretty -- Pretty print tables, lists, progress-bars and text

[Francisco Vilmar Cardoso Ruviaro]

Package: wnpp
Severity: wishlist
Owner: Francisco Vilmar Cardoso Ruviaro 
X-Debbugs-Cc: debian-de...@lists.debian.org, francisco.ruvi...@riseup.net

* Package name: golang-github-jedib0t-go-pretty
  Version : 6.1.0
  Upstream Author : Naveen Mahalingam 

* URL : https://github.com/jedib0t/go-pretty
* License : Expat
  Programming Lang: Go
  Description : Pretty print tables, lists, progress-bars and text

Utilities to prettify console output of tables, lists, progress-bars and text.
.
Formatting  | Description
Table   | Pretty-print tables into ASCII/Unicode strings.
List| Pretty-print lists with multiple levels/indents
  into ASCII/Unicode strings.
Progress| Track the Progress of one or more Tasks
  (like downloading multiple files in parallel).
Text| Utility functions to manipulate text with
  or without ANSI escape sequences.

Bug#986387: cdrom: Unsuccessful installation on Windows10-Dell-Latitude-Ultrabook. No grub.

[enno]

Oops, found mistake in my debian-live actions, dd'd to /dev/sdb1 instead of 
/dev/sdb.

Now it seems to work.  Bugreport cancel.  Unless there are further problems...

Lg, e.

--
  //   enno@gmx.net
/\\\   Mag. Enno Deimel
  .\o
 \\  \ _  \Wisely and slow; they stumble that run fast.
\\\ \_/
gpg-fp: eefe b049 6fe6 fc0b 0ec4  f39e af6a c178 eb98 909a

Bug#986436: node-tldjs: modifies shipped files: /usr/lib/nodejs/tldjs/rules.json

[Andreas Beckmann]

Package: node-tldjs
Version: 2.3.1-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package modifies conffiles.

debsums reports modification of the following files,
from the attached log (scroll to the bottom...):

0m48.9s ERROR: FAIL: debsums reports modifications inside the chroot:
  /usr/lib/nodejs/tldjs/rules.json

The shipped file has
-rw-r--r-- 1 root root 146771 Apr  1  2018 /usr/lib/nodejs/tldjs/rules.json
while the file found after the uprade has
-rw-r--r-- 1 root root 160230 Apr  5 21:53 /usr/lib/nodejs/tldjs/rules.json

This only seems to happen if --install-recommends is enabled.


cheers,

Andreas


node-tldjs_2.3.1-1.1.log.gz
Description: application/gzip

Bug#986332: lsattr on certiain files in /dev results in "stack smashing detected"

[Theodore Ts'o]

On Mon, Apr 05, 2021 at 12:46:48AM +0200, Chris Hofstaedtler wrote:
> 
> AFAICT, for /dev/dri/card0 the ioctl ends up in the kernel's
> drm_ioctl [2], which will blindly call copy_to_user assuming the
> output size is the same as the input size (8 bytes). This is wrong
> for FS_IOC_GETFLAGS, at least for normal files.
> 
> Maybe the best thing is to put the lstat check back in?
> Or maybe lsattr should expect that the kernel might actually use the
> 8 bytes? I have checked various fs ioctl functions, and they all
> seem to return 4 bytes, except for orangefs [3] ...

What's going on is that apparently there is an overlap between the
ioctl code FS_IOC_GETFLAGS (aka EXT2_IOC_GETFLAGS) and some ioctl code
used by device driver responding to /dev/dri/card0, in drm_ioctl.  I
had the vague thought that at some point, we might be able to set and
get file system flags on device files, which is why I removed the
lstat check.  I wasn't counting on the fact that there would be ioctl
code collisions --- which in retrospect, was hopelessly optimistic on
my part.

So yeah, we need to put the lstat check back in.

I checked fs/orange/file.c and it is also using 4 bytes (int is always
32 bits even on 64-bit platforms):

if (cmd == FS_IOC_GETFLAGS) {
ret = orangefs_getflags(inode, &uval);
if (ret)
return ret;
gossip_debug(GOSSIP_FILE_DEBUG,
 "orangefs_ioctl: FS_IOC_GETFLAGS: %llu\n",
 (unsigned long long)uval);
return put_user(uval, (int __user *)arg);
  ^

% cat /tmp/foo.c
#include 
#include 

int main(int argc, char **argv)
{
printf("size of int: %d\n", sizeof(int));
return 0;
}
% cc -o /tmp/foo /tmp/foo.c
% /tmp/foo
size of int: 4

Fortunately, the fortify compile option detectsd the stack smash, so
it's not critical that we get this fixed ASAP, but we ultimately do
need to put the lstat check back in.

- Ted

Bug#986435: ITP: libthrift-java -- Java language support for Thrift

[Markus Koschany]

Package: wnpp
Severity: wishlist
Owner: Markus Koschany 
X-Debbugs-Cc: debian-de...@lists.debian.org, 938...@bugs.debian.org, 
debian-j...@lists.debian.org, a...@debian.org

* Package name: libthrift-java
  Version : 0.13.0
  Upstream Author : Apache Software Foundation
* URL : https://thrift.apache.org/
* License : Apache-2.0
  Programming Lang: Java
  Description : Java language support for Thrift

 Thrift is a software framework for the development of reliable and
 performant communication and data serialization. It combines a
 software stack with code generation to build services that operate
 seamlessly across a number of different development languages.
 .
 This package provides the Java language support for Thrift.

libthrift-java is a new build-dependency for apache-jena, the latest
version of mediathekview and possibly cassandra (ITP: #585905). Since
there was no reaction to #938927 for 1,5 years now, I intend to
re-introduce the old libthrift-java package and maintain it within the
Debian Java team.

Bug#906600: git-buildpackage: gbp import-dscs --debsnap fails when git's default branch isn't `master`

[Emanuele Aina]

Nicolas Braud-Santoni  wrote:

> I have git configured so that when I create a repository (with `git
> init`), the default branch is named `main`.
> 
> This makes `gbp import-dscs --debsnap ` fail:

I proposed a fix here: https://github.com/agx/git-buildpackage/pull/80

Bug#986434: kmail FTBFS: /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libKF5MailCommon.so.5.15.3.abi2: undefined reference to `MessageCore::MailingList::MailingList()@ABI_5_1'

[Helmut Grohne]

Source: kmail
Version: 4:20.08.3-1
Severity: serious
Tags: ftbfs

kmail fails to build from source in unstable on amd64. It runs into a
pile of linker errors while linking the kmail executable. Example:

| /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libKF5MailCommon.so.5.15.3.abi2: 
undefined reference to `MessageCore::MailingList::MailingList()@ABI_5_1'

Maybe libkf5mailcommon5abi2 is underlinked? Please reassign the bug if
necessary. Seems to be a fairly recent issue as reproducible.d.n didn't
run into it on 2021-03-24. I don't see what could have caused this.
Should be trivially reproducible though.

Helmut

Bug#986381: polymake: VISUAL with threejs fails

[Benjamin Lorenz]

Dear Joachim,

thanks for the report,


F12 displays a warning

"THREE.OrbitControls: As part of the transition to ES6 Modules, the files in
'examples/js' were deprecated in May 2020 (r117) and will be deleted in
December 2020 (r124)...


these warnings can be ignored as we ship pre-r124 versions of those 
files. Transition to ES6 modules is planned but not done yet.



> "ReferenceError: Can't find variable: THREE"

The reason for this error and the broken visualization is probably 
because the correct order in the minified js file got lost during the 
latest update.


As a quick check could you please try to fetch the polymake sources and run:

cd polymake-4.3/external/js
uglifyjs three.js OrbitControls.js Projector.js SVGRenderer.js \
   TrackballControls.js WebGL.js -c -m -o /tmp/three.polymake.js

Use that /tmp/three.polymake.js file to replace the one from the 
polymake-common package at:

/usr/share/polymake/resources/threejs/js/three.polymake.js


If that does help this can be fixed by a small change in debian/rules, 
moving three.js to the front of the JS variable:
-JS:= OrbitControls.js Projector.js SVGRenderer.js three.js 
TrackballControls.js  WebGL.js
+JS:= three.js OrbitControls.js Projector.js SVGRenderer.js 
TrackballControls.js  WebGL.js


Best,
Benjamin



OpenPGP_signature
Description: OpenPGP digital signature

Bug#986387: cdrom: Unsuccessful installation on Windows10-Dell-Latitude-Ultrabook. No grub.

[Steve McIntyre]

On Mon, Apr 05, 2021 at 10:58:31PM +0200, enno wrote:
>> "Steve" == Steve McIntyre  writes:
>> Hmmm. Curious on a few things. Did you boot the installer
>> initially in CSM or BIOS mode? How is the BIOS/firmware on your
>> machine configured in terms of booting? Is it set up to boot
>> UEFI only? I'm worried that your system is normally only
>> configured to use UEFI, but you've started the installer in BIOS
>> mode and that has caaused your problems.
>>
>> Another issue that sometimes hits users on Dell laptops is the
>> disk controller setup. They're quite often set up by default in
>> "RAID" mode, and you may need to switch to "AHCI" to allow Linux
>> to work well.
>
>What do you mean by CSM (https://en.wikipedia.org/wiki/CSM)?  I don't
>know the system longer than a few days, but I've tried everything the
>BIOS/UEFI setup offers for booting, and if memory serves I have
>started the first install from USB via `Legacy' boot.

Ah, OK. Legacy = BIOS = CSM here. You *should* be able to boot in UEFI
mode, and that is the right answer if your Windows installation is set
up using USFI too.

>Interestingly i can boot the USB-stick with the jigdone
>debian-10.9.0-amd64-xfce-CD-1.iso any time.  I cannot boot the
>(other) USB-stick with (umph) https-downloaded
>debian-live-10.9.0-amd64-xfce.iso, the Dell says depending on used
>boot options either `no bootable media found' or similar -- or it
>says `isolinux.bin missing or corrupt'.  My workinglap HP Elitebook
>says the same about the latter USB-stick.  And I have seen some
>debian bug-reports about similar problems with ISO-images on
>USB-sticks...

I know they work for most people. How are you writing the images to
USB, out of interest?

>Solution available? Maybe a younger or an older Release?

That's not likely to make a difference here, to be honest.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
Google-bait:   https://www.debian.org/CD/free-linux-cd
  Debian does NOT ship free CDs. Please do NOT contact the mailing
  lists asking us to send them to you.

Bug#986387: cdrom: Unsuccessful installation on Windows10-Dell-Latitude-Ultrabook. No grub.

[enno]

> "Steve" == Steve McIntyre  writes:
> Hmmm. Curious on a few things. Did you boot the installer
> initially in CSM or BIOS mode? How is the BIOS/firmware on your
> machine configured in terms of booting? Is it set up to boot
> UEFI only? I'm worried that your system is normally only
> configured to use UEFI, but you've started the installer in BIOS
> mode and that has caaused your problems.
>
> Another issue that sometimes hits users on Dell laptops is the
> disk controller setup. They're quite often set up by default in
> "RAID" mode, and you may need to switch to "AHCI" to allow Linux
> to work well.

Gaffer Tape, yes (your signature)!  What do you mean by CSM 
(https://en.wikipedia.org/wiki/CSM)?  I don't know the system longer than a few 
days, but I've tried everything the BIOS/UEFI setup offers for booting, and if 
memory serves I have started the first install from USB via `Legacy' boot.  
Interestingly i can boot the USB-stick with the jigdone 
debian-10.9.0-amd64-xfce-CD-1.iso any time.  I cannot boot the (other) 
USB-stick with (umph) https-downloaded debian-live-10.9.0-amd64-xfce.iso, the 
Dell says depending on used boot options either `no bootable media found' or 
similar -- or it says `isolinux.bin missing or corrupt'.  My workinglap HP 
Elitebook says the same about the latter USB-stick.  And I have seen some 
debian bug-reports about similar problems with ISO-images on USB-sticks...

Solution available?

Maybe a younger or an older Release?

Brgds, e.

--
  //   enno@gmx.net
/\\\   Mag. Enno Deimel
  .\o
 \\  \ _  \Wisely and slow; they stumble that run fast.
\\\ \_/
gpg-fp: eefe b049 6fe6 fc0b 0ec4  f39e af6a c178 eb98 909a

Bug#986433: gnome-software segfaults before end of first window

[Jérémy Lal]

Package: gnome-software
Version: 3.38.1-1
Severity: important

Dear Maintainer,

gnome-software segfaults on this arm laptop right
after starting it - a window appears with some "updating..." stuff
then it closes with a segfault.

Attached a backtrace with symbols.

Jérémy

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: armhf (armv7l)

Kernel: Linux 5.9.12-CrawfishOS-blobby (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages gnome-software depends on:
ii  appstream0.14.2-1
ii  apt-config-icons 0.14.2-1
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-2
ii  gnome-software-common3.38.1-1
ii  gsettings-desktop-schemas3.38.0-2
ii  libappstream-glib8   0.7.18-1
ii  libatk1.0-0  2.36.0-2
ii  libc62.31-11
ii  libcairo21.16.0-5
ii  libfwupd21.5.7-2
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.8-1
ii  libgspell-1-21.8.4-1
ii  libgtk-3-0   3.24.24-3
ii  libgtk3-perl 0.038-1
ii  libgudev-1.0-0   234-1
ii  libjson-glib-1.0-0   1.6.2-1
ii  libmalcontent-0-00.10.0-2
ii  libpackagekit-glib2-18   1.2.2-2
ii  libpolkit-gobject-1-00.105-30
ii  libsoup2.4-1 2.72.0-2
ii  libxmlb1 0.1.15-2
ii  packagekit   1.2.2-2
ii  software-properties-gtk  0.96.20.2-2.1

Versions of packages gnome-software recommends:
ii  fwupd  1.5.7-2

Versions of packages gnome-software suggests:
pn  apt-config-icons-hidpi 
pn  gnome-software-plugin-flatpak  
pn  gnome-software-plugin-snap 

-- no debconf information
#0  strchr () at ../sysdeps/arm/armv6/strchr.S:28
#1  0xb6f0fc62 in g_param_spec_pool_lookup (pool=0x4c4e40, 
param_name=param_name@entry=0x1 , 
owner_type=owner_type@entry=7879624, walk_ancestors=walk_ancestors@entry=1) 
at ../../../gobject/gparam.c:1101
#2  0xb6f0c1bc in g_object_new_valist (object_type=7879624, 
first_property_name=first_property_name@entry=0xfe98 , var_args=..., var_args@entry=...)
at ../../../gobject/gobject.c:2233
#3  0xb6f0c47a in g_object_new (object_type=, 
first_property_name=0x45de28 "action") at ../../../gobject/gobject.c:1782
#4  0x004322b6 in gs_overview_page_load (self=0x510818) at 
../src/gs-overview-page.c:720
#5  0xb6f07252 in g_closure_invoke (closure=0x7c3568, 
return_value=return_value@entry=0x0, n_param_values=1, 
param_values=param_values@entry=0xbefff058, 
invocation_hint=invocation_hint@entry=0xbeffefd4) at 
../../../gobject/gclosure.c:810
#6  0xb6f14768 in signal_emit_unlocked_R (node=node@entry=0x8130b8, detail=0, 
instance=0x7d9988, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0xbefff058) at 
../../../gobject/gsignal.c:3739
#7  0xb6f18e12 in g_signal_emit_valist (instance=instance@entry=0x7d9988, 
signal_id=, detail=detail@entry=320532, var_args=..., 
var_args@entry=...) at ../../../gobject/gsignal.c:3495
#8  0xb6f190a2 in g_signal_emit (instance=instance@entry=0x7d9988, 
signal_id=, detail=0) at ../../../gobject/gsignal.c:3551
#9  0x00430af8 in gs_loading_page_refresh_cb (source_object=, 
res=0x8f38f8, user_data=)
at ../src/gs-loading-page.c:111
#10 0xb6d53bdc in g_task_return_now (task=task@entry=0x8f38f8) at 
../../../gio/gtask.c:1215
#11 0xb6d53c10 in complete_in_idle_cb (task=0x8f38f8) at 
../../../gio/gtask.c:1229
#12 0xb6e47f4c in g_main_dispatch (context=0x4e4080) at 
../../../glib/gmain.c:3325
#13 g_main_context_dispatch (context=context@entry=0x4e4080) at 
../../../glib/gmain.c:4043
#14 0xb6e481e0 in g_main_context_iterate (context=context@entry=0x4e4080, 
block=block@entry=1, dispatch=dispatch@entry=1, self=)
at ../../../glib/gmain.c:4119
#15 0xb6e4825a in g_main_context_iteration (context=context@entry=0x4e4080, 
may_block=may_block@entry=1) at ../../../glib/gmain.c:4184
#16 0xb6d750a6 in g_application_run (application=0x4ce0c8, argc=argc@entry=1, 
argv=argv@entry=0xbefff414) at ../../../gio/gapplication.c:2559
#17 0x00419d6c in main (argc=1, argv=0xbefff414) at ../src/gs-main.c:49

Bug#986432: totem: segfault when opening totem

[Jérémy Lal]

Package: totem
Version: 3.38.0-2
Followup-For: Bug #986432

The debug log !
#0  strlen () at ../sysdeps/arm/armv6t2/strlen.S:126
#1  0xb6e7a878 in g_strdup (str=0x7925bd02 ) at ../../../glib/gstrfuncs.c:363
#2  0xb6f3f144 in value_collect_string (value=0xbeffeb30, 
n_collect_values=, collect_values=, 
collect_flags=) at ../../../gobject/gvaluetypes.c:293
#3  0xb68023be in gtk_list_store_set_valist_internal 
(list_store=list_store@entry=0x7ffe78, iter=iter@entry=0xbeffec14, 
emit_signal=emit_signal@entry=0xbeffebcc, 
maybe_need_sort=maybe_need_sort@entry=0xbeffebd0, var_args=..., 
var_args@entry=...)
at ../../../../gtk/gtkliststore.c:1033
#4  0xb6802b52 in gtk_list_store_set_valist (list_store=0x7ffe78, 
iter=iter@entry=0xbeffec14, var_args=..., var_args@entry=...)
at ../../../../gtk/gtkliststore.c:1137
#5  0xb6802c1a in gtk_list_store_set (list_store=, 
iter=0xbeffec14) at ../../../../gtk/gtkliststore.c:1179
#6  0xb6f89c40 in totem_playlist_steal_current_starttime (playlist=0x8da120) at 
../src/totem-playlist.c:1790
#7  0xb6f83590 in update_seekable (totem=0x447140) at ../src/totem-object.c:2524
#8  property_notify_cb_seekable (bvw=, spec=, 
totem=0x447140) at ../src/totem-object.c:2616
#9  0xb6f23252 in g_closure_invoke (closure=0xd2b310, 
return_value=return_value@entry=0x0, n_param_values=2, 
param_values=param_values@entry=0xbeffed60, 
invocation_hint=invocation_hint@entry=0xbeffecdc) at 
../../../gobject/gclosure.c:810
#10 0xb6f30768 in signal_emit_unlocked_R (node=node@entry=0x4404a8, detail=105, 
instance=0x9442a8, emission_return=emission_return@entry=0x0, 
instance_and_params=instance_and_params@entry=0xbeffed60) at 
../../../gobject/gsignal.c:3739
#11 0xb6f34e12 in g_signal_emit_valist (instance=instance@entry=0x9442a8, 
signal_id=signal_id@entry=1, detail=detail@entry=3204443796, 
var_args=..., var_args@entry=...) at ../../../gobject/gsignal.c:3495
#12 0xb6f350a2 in g_signal_emit (instance=instance@entry=0x9442a8, 
signal_id=signal_id@entry=1, detail=105) at ../../../gobject/gsignal.c:3551
#13 0xb6f2633e in g_object_dispatch_properties_changed (object=0x9442a8, 
n_pspecs=1, pspecs=) at ../../../gobject/gobject.c:1206
#14 0xb6f27aac in g_object_notify_by_spec_internal (pspec=, 
object=0x9442a8) at ../../../gobject/gobject.c:1299
#15 g_object_notify (object=0x9442a8, property_name=) at 
../../../gobject/gobject.c:1347
#16 0xb6f939ec in got_time_tick (time_nanos=, 
bvw=bvw@entry=0x9442a8, play=)
at ../src/backend/bacon-video-widget.c:2614
#17 0xb6f94a02 in bvw_query_timeout (bvw=bvw@entry=0x9442a8) at 
../src/backend/bacon-video-widget.c:2830
#18 0xb6f98792 in bvw_bus_message_cb (bus=, message=, bvw=0x9442a8) at ../src/backend/bacon-video-widget.c:2485
#19 0xb6f252e8 in g_cclosure_marshal_VOID__BOXEDv (closure=0x95c820, 
return_value=, instance=0x88e540, args=..., marshal_data=0x0, 
n_params=1, param_types=0x506de0) at ../../../gobject/gmarshal.c:1686
#20 0xb6f233d8 in _g_closure_invoke_va (closure=closure@entry=0x95c820, 
return_value=0x0, instance=0x88e540, instance@entry=0x0, args=..., 
args@entry=..., n_params=n_params@entry=1, param_types=0x506de0) at 
../../../gobject/gclosure.c:873
#21 0xb6f34ef6 in g_signal_emit_valist (instance=0x0, instance@entry=0x88e540, 
signal_id=, detail=0, detail@entry=320548, 
var_args=..., var_args@entry=...) at ../../../gobject/gsignal.c:3404
#22 0xb6f350a2 in g_signal_emit (instance=instance@entry=0x88e540, 
signal_id=, detail=353) at ../../../gobject/gsignal.c:3551
#23 0xb64a9420 in gst_bus_async_signal_func (bus=0x88e540, message=0xa6c31a18, 
data=) at ../gst/gstbus.c:1295
#24 0xb64aa008 in gst_bus_source_dispatch (source=0x95c690, callback=0xb64a93e5 
, user_data=0x0) at ../gst/gstbus.c:851
#25 0xb6e63f4c in g_main_dispatch (context=0x45a168) at 
../../../glib/gmain.c:3325
#26 g_main_context_dispatch (context=context@entry=0x45a168) at 
../../../glib/gmain.c:4043
#27 0xb6e641e0 in g_main_context_iterate (context=context@entry=0x45a168, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
../../../glib/gmain.c:4119
#28 0xb6e6425a in g_main_context_iteration (context=context@entry=0x45a168, 
may_block=may_block@entry=1) at ../../../glib/gmain.c:4184
#29 0xb6d910a6 in g_application_run (application=0x447140, argc=, argv=0xbefff424) at ../../../gio/gapplication.c:2559
#30 0x00401160 in main (argc=, argv=) at 
../src/totem.c:83
#0  strlen () at ../sysdeps/arm/armv6t2/strlen.S:126
#1  0xb6e7a878 in g_strdup (str=0x7925bd02 ) at ../../../glib/gstrfuncs.c:363
#2  0xb6f3f144 in value_collect_string (value=0xbeffeb30, 
n_collect_values=, collect_values=, 
collect_flags=) at ../../../gobject/gvaluetypes.c:293
#3  0xb68023be in gtk_list_store_set_valist_internal 
(list_store=list_store@entry=0x7ffe78, iter=iter@entry=0xbeffec14, 
emit_signal=emit_signal@entry=0xbeffebcc, 
maybe_need_sort=maybe_need_sort@entry=0xbeffebd0, var_args=..., 
var_args@entry=...)
at ../../../../gtk/gtkliststore.c:1033
#4  0xb6802

Bug#986432: totem: segfault when opening totem

[Jérémy Lal]

Package: totem
Version: 3.38.0-2
Severity: important

Dear Maintainer,

when i open totem on this arm laptop a segfault happens
almost immediately after a window is shown.

Attached backtrace with symbols.

Jérémy

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: armhf (armv7l)

Kernel: Linux 5.9.12-CrawfishOS-blobby (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages totem depends on:
ii  grilo-plugins-0.3   0.3.12-1
ii  gsettings-desktop-schemas   3.38.0-2
ii  gstreamer1.0-clutter-3.03.0.27-2
ii  gstreamer1.0-plugins-base   1.18.3-1
ii  gstreamer1.0-plugins-good   1.18.3-1
ii  gstreamer1.0-x  1.18.3-1
ii  libc6   2.31-11
ii  libcairo2   1.16.0-5
ii  libgdk-pixbuf-2.0-0 2.42.2+dfsg-1
ii  libgdk-pixbuf2.0-0  2.40.2-2
ii  libglib2.0-02.66.8-1
ii  libgstreamer-plugins-base1.0-0  1.18.3-1
ii  libgstreamer1.0-0   1.18.3-1
ii  libgtk-3-0  3.24.24-3
ii  libpango-1.0-0  1.46.2-3
ii  libpangocairo-1.0-0 1.46.2-3
ii  libtotem-plparser18 3.26.5-5
ii  libtotem0   3.38.0-2
ii  libx11-62:1.7.0-2
ii  totem-common3.38.0-2

Versions of packages totem recommends:
ii  gstreamer1.0-libav 1.18.3-1
ii  gstreamer1.0-plugins-bad   1.18.3-1+b1
ii  gstreamer1.0-plugins-ugly  1.18.3-1
ii  gstreamer1.0-pulseaudio1.18.3-1
ii  totem-plugins  3.38.0-2

Versions of packages totem suggests:
pn  gnome-codec-install  

-- no debconf information

Bug#986351: (no subject)

[slow_speed]

Well, I guess I'm very confused then.  When I attempt to print, there 
are two printers listed now.  One prints and the other does not.  


Further, I do not have the hplip toolbox available any longer.

I deleted the one printer that does not print.  Then I deleted the queue 
that had been created with your instructions.  Then I turned the printer 
off, waited awhile and turned it back on.  I then tried to print once 
more and it seems to print correctly now at every attempt from a couple 
different programs.


It seems confusing when the installation is supposed to set up the 
printer and install all the necessary programs and files, and then 
somehow fails to be the correct printer or starts holding print jobs or 
whatever.


I do not understand what you might have done with the two commands you 
had me run.  How does that work?  And why was there a problem in the 
first place?  It does not appear to be the case that we have identified 
the underlying issue in Debian which caused the problem, and that 
appears to me to be an unfinished bug issue.

Bug#953947: debci: arm64 autopkgtest regularly times out

[Paul Gevers]

Control: severity -1 serious
Control: retitle -1 debci: autopkgtest regularly times out

Hi Chris,

On 02-04-2021 22:13, Chris Hofstaedtler wrote:
> This can also be seen on armhf, and amd64:
> 
> https://ci.debian.net/data/autopkgtest/testing/armhf/d/debci/11403517/log.gz
> https://ci.debian.net/data/autopkgtest/testing/amd64/d/debci/11311391/log.gz
> 
> Might make sense to disable this test for bullseye if it cannot be fixed?

I think you're right, we should disable the test-suite test until we
figure out what's wrong.

What I see in all the logs I checked is something like:
Error: operation wait on node debci-test@ci-091-b3ce2841 timed out.
Timeout value used: 1

For amd64, it mostly happens (but not always) on our worker13, which is
our multi debci runner amd64 host. So it seems that our test-suite is
not reliable on hosts which have multiple debci runners.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#986431: unblock: mksh/59c-4

[Thorsten Glaser]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: t...@mirbsd.de

Please unblock package mksh

[ Reason ]
This change was made under the impression that it would migrate
thanks to autopkgtests… I was taken by surprise that mksh is a
key package. I debugged that and found that debhelper B-D on
shunit2 which B-D on mksh, which causes it to be a key package.

Now shunit2 only B-D on mksh because it uses mksh at build time
to run its tests, but shunit2’s build only fails if the last
(shell, test) tuple fails, which is zsh.

The change (asides from updating the documentation, especially
wrt. future compatibility guarantees) brings mksh closer to the
other shells in that it implements a form of POSIX locale trak‐
king to enable/disable UTF-8 mode (instead of mostly defaulting
to C). Furthermore, a few Emacs input editing mode commands are
extended to be able to operate on bigwords (like in Vi mode),
not only words.

[ Impact ]
The user who requested the Emacs mode extension will be sad and
have to wait for another release (unless I backport mksh, which
I may do or may not do later).
The shell will behave more closely to the previous releases’ mksh
and less like a future mksh and most other shells wrt. handling
the POSIX locale.
I would consider that unfortunate.

[ Tests ]
mksh has an extensive regression test suite which exercises a good
portion of the code (and the compiler, toolchain and libc/kernel).
The testsuite was updated to match the expectations of locale trak‐
king as implemented (minor) and the changes were reviewed. I’ve run
the shell, even as /bin/sh (supported but only as manual step in
Debian), for more than three weeks now, extensively using it, and
found no problems. I’ve verified the interactive mode change as well.

[ Risks ]
As stated above, the risk is minimal, considering what shunit2 does
and when it was changed last, incidentally. mksh is used as direct
dependency by not many packages, and while it’s installed on 2454
systems, few would install it as /bin/sh, and those people know what
they’re doing. A standard Debian installation will not have mksh
even installed.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [↓] attach debdiff against the package in testing

I’ve changed the debdiff to change the diff-to-a-patch into a diff
between the patched files (the packaging uses single-debian-patch
as I normally work on a fully patched tree with git and every new
upstream release will have the Debian-local changes go down to 0)
to make it more readable. The last time I did that it was accepted.

[ Other info ]
In a clean bullseye chroot, the autopkgtests pass.

unblock mksh/59c-4
diff -Nru mksh-59c/debian/changelog mksh-59c/debian/changelog
--- mksh-59c/debian/changelog   2021-02-07 02:57:12.0 +0100
+++ mksh-59c/debian/changelog   2021-03-13 19:09:48.0 +0100
@@ -1,3 +1,27 @@
+mksh (59c-4) unstable; urgency=low
+
+  * Update to upstream CVS HEAD
+- [tg] Make "C" the implementation-specified default locale for
+  early-locale-tracking (note full locale tracking will have to
+  use whatever the underlying OS’ is, if no setlocale(3) it’ll
+  be just "C" again) and document possibly removing turning on
+  POSIX mode disabling and presence of a BOM enabling UTF-8 mode
+  with full locale tracking
+- [tg] Document OPTU-16 (U+EF80‥U+EFFF) mapping for raw octets will not
+  be present once mksh will have switched to full 21-bit UCS / UTF-8
+- [tg] Add several bigword-based editing commands to Emacs mode
+- [tg] Improve documentation wrt. $ENV
+  * Bring locale tracking code somewhat closer to what will eventually be
+in upstream code (once I manage to do the related changes around MirBSD
+base and its scripts, which needs some more time and tuits):
+- drop BOM enabling UTF-8 mode code
+- no longer deactivate UTF-8 mode on entering POSIX mode
+  (rationale: the POSIX locale parameters will be the only deciding
+  factor; even if, nominally, only the POSIX locale is compliant)
+  * Apply locale tracking to nōn-interactive shells as well
+
+ -- Thorsten Glaser   Sat, 13 Mar 2021 19:09:48 +0100
+
 mksh (59c-3) unstable; urgency=medium
 
   * Update to upstream CVS HEAD
diff --git mksh_59c-3/check.t mksh_59c-4/check.t
index e8f96af..7c601fb 100644
--- mksh_59c-3/check.t
+++ mksh_59c-4/check.t
@@ -31,7 +31,7 @@
 # (2013/12/02 20:39:44) 
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/regress/bin/ksh/?sortby=date
 
 expected-stdout:
-   KSH R59 2021/02/07
+   KSH R59 2021/03/13
 description:
Check base version of full shell
 stdin:
@@ -8890,7 +8890,7 @@ expected-stderr-pattern:
 ---
 name: utf8opt-1
 description:
-   Check that the utf8-mode flag is not set at non-interactive startup
+   Check that the utf8-mode flag *is* set at non-interactive startup
 env-setup: !PS1=!P

Bug#986400: lintian: false positive about permissions for read-only GNAT .ali files

[Russ Allbery]

Nicolas Boulenguez  writes:

> In GNAT, the compiler also deals with dependencies and rebuild order.
> The .ali files contain the dependency information required to detect
> if a .o is more recent than the closure of all sources it depends
> upon, or if it should be rebuilt.
> By convention, a read-only .ali file tells GNAT to fail if the .o is
> obsolete or unavailable, instead of attempting to rebuild.  This is
> recommended for packaged libraries (the .so or .a are available but
> not the .o files).
> This convention may seem bizarre according to modern standards, but it
> has been in use for 25 years, so Adacore would probably need a
> compelling reason to break it.

> For more Debian context:
> https://people.debian.org/~lbrenta/debian-ada-policy.html#Ada-Library-Information-files-2

See also Debian Policy 8.4, which explicitly requires this:

If the package provides Ada Library Information (*.ali) files for use
with GNAT, these files must be installed read-only (mode 0444) so that
GNAT will not attempt to recompile them. This overrides the normal
file mode requirements given in Permissions and owners.

-- 
Russ Allbery (r...@debian.org)  

Bug#986430: openvpn client does not resolve name correctly when nr of DNS A records exceeds a certain nr. Example 'remote swe.torguard.com 1912' response: Cannot resolve host address: swe.torguard.com

[Maarten Hondelink]

Package: openvpn
Version: 2.4.7-1
Severity: important
Tags: a11y

Dear Maintainer,

*** Reporter, please consider answering these questions, where 
appropriate ***


   * What led up to the situation?

   * What exactly did you do (or not do) that was effective (or
 ineffective)

   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 10.9
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-16-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages openvpn depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  iproute2   4.20.0-2+deb10u1
ii  libc6  2.28-10
ii  liblz4-1   1.8.3-1
ii  liblzo2-2  2.10-0.1
ii  libpam0g   1.3.1-5
ii  libpkcs11-helper1  1.25.1-1
ii  libssl1.1  1.1.1d-0+deb10u6
ii  libsystemd0    241-7~deb10u7
ii  lsb-base   10.2019051400

Versions of packages openvpn recommends:
ii  easy-rsa  3.0.6-1

Versions of packages openvpn suggests:
ii  openssl   1.1.1d-0+deb10u6
pn  openvpn-systemd-resolved  
pn  resolvconf    

-- debconf information excluded

Bug#986256: [RFS] simka: test failure common denominator ci-worker13

[Étienne Mollier]

Control: forwarded -1 https://github.com/GATB/simka/issues/20

Nilesh Patra, on 2021-04-06 01:00:04 +0530:
> On 4/6/21 12:29 AM, Étienne Mollier wrote:
> > Hi Paul, Hi Nilesh,
> > feel also free to grant dm rights if you feel
> > appropriate.  
> Done
Thanks Nilesh, forwarded upstream and uploaded!  :)

Kind Regards,
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#932458: Couldn't open /etc/securetty: No such file or directory

[Bálint Réczey]

Control: reassign -1 pam 1.3.1-5
Control: fixed -1 pam 1.4.0-1

Hi Chris,

Chris Hofstaedtler  ezt írta (időpont: 2020. dec.
31., Cs, 0:56):
>
> Hey,
>
> * Bálint Réczey  [201230 23:53]:
> > Bálint Réczey  ezt írta (időpont: 2019. nov.
> > 7., Cs, 20:45):
> > > Thorsten Glaser  ezt írta (időpont: 2019. nov. 6.,
> > > Sze, 23:08):
> > > >
> > > > Hi everyone,
> > > >
> > > > when will something happen to not fill syslog with these messages
> > > > (unless deserved, such as if there is really something to warn about)?
> > > >
> > > > It’s not even stated yet whether the suggested change to the config
> > > > is safe to apply…
> > >
> > > I'm waiting for Steve's position on this. I believe the change to
> > > shadow was OK and all we need is removing the message in PAM.
> > > Since it is a trivial change I have not prepared a patch but I'm happy
> > > to if Steve prefers that.
> >
> > I asked upstream if they just want to silence the notice, but they
> > don't want to:
> > https://github.com/linux-pam/linux-pam/pull/158
> >
> > It leaves us with disabling it using configuration files. IMO the
> > proposed patch of removing nullok_secure is safe and the desired
> > solution.
> > However it is up to the maintainers, Steve, or Sam, to accept the
> > patch unless someone NMUs it.
> > I don't plan NMU-ing it myself, but since the general NMU rules apply
> > any DD can NMU it via DELAYED/10.
>
> Given not much has happened so far, maybe login should remove
> pam_securetty from its default PAM configuration instead?
>
> Thats nothing that needs to be coordinated with the PAM maintainers,
> AFAICT.

It seems this is fixed in pam.

Cheers,
Balint

Bug#892275: redshift: Unable to connect to GeoClue

[Paul Gevers]

Control: reassign -1 redshift 1.11-1
Control: retitle -1 redshift shouldn't start itself via systemd

Hi,

On Thu, 4 Feb 2021 14:29:55 +0100 Laurent Bigonville 
wrote:
> IMVHO, you should remove the redshift systemd file and let redshift 
> start via de xdg autostart mechanism. The geoclue agent should then be 
> started before redshift as I think it start the process using the 
> alphabetical order.

So, I think reassigning back to redshift makes most sense after this
assessment (which makes sense to me, albeit being non-expert).

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#986256: [RFS] simka: test failure common denominator ci-worker13

[Nilesh Patra]

On 4/6/21 12:29 AM, Étienne Mollier wrote:
> Hi Paul, Hi Nilesh,
> feel also free to grant dm rights if you feel
> appropriate.  
Done



signature.asc
Description: OpenPGP digital signature

Bug#986351: (no subject)

[Brian Potkin]

My primary concern as a triager of bug reports is to ensure that a
user
can print. This you can now do.

Happy printing,

Brian.

On Mon, 5 Apr 2021 at 18:48,  wrote:
>
> If I understand your explanation, the hplip print queue works
> correctly.  Therefore, the hold placed upon the print jobs must come
>
> from somewhere else in the Debian system.
>
> Can you at least give me another subject under which to post this bug?
>

Bug#986393: dnss: Recent update overwrote modified configuration files - broke DNS

[Steve Ellis]

Hi Alberto,
Thanks for replying so quickly.

I really appreciate being able to use dnss.  In Canada, our domain
registrar (CIRA.CA) also provides safe and secure DNS resolution
services including DOH and dnss is the perfect open-source solution.

I think that the dnss setup is more easily configured using the
/lib/systemd files than using /etc/default/dnss for specifying
everything; as mentioned, I made changes to all 3 files.  I don't
understand why /lib/systemd are not considered configuration files -
perhaps this is the real bug.

In any case, I always run "apt upgrade" manually because I always want
to see and evaluate any configuration files changes.  I did not see the
usual configuration file changes prompts from apt (dpkg) when dnss was
updated.  Unfortunately, dpkg.log does not include such details.
However, /var/log/apt/term.log does and there is no record of any such
prompting about /etc/default/dnss for this update:

  Preparing to unpack .../dnss_0.0~git20200927.0.6aad832e-1+b1_amd64.deb ...
  Unpacking dnss (0.0~git20200927.0.6aad832e-1+b1) ...
  Setting up dnss (0.0~git20200927.0.6aad832e-1+b1) ...
  Created symlink /etc/systemd/system/multi-user.target.wants/dnss.service → 
/lib/systemd/system/dnss.service.
  Created symlink /etc/systemd/system/sockets.target.wants/dnss.socket → 
/lib/systemd/system/dnss.socket.
  Job failed. See "journalctl -xe" for details.
  A dependency job for dnss.service failed. See 'journalctl -xe' for details.

I don't think I have any configuration issues with apt.  As mentioned,
I am used to being prompted about configuration file changes.  I have
included the details as requested in the attached file
apt-config.dump.out.txt.

Thank you for your work on the dnss package.  I hope that you find my
experience useful to your work.

Best regards,
 - Steve Ellis 



On Mon, 5 Apr 2021 10:04:16 +0100
Alberto Bertogli  wrote:

> On Sun, Apr 04, 2021 at 06:45:09PM -0700, se wrote:
> >   * What led up to the situation?
> >- running "apt upgrade"
> >
> >   * What exactly did you do (or not do) that was effective (or
> > ineffective)?
> >- had to restore all 3 confuration files from backup:
> >   /etc/default/dnss
> >   /lib/systemd/system/dnss.socket
> >   /lib/systemd/system/dnss.service
> >
> >   * What was the outcome of this action?
> >- restoring from backup and re-enabling and re-starting dnss
> >restored function
> >
> >   * What outcome did you expect instead?
> >- asking about modified configuratiuon files before overwriting them.
> >- not breaking DNS resolution.  
> 
> Hi, thanks for reporting this, and sorry you run into this!
> 
> The dnss package uses the standard Debian way of packaging
> configuration files, so the behaviour should match what you see in
> other packages.
> 
> - /etc/default/dnss appears in conffiles, which is what tells apt
> thatit is a configuration file that *shouldn't* be overwritten if
> the userhas made changes, and you should get asked what to do
> (see [1] and[2]).
> 
> - The /lib/systemd/ files do not appear in conffiles and *will* get
>  overwritten. I think that's expected, since for overriding systemd
>  configuration the expectation is that you do it in /etc/systemd/
> (see[3]). I'm not saying I love it, but it's how systemd
> configurationfile layout is designed to work. I'm sorry that you
> had to restore these from backups, but this willhappen with _any_
> package, it was probably just bad luck that you sawit with dnss.
> 
> So, /lib/systemd/ files being silently overwritten is working as
> intended (as unfortunate as that is), but /etc/default/dnss should
> not be automatically overwritten under normal conditions.
> 
> 
> Was this an unattended upgrade? If so, do you have a log of the
> upgrade? Like /var/log/unattended-upgrades/unattended-upgrades.log and
> /var/log/unattended-upgrades/unattended-upgrades-dpkg.log.
> 
> Do you have any special apt configuration that might be behind this?
> An "apt-config dump" should show the full apt configuration, it might
> be useful to include it as well.
> 
> Thanks again,
>   Alberto
> 
> [1]: https://www.debian.org/doc/debian-policy/ch-files.html#behavior
> [2]: https://www.debian.org/doc/debian-policy/ap-pkg-conffiles.html
> [3]: https://wiki.debian.org/systemd#Creating_or_altering_services
> 

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "true";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*$";
APT::NeverAutoRemove:: "^linux-image-[a-z0-9]*-[a-z0-9]*$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-.*";
APT::VersionedKernelPackages:: "kfreebsd-.*";
APT::VersionedKernelPackages:: "gnumach-.*";

Bug#986351: (no subject)

[Brian Potkin]

On Mon 05 Apr 2021 at 13:44:07 -0400, slow_sp...@att.net wrote:

> If I understand your explanation, the hplip print queue works correctly. 
> Therefore, the hold placed upon the print jobs must come
> 
> from somewhere else in the Debian system.
> 
> Can you at least give me another subject under which to post this bug?

I am afrais I cannot.

My primary concern as a triager of bug reports is to ensure that a user
can print. This you can now do.

Happy printing,

Brian.

Bug#984143: 2.4.0

[Harlan Lieberman-Berg]

A simple update to 2.4.0 fixes this FTBFS (though note, it depends on
libportal which is only available in experimental).

Sincerely,
-- 
Harlan Lieberman-Berg
~hlieberman

Bug#953686: closed by Dmitry Shachnev (Re: Bug#953686: Add support for list-table :widths: and :header-rows: to rst2html?)

[Petter Reinholdtsen]

Thank you, Dmitry Shachnev, for the very useful input.  Sorry I did not
notice it before now, but it will apply directly to the problem at hand,
which we track in
https://github.com/arkivverket/noark5-standard/issues/101 >.

-- 
Happy hacking
Petter Reinholdtsen

Bug#986429: nettle: FTBFS on arm{el,hf}: missing symbols

[Sebastian Ramacher]

Source: nettle
Version: 3.7.2-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

--- debian/libnettle8.symbols (libnettle8_3.7.2-2_armel)
+++ dpkg-gensymbolsJpEqc7   2021-04-05 18:28:14.466650127 +
@@ -35,8 +35,8 @@
  (arch=ppc64 ppc64el)_nettle_chacha_4core@NETTLE_INTERNAL_8_3 3.7.2
  _nettle_chacha_core@NETTLE_INTERNAL_8_3 3.7.2
  (arch=ppc64 ppc64el)_nettle_chacha_core_altivec@NETTLE_INTERNAL_8_3 3.7.2
- (arch=armel armhf ppc64 ppc64el)_nettle_chacha_core_c@NETTLE_INTERNAL_8_3 
3.7.2
- (arch=armel armhf)_nettle_chacha_core_neon@NETTLE_INTERNAL_8_3 3.7.2
+#MISSING: 3.7.2-2# (arch=armel armhf ppc64 
ppc64el)_nettle_chacha_core_c@NETTLE_INTERNAL_8_3 3.7.2
+#MISSING: 3.7.2-2# (arch=armel 
armhf)_nettle_chacha_core_neon@NETTLE_INTERNAL_8_3 3.7.2
  (arch=armel armhf ppc64 
ppc64el)_nettle_chacha_crypt32_1core@NETTLE_INTERNAL_8_3 3.7.2
  (arch=armel armhf)_nettle_chacha_crypt32_3core@NETTLE_INTERNAL_8_3 3.7.2
  (arch=ppc64 ppc64el)_nettle_chacha_crypt32_4core@NETTLE_INTERNAL_8_3 3.7.2
dh_makeshlibs: error: failing due to earlier errors
make: *** [debian/rules:4: binary-arch] Error 25

See
https://buildd.debian.org/status/fetch.php?pkg=nettle&arch=armel&ver=3.7.2-2&stamp=1617647308&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#986387: cdrom: Unsuccessful installation on Windows10-Dell-Latitude-Ultrabook. No grub.

[Steve McIntyre]

Hi enno,

On Mon, Apr 05, 2021 at 12:37:11AM +0200, enno wrote:
>Package: cdrom
>Severity: important
>
>Jigdone a debian-10.9.0-amd64-xfce-CD1 USB-Stick.  Booted a Dell Latitude
>Ultrabook with preinstalled Windows 10 from aforesaid USB-Stick.  Performed
>full installation including resizing the NTFS partition and including
>installation of grub(2).  Rebooted.  No bootable media found.
>On reboot via F12 I could select Windows Boot Manager to boot successfully into
>Windows10.  But Grub or Linux are not available.
>
>Windows10 recognises the resize of the NTFS partition, the
>additional partitions sda4 (root) and sda5 (swap) are recognised as well.
>
>UEFI booting presents a "normal" Windows 10.
>Legacy booting says, no bootable media found.
>Booting via UEFI-->Windows Bootmanager boots Windows 10.
>Legacy AND UEFI booting Installation-USB-Stick work up to the point to
>register the disk(s), and there it stops, it doesn't seem to recognise the
>partition table, that the installer has written and is also reported by
>Windows10.
>
>It just presents an unformatted disk of MAX units to go on with.  But Windows
>DatentrÀgerverwaltung does indeed see the created partitions.
>
>I'm at a loss.

Hmmm. Curious on a few things. Did you boot the installer initially in
CSM or BIOS mode? How is the BIOS/firmware on your machine configured
in terms of booting? Is it set up to boot UEFI only? I'm worried that
your system is normally only configured to use UEFI, but you've
started the installer in BIOS mode and that has caaused your problems.

Another issue that sometimes hits users on Dell laptops is the disk
controller setup. They're quite often set up by default in "RAID"
mode, and you may need to switch to "AHCI" to allow Linux to work
well.

-- 
Steve McIntyre, Cambridge, UK.st...@einval.com
"Yes, of course duct tape works in a near-vacuum. Duct tape works
 anywhere. Duct tape is magic and should be worshipped."
   -― Andy Weir, "The Martian"

Bug#986428: unblock: nettle/3.7.2-2

[Magnus Holmgren]

Package: release.debian.org 
User: release.debian@packages.debian.org 
Usertags: unblock 
Severity: normal 

Please unblock package nettle. See https://lists.debian.org/debian-release/
2021/03/msg00843.html for discussion.

unblock nettle/3.7.2-2

-- 
Magnus Holmgrenholmg...@debian.org
Debian Developer 

signature.asc
Description: This is a digitally signed message part.

Bug#986256: [RFS] simka: test failure common denominator ci-worker13

[Étienne Mollier]

Hi Paul, Hi Nilesh,

when looking up that issue today, I noticed on the CI web
page[1], that all tests were failing on one given host, which is
ci-worker13.  I would thus suspect, that the failure is
triggered by some hardware specific configuration: maybe core
count (ci-worker13 reports builds with 48 parallel jobs), memory
size, or something more exotic.

[1]: https://ci.debian.net/packages/s/simka/testing/amd64/

Looking then further, I think I'm on a good trail on the high
cores count hypothesis.  I can reproduce some severe slowdowns
using qemu with 48 cpus overcommit, or even less.  Actually I
could bissect clunky execution speed of the test case past 8 cpu
cores allocated.  As far as I can tell, passing CI runs only
occurred on 2 cpu cores count machines, so they seem consistent
with my own observations.

I brought a change on simka run-unit-test on Salsa[2], to cap
the execution of simka to 8 cores in the context of the test and
address the issue.  simka 1.5.3-3 is available for review, and
possibly upload, feel also free to grant dm rights if you feel
appropriate.  Note that CI pipeline is on hold, but I expect the
blhc test to fail due to missing compilation flags; other CI
tests did seem to pass on my end.

[2]: https://salsa.debian.org/med-team/simka/

Hopefully the slowdown is specific to the test case, but this
might need to be brought upstream.  Thanks for having caught it!

Kind Regards,
-- 
Étienne Mollier 
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/2, please excuse my verbosity.


signature.asc
Description: PGP signature

Bug#986427: psgml: causes emacs-gtk to fail to upgrade from buster to bullseye

[Andreas Beckmann]

Package: psgml
Version: 1.4.0-11
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails.

This problem was observed by first performing 'apt-get upgrade' (which
upgrades psgml) followed by 'apt-get dist-upgrade' (which upgrades
emacs-gtk).
It does not happen if only 'apt-get dist-upgrade' is executed, i.e. both
packages are upgraded in one run.
--install-recommends was disabled during all these tests

From the attached log (scroll to the bottom...):

[... during apt-get upgrade ...]
  Preparing to unpack .../78-psgml_1.4.0-11_all.deb ...
  Remove psgml for emacs
  remove/psgml: Ignoring emacsen flavor emacs.
  Remove psgml for emacs
  remove/psgml: Ignoring emacsen flavor emacs.
  Unpacking psgml (1.4.0-11) over (1.4.0-7) ...
[...]
  Setting up psgml (1.4.0-11) ...
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install psgml for emacs
  install/psgml: Byte-compiling for emacs...Loading 
/etc/emacs/site-start.d/00debian.el (source)...
  
  In toplevel form:
  psgml.el:719:26:Warning: (lambda (foo) ...) quoted with ' rather than with #'
  
  In sgml-mode:
  psgml.el:1225:52:Warning: assignment to free variable `which-func-format'
  
  In sgml-set-buffer-multibyte:
  psgml-parse.el:365:16:Warning: assignment to free variable `mc-flag'
  
  In sgml-set-active-dtd-indicator:
  psgml-parse.el:2898:47:Warning: assignment to free variable `which-func-mode'
  
  In sgml-kill-markup:
  psgml-edit.el:247:4:Warning: value returned from (/= 0 (skip-chars-forward "  
  
")) is unused
  psgml-edit.el:247:4:Warning: value returned from (= 0 (skip-chars-forward "   
  
")) is unused
  psgml-edit.el:247:4:Warning: value returned from (= (skip-chars-forward " 
  
") 0) is unused
  
  In sgml-edit-external-entity:
  psgml-edit.el:1975:62:Warning: Use `with-current-buffer' rather than
  save-excursion+set-buffer
  psgml-edit.el:1977:24:Warning: `process-kill-without-query' is an obsolete
  function (as of 22.1); use `process-query-on-exit-flag' or
  `set-process-query-on-exit-flag'.
  
  In sgml-append-to-help-buffer:
  psgml-edit.el:2177:36:Warning: Use `with-current-buffer' rather than
  save-excursion+set-buffer
  
  In sgml-show-structure:
  psgml-edit.el:2412:6:Warning: Use `with-current-buffer' rather than
  save-excursion+set-buffer
  
  In end of data:
  psgml-edit.el:2475:1:Warning: the function `string-to-int' is not known to be
  defined.
  
  In sgml-parse-entity-type:
  psgml-dtd.el:646:8:Warning: value returned from (/= 0 (skip-chars-forward "   
  
")) is unused
  psgml-dtd.el:646:8:Warning: value returned from (= 0 (skip-chars-forward "
  
")) is unused
  psgml-dtd.el:646:8:Warning: value returned from (= (skip-chars-forward "  
  
") 0) is unused
  psgml-dtd.el:646:8:Warning: value returned from (= (skip-chars-forward "  
  
") 0) is unused
  psgml-dtd.el:646:8:Warning: value returned from (= (skip-chars-forward "  
  
") 0) is unused
  
  In sgml-write-dtd:
  psgml-dtd.el:1010:9:Warning: assignment to free variable `file-type'
  
  In end of data:
  psgml-dtd.el:1016:1:Warning: the function `string-to-int' is not known to be
  defined.
  Done compiling
  WARNING: tempfile is deprecated; consider using mktemp instead.
  
  Creating config file /etc/emacs/site-start.d/50psgml-init.el with new version
   done.

[... during subsequent apt-get dist-upgrade ...]
  Preparing to unpack .../02-emacs-gtk_1%3a27.1+1-3_amd64.deb ...
  Remove psgml for emacs
  remove/psgml: Removing for emacs... done.
  Remove emacsen-common for emacs
  emacsen-common: Handling removal of emacsen flavor emacs
  Unpacking emacs-gtk (1:27.1+1-3) over (1:26.1+1-3.2+deb10u2) ...
[...]
  Setting up emacs-gtk (1:27.1+1-3) ...
  Install emacsen-common for emacs
  emacsen-common: Handling install of emacsen flavor emacs
  Install psgml for emacs
  install/psgml: Byte-compiling for emacs...cp: cannot stat 'Makefile-el': No 
such file or directory
  ERROR: install script from psgml package failed
  dpkg: error processing package emacs-gtk (--configure):
   installed emacs-gtk package post-installation script subprocess returned 
error exit status 1
  Setting up librsvg2-common:amd64 (2.50.3+dfsg-1) ...
  Setting up systemd-timesyncd (247.3-3) ...
  Created symlink 
/etc/systemd/system/sysinit.target.wants/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.
  Setting up systemd (247.3-3) ...
  Installing new version of config file /etc/systemd/journald.conf ...
  Installing new version of config file /etc/systemd/logind.conf ...
  Installing new version of config file /etc/systemd/networkd.conf ...
  Installing new version of config file /etc/systemd/resolved.conf ...
  Installing new version of config file /etc/systemd/system.conf ...
  Installing new version o

Bug#980536: raspi-firmware: CMA=64M too small for 4K display and vc4.ko in 5.10 kernel

[Gunnar Wolf]

tags -1 wontfix
severity -1 wishlist
thanks

Hi,

There are Raspberries in use with memory ranging from 256M (512M
currently for sale) to 8G. I do not want to ship a package that's
unusable in all of the 0 and 1 families.

As you mention in your bug report, it's easy to do this fix in
/etc/default/raspi-firmware -- that's the reason for it to exist!

Please note /etc/default/raspi-firmware discourages setting a CMA in
the RPi4 family. I don't have the needed hardware (i.e. 4K monitor) to
test this, but I do remember having unbootable RPi4 when I had CMA
set.

I'm tagging this bug as "wontfix", at least for the time being. I
think it's best for all users to be able to boot (and then tweak as
you did) than to make it more difficult for some users to get to basic
system functionality.

Bug#603340: ugly error messages with "http:" appended when cannot connect

[Vincent Lefevre]

Package: libapt-pkg6.0
Version: 2.2.2
Severity: normal
Followup-For: Bug #603340

Raising severity to normal. Until I saw this bug, I thought that apt
got seriously broken by connecting to a wrong hostname (which could
have explained the connection failure).

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-security'), (500, 
'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-5-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libapt-pkg6.0 depends on:
ii  libbz2-1.0   1.0.8-4
ii  libc62.31-11
ii  libgcc-s110.2.1-6
ii  libgcrypt20  1.8.7-3
ii  liblz4-1 1.9.3-1
ii  liblzma5 5.2.5-2
ii  libstdc++6   10.2.1-6
ii  libsystemd0  247.3-3
ii  libudev1 247.3-3
ii  libxxhash0   0.8.0-2
ii  libzstd1 1.4.8+dfsg-2.1
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages libapt-pkg6.0 recommends:
ii  apt  2.2.2

libapt-pkg6.0 suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#986408: mali-midgard-dkms: Fail to install/build

[Christian Marillat]

On 05 avril 2021 17:28, Chris Hofstaedtler  wrote:

> Hello Christian,

Hello Chris,


[...]

>> RELEASES_ORDER.sort(key=lambda n: float(n[0]))
>>   File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in 
>> RELEASES_ORDER.sort(key=lambda n: float(n[0]))
>> ValueError: could not convert string to float: '6.06 LTS'
>
> Please try running this, and see if that also fails:
>
> lsb_release -s -i
>
> I think your system configuration confuses lsb_release. If so,
> please reassign to lsb-release.

Yes this is a bug in lsb-release. I'll reassign to lsb-release.

Otherwise mali-midgard-dkms fail to build with  latest 5.10 kernel.

Christian

Bug#977367: debsources: search results point to not existing sources?

[Matthieu Caneill]

Control: usertag -1 debsources
Control: merge 761077 -1

Hi Tomas,

On Mon, Dec 14, 2020 at 02:13:49PM +0100, Tomas Pospisek wrote:
> Go to 
> https://codesearch.debian.net/search?q=Client+sent+an+HTTP+request+to+an+HTTPS+server
> select first link 
> https://codesearch.debian.net/show?file=gcc-10_10.2.1-1%2Fgcc-10.2.0%2Flibgo%2Fgo%2Fnet%2Fhttp%2Fserver.go&line=1798
> get a 404 with a list of 12 alternative source files of different
> versions of gcc-XX/XX.Y.Z-W/gcc-XX.V.U/libgo/go/net/http/server.go
> each returning a 404.
> 
> I have now clicked through quite a few links to source files, but
> have yet to find one that won't return a 404...?
> 
> Maybe the search index would need to be purged of source files that
> have disappeared (been updated) or something?

Thank you very much for the detailed bug report, and apologies for the
delay in getting back to you.

After further inspection, it turns out the tarball containing the
source for gcc-10 contains embedded tarballs. See
http://deb.debian.org/debian/pool/main/g/gcc-10/gcc-10_10.2.1.orig.tar.xz
and https://sources.debian.org/src/gcc-10/10.2.0-3/

Debsources unpacked the first tarball, and the embedded ones are
technically the "source" of gcc-10. The path you obtained from
codesearch.debian.net points to a file inside the tarball inside the
tarball; this is unfortunately not supported by sources.d.o.

I didn't know codesearch supported this feature. CCing Michael, in
case you have an idea on how not to point to sources.d.o for code
results originating from unpacked archives. :)

Cheers,
--
Matthieu


signature.asc
Description: PGP signature

Bug#986161: fixed in droopy 0.20160830-4

[Ivo De Decker]

Hi,

On Sat, Apr 03, 2021 at 02:17:47PM +, Debian FTP Masters wrote:
> Binary: droopy
> Architecture: source all

Please note that you uploaded binaries. If you want the fix to (potentially)
migrate to testing, you'll need to do a new source-only upload (and file an
unblock request after that).

Cheers,

Ivo

Bug#986425: unblock: libfits-java/1.15.2-2

[Ole Streicher]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package libfits-java

[ Reason ]
The upload fixes RC Bug#986403: Compression doesn't work

[ Impact ]
The upload is required to actually make skyview, and transitively
topcat and other packages (especially the starjava packages) working.

[ Tests ]
The package was manually tested to work and to not have a negative
impact on its reverse dependencies.

[ Risks ]
The patch is obvious, and does not have known risks.

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing


unblock libfits-java/1.15.2-2

Best regards

Ole
diff -Nru libfits-java-1.15.2/debian/changelog 
libfits-java-1.15.2/debian/changelog
--- libfits-java-1.15.2/debian/changelog2017-10-05 08:55:15.0 
+0200
+++ libfits-java-1.15.2/debian/changelog2021-04-05 12:10:07.0 
+0200
@@ -1,3 +1,10 @@
+libfits-java (1.15.2-2) unstable; urgency=medium
+
+  * Team upload.
+  * Add resources files to jar (Closes: #986403)
+
+ -- Ole Streicher   Mon, 05 Apr 2021 12:10:07 +0200
+
 libfits-java (1.15.2-1) unstable; urgency=low
 
   * Team upload.
diff -Nru 
libfits-java-1.15.2/debian/patches/libfits-java_add-ant-build-system.patch 
libfits-java-1.15.2/debian/patches/libfits-java_add-ant-build-system.patch
--- libfits-java-1.15.2/debian/patches/libfits-java_add-ant-build-system.patch  
2017-10-03 16:09:30.0 +0200
+++ libfits-java-1.15.2/debian/patches/libfits-java_add-ant-build-system.patch  
2021-04-05 12:07:42.0 +0200
@@ -1,15 +1,26 @@
-Description: Added ANT build system
- The sources of the fits package are shipped in a
- jar archive which does not contain any build system.
- In order to provide checks on the source code,
- we have added a build system based on ANT.
- This system will also be used to build the Debian
- package of the fits library.
+From: Florian Rothmaier 
+Date: Thu, 17 Nov 2016 23:51:42 +0100
+Subject: Added ANT build system
+
 Origin: http://heasarc.gsfc.nasa.gov/docs/heasarc/fits/java/
-Author: Florian Rothmaier 
+
+The sources of the fits package are shipped in a
+jar archive which does not contain any build system.
+In order to provide checks on the source code,
+we have added a build system based on ANT.
+This system will also be used to build the Debian
+package of the fits library.
+---
+ build.xml | 183 ++
+ 1 file changed, 183 insertions(+)
+ create mode 100644 build.xml
+
+diff --git a/build.xml b/build.xml
+new file mode 100644
+index 000..b4cdb68
 --- /dev/null
 +++ b/build.xml
-@@ -0,0 +1,182 @@
+@@ -0,0 +1,183 @@
 +
 +
 +

Bug#986406: unblock: node-d3-dsv/1.1.1-4

[Yadd]

Control: tags -1 - moreinfo

Le 05/04/2021 à 13:28, Sebastian Ramacher a écrit :
> [...]
> The dependencies seem to be wrong:
> 
> $ json2dsv
> internal/modules/cjs/loader.js:818
>   throw err;
>   ^
> 
> Error: Cannot find module 'iconv-lite'
> Require stack:
> - /usr/share/nodejs/d3-dsv/bin/json2dsv
> at Function.Module._resolveFilename 
> (internal/modules/cjs/loader.js:815:15)
> at Function.Module._load (internal/modules/cjs/loader.js:667:27)
> at Module.require (internal/modules/cjs/loader.js:887:19)
> at require (internal/modules/cjs/helpers.js:74:18)
> at Object. (/usr/share/nodejs/d3-dsv/bin/json2dsv:6:13)
> at Module._compile (internal/modules/cjs/loader.js:999:30)
> at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
> at Module.load (internal/modules/cjs/loader.js:863:32)
> at Function.Module._load (internal/modules/cjs/loader.js:708:14)
> at Function.executeUserEntryPoint [as runMain] 
> (internal/modules/run_main.js:60:12) {
>   code: 'MODULE_NOT_FOUND',
>   requireStack: [ '/usr/share/nodejs/d3-dsv/bin/json2dsv' ]
> }

Hi,

Fixed and tested (build + autopkgtest):
rebuild  node-d3-fetch ... PASS
rebuild  node-d3-hierarchy ... PASS
rebuild  node-d3   ... PASS
autopkgtest  node-d3   ... PASS
autopkgtest  node-d3-fetch ... PASS


>>  * Remove useless debian/webpack.config.js
>>
>> [ Checklist ]
>>   [X] all changes are documented in the d/changelog
>>   [X] I reviewed all changes and I approve them
>>   [X] attach debdiff against the package in testing
>>
>> Cheers,
>> Yadd
>>
>> unblock node-d3-dsv/1.1.1-4
> 
>> diff --git a/debian/changelog b/debian/changelog
>> index 2678e16..dffccb2 100644
>> --- a/debian/changelog
>> +++ b/debian/changelog
>> @@ -1,3 +1,20 @@
>> +node-d3-dsv (1.1.1-4) unstable; urgency=medium
>> +
>> +  * Team upload
>> +
>> +  [ Pirate Praveen ]
>> +  * Drop node unused debian/webpack.config.js (we switched to rollup)
>> +
>> +  [ Yadd ]
>> +  * Bump debhelper compatibility level to 13
> 
> Please revert this change. It's no longer appropriate at this stage of
> the freeze.

Done

>> +  * Add "Rules-Requires-Root: no"
>> +  * Add debian/gbp.conf
>> +  * Modernize debian/watch
>> +  * Use dh-sequence-nodejs
> 
> This also just adds noise too the diff.

Done

> Cheers

Cheers,
Yadd
diff --git a/debian/changelog b/debian/changelog
index 2678e16..6b7d5f7 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,29 @@
+node-d3-dsv (1.1.1-5) unstable; urgency=medium
+
+  * Team upload
+  * Revert debhelper upgrade due to freeze
+  * Update debian/watch due to GitHub changes
+  * Replace node-iconv by node-iconv-lite in dependencies as required by 
package.json
+
+ -- Yadd   Mon, 05 Apr 2021 19:51:03 +0200
+
+node-d3-dsv (1.1.1-4) unstable; urgency=medium
+
+  * Team upload
+
+  [ Pirate Praveen ]
+  * Drop node unused debian/webpack.config.js (we switched to rollup)
+
+  [ Yadd ]
+  * Bump debhelper compatibility level to 13
+  * Add "Rules-Requires-Root: no"
+  * Add debian/gbp.conf
+  * Modernize debian/watch
+  * Use dh-sequence-nodejs
+  * Fix links (Closes: #985518)
+
+ -- Yadd   Sat, 20 Mar 2021 12:08:15 +0100
+
 node-d3-dsv (1.1.1-3) unstable; urgency=medium
 
   [ Debian Janitor ]
diff --git a/debian/control b/debian/control
index 6489133..23503df 100644
--- a/debian/control
+++ b/debian/control
@@ -22,7 +22,7 @@ Architecture: all
 Depends:
  ${misc:Depends}
  , nodejs
- , node-iconv (>= 0.4)
+ , node-iconv-lite (>= 0.4)
  , node-rw (>= 1)
  , node-commander (>= 2)
 Description: parser and formatter for delimiter-separated values, such as CSV
diff --git a/debian/copyright b/debian/copyright
index c3995ef..bd2f526 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -11,7 +11,7 @@ Files: debian/*
 Copyright: 2017 Pirate Praveen 
 License: BSD-3-Clause
 
-License: BSD-3-clause
+License: BSD-3-Clause
  Redistribution and use in source and binary forms, with or without
  modification, are permitted provided that the following conditions
  are met:
@@ -35,4 +35,3 @@ License: BSD-3-clause
  LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
  NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
  SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
diff --git a/debian/gbp.conf b/debian/gbp.conf
new file mode 100644
index 000..b713356
--- /dev/null
+++ b/debian/gbp.conf
@@ -0,0 +1,5 @@
+[DEFAULT]
+pristine-tar = True
+
+[import-orig]
+filter = [ '.gitignore', '.travis.yml', '.git*' ]
diff --git a/debian/links b/debian/links
deleted file mode 100644
index 2d71628..000
--- a/debian/links
+++ /dev/null
@@ -1,9 +0,0 @@
-usr/lib/nodejs/d3-dsv/bin/dsv2dsv usr/bin/csv2tsv
-usr/lib/nodejs/d3-dsv/bin/json2dsv usr/bin/json2csv
-usr/lib/nodejs/d3-dsv/bin/json2dsv usr/bin/json2tsv
-usr/lib/nodejs/d3-dsv/bin/dsv2json usr/bin/dsv2json
-usr/lib/nodejs/d3-dsv/bin/dsv2dsv usr/bin/dsv2dsv
-usr/lib/nodejs/d3-dsv/bin/dsv2json usr/bin/csv2json
-usr/lib/

Bug#986424: unblock: skyview/3.5.5+repack-2

[Ole Streicher]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package skyview

[ Reason ]
The new upload fixes the RC Bug#986392: skyview fails to start.

[ Impact ]
Skyview is a dependency of the starjava packages which feature the
important astronomy program "topcat".

[ Tests ]
The upload was tested manually to work, and to not impact its reverse
dependencies.

[ Risks ]
The change is an obious fix without known risks.

[ Checklist ]
  [X] all changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in testing

unblock skyview/3.5.5+repack-2


Best regards

Ole
diff -Nru skyview-3.5.5+repack/debian/changelog 
skyview-3.5.5+repack/debian/changelog
--- skyview-3.5.5+repack/debian/changelog   2021-01-13 21:26:41.0 
+0100
+++ skyview-3.5.5+repack/debian/changelog   2021-04-05 12:00:20.0 
+0200
@@ -1,3 +1,9 @@
+skyview (3.5.5+repack-2) unstable; urgency=medium
+
+  * Include default settings file and intro in skyview jar (Closes: #986392)
+
+ -- Ole Streicher   Mon, 05 Apr 2021 12:00:20 +0200
+
 skyview (3.5.5+repack-1) unstable; urgency=medium
 
   * New upstream version 3.5.5+repack
diff -Nru skyview-3.5.5+repack/debian/rules skyview-3.5.5+repack/debian/rules
--- skyview-3.5.5+repack/debian/rules   2021-01-13 21:25:33.0 +0100
+++ skyview-3.5.5+repack/debian/rules   2021-04-05 10:14:04.0 +0200
@@ -2,6 +2,7 @@
 
 export JAVA_HOME=/usr/lib/jvm/default-java
 export 
CLASSPATH=/usr/share/java/jsamp.jar:/usr/share/java/fits.jar:/usr/share/java/ij.jar:/usr/share/java/commons-io.jar:/usr/share/java/commons-math3.jar
+export JH_JAR_EXTRA=skyview.settings onlineintro.txt
 
 %:
dh $@ --with javahelper 

Bug#986351: (no subject)

[slow_speed]

If I understand your explanation, the hplip print queue works 
correctly.  Therefore, the hold placed upon the print jobs must come 


from somewhere else in the Debian system.

Can you at least give me another subject under which to post this bug?

Bug#939579: Your software is still bugged !?!?

[肖盛文]

Hi,phamiet,

    Which desktop do you use? Is it Xfce?

I use Xfce, and also meet the same bug.

I also think that the bug your report is the same as #932088

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932088

I'd add some debug info for it before.


在 2021/4/5 下午7:01, pham...@bluewin.ch 写道:
> Hi,
>
> It will soon be 1 year and a half that your software is bugged, would
> you be kind enough to do something to make it finally work correctly ? 
>
> Regards.

-- 
肖盛文 xiao sheng wen Faris Xiao 
微信(wechat)：atzlinux
《铜豌豆 Linux》https://www.atzlinux.com
基于 Debian 的 Linux 中文 桌面 操作系统
Debian QA page: https://qa.debian.org/developer.php?login=atzlinux%40sina.com
GnuPG Public Key: 0x00186602339240CB



OpenPGP_signature
Description: OpenPGP digital signature

Bug#986423: msr: Write to unrecognized MSR 0x49 by perl caused by spectre-meltdown-checker

[curious_debian]

Package: spectre-meltdown-checker
Version: 0.44-1~bpo10+1
Severity: normal

Dear Maintainer,

Each run of spectre-meltdown-checker causes dmesg to print out a line:
msr: Write to unrecognized MSR 0x49 by perl (pid: 531711). Please report to
x...@kernel.org.

I have reported this to kernel devs, and they have replied with this list:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/about/

Indeed this code is there:
0x49perl (spectre-meltdown-
checker.sh)

Can you please fix your package as explained by kernel.org page.
Thank you.


Using Debian Buster AMD64 with AMD Ryzen 1700 processor.



-- System Information:
Debian Release: 10.9
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (10, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-0.bpo.4-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CPU_OUT_OF_SPEC, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

Bug#986006: libpdfbox2-java: CVE-2021-27807

[tony mancill]

On Sat, Mar 27, 2021 at 07:52:37PM +0100, Salvatore Bonaccorso wrote:
> Source: libpdfbox2-java
> Version: 2.0.22-1
> Severity: important
> Tags: security upstream
> X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> 

Hi Salvatore,

I'm continuing our thread from 986008, but switching over the BTS entry
986006 for CVE-2021-27807 to try to cut down on confusion between the CVEs.
Below is why I marked this bug as fixed in 2.0.23-1.  I haven't yet
identified the exact commit(s), but will update bug if I can locate it.

From https://pdfbox.apache.org/#news:

> CVE-2021-27807, CVE-2021-27906 Infinite loop and OutOfMemory
> 2021-03-20
> CVE-2021-27807: A carefully crafted PDF file can trigger an infinite loop 
> while loading the file.
> 
> CVE-2021-27906: A carefully crafted PDF file can trigger an 
> OutOfMemory-Exception while loading the file.
> 
> Versions Affected: Apache PDFBox <= 2.0.22
> 
> Mitigation: Upgrade to Apache PDFBox 2.0.23

Note that others have drawn the same conclusion from the announcement -
e.g. 
https://github.com/apache/ofbiz-framework/commit/df69401118c99896432b417690f2229bc757072c

Thanks,
tony


signature.asc
Description: PGP signature

Bug#986008: libpdfbox2-java: CVE-2021-27906

[tony mancill]

On Mon, Apr 05, 2021 at 05:15:12PM +0200, Salvatore Bonaccorso wrote:
> On Sun, Apr 04, 2021 at 09:05:06PM -0700, tony mancill wrote:
> > On Sat, Mar 27, 2021 at 07:54:11PM +0100, Salvatore Bonaccorso wrote:
> > > Source: libpdfbox2-java
> > > Version: 2.0.22-1
> > > Severity: important
> > > Tags: security upstream
> > > Forwarded: https://issues.apache.org/jira/browse/PDFBOX-5112
> > > X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> > > 
> > 
> > Hi,
> > 
> > I took a look at this and I think the best thing to do for our users is
> > to upload 2.0.23 instead of trying pick backport just the CVE changes
> > from this set of commits [1].
> > 
> > The 2.0.23 package builds without any other changes and doesn't
> > introduce any API changes [2].  This will address both CVE-2021-27807
> > and CVE-2021-27906.
> > 
> > I have an upload ready (using DEP-14 branches, so it won't change
> > master).  I originally considered uploading 2.0.23 to experimental due
> > to the freeze, but I think it should go to unstable and then we can
> > discuss what we do for bullseye.
> 
> Do you by chance have any more details on CVE-2021-27807? The two
> posts to oss-security were a bit scarce on details for CVE-2021-27807.
> For CVE-2021-27906 at least there was a point to a respective upstream
> issue.

Err, I'm glad you asked.  I'm looking through my notes and I think I
made a mistake about CVE-2021-27807 being in 2.0.23.  I will mark the
bug as not-fixed and follow up.

> Abuout the upload to unstable, would it maybe be sensible to ask first
> of a pre-pprovial to the release team?

Yes, it definite is sensible.  For this issue, I think the cherry-pick
approach is more likely to result in problems for users than the updated
version.  If the Release Team does not agree, I will track the issue and
work through s-p-u, or at least backports.

Thank you,
tony


signature.asc
Description: PGP signature

Bug#986371: qemu-system-x86: /proc/stat on host does not show guest cpu usage

[Chris Hofstaedtler]

* Michael Tokarev  [210405 15:40]:
> In the stock linux kernel, as far as I can see, there's no counting for this 
> info for x86
> architecture, - it is only counted for ia64, powerpc and s390x architectures.

I think this is not quite true. Even on x86, guest_enter_irqoff gets
called by the kvm kernel code (from svm_vcpu_enter_exit). I think
it should just work?

> I'm not an expert in this area, maybe you can find out what ubuntu does here 
> and ask debian
> kernel guys to include the same in debian. As far as I can see, there's 
> nothing qemu can do
> about it as long as kernel itself does not provide a way to update this 
> information.

I guess qemu doesn't need to do anything except use KVM.

If it does not work, probably best to ask the kernel folk if they
have any ideas?

Chris

Bug#986399: sgf2dg: The sgf2dg program fails to start on bullseye

[Chris Hofstaedtler]

Control: tags -1 + moreinfo

Hello John,

* John Green  [210405 15:34]:
> Package: sgf2dg
> Version: 4.252-1

> The sgf2dg program fails to start. It reports an error message that
> begins as follows.
> 
> Can't locate Games/Go/Diagram.pm in @INC (you may need to install the 
> Games::Go::Diagram module)

I have given this a short try, and cannot reproduce the problem
here (i.e. it "just works" for me).
Can you show us your exact command line, and what else you might
have tried?

Chris

Bug#986408: mali-midgard-dkms: Fail to install/build

[Chris Hofstaedtler]

Hello Christian,

* Christian Marillat  [210405 15:26]:
> This package fail to install/build with :
> 
> $ sudo apt-get dist-upgrade 
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Calculating upgrade... Done
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> 1 not fully installed or removed.
> After this operation, 0 B of additional disk space will be used.
> Do you want to continue? [Y/n] 
> Setting up mali-midgard-dkms (16.0+pristine-4) ...
> Building for 5.10.0-5-arm64
> Traceback (most recent call last):
>   File "/usr/bin/lsb_release", line 95, in 
> main()
>   File "/usr/bin/lsb_release", line 59, in main
> distinfo = lsb_release.get_distro_information()
>   File "/usr/lib/python3/dist-packages/lsb_release.py", line 356, in 
> get_distro_information
> distinfo = guess_debian_release()
>   File "/usr/lib/python3/dist-packages/lsb_release.py", line 246, in 
> guess_debian_release
> get_distro_info(distinfo['ID'])
>   File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in 
> get_distro_info
> RELEASES_ORDER.sort(key=lambda n: float(n[0]))
>   File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in 
> RELEASES_ORDER.sort(key=lambda n: float(n[0]))
> ValueError: could not convert string to float: '6.06 LTS'

Please try running this, and see if that also fails:

lsb_release -s -i

I think your system configuration confuses lsb_release. If so,
please reassign to lsb-release.

Best,
Chris

Bug#986421: ITP: nxtrim -- Optimized trimming of Illumina mate pair reads

[Nilesh Patra]

Package: wnpp
Severity: wishlist
Owner: Nilesh Patra 
X-Debbugs-Cc: debian-de...@lists.debian.org, nil...@debian.org

* Package name: nxtrim
  Version : 0.4.3+dfsg
  Upstream Author : Illumina, Inc.
* URL : https://github.com/sequencing/NxTrim
* License : BSD
  Programming Lang: C++
  Description : Optimized trimming of Illumina mate pair reads
  This package helps rmove Nextera Mate Pair junction adapters
  and categorise reads according to the orientation implied
  by the adapter location.

  I shall maintain this package

Bug#986008: libpdfbox2-java: CVE-2021-27906

[Salvatore Bonaccorso]

Hi,

On Sun, Apr 04, 2021 at 09:05:06PM -0700, tony mancill wrote:
> On Sat, Mar 27, 2021 at 07:54:11PM +0100, Salvatore Bonaccorso wrote:
> > Source: libpdfbox2-java
> > Version: 2.0.22-1
> > Severity: important
> > Tags: security upstream
> > Forwarded: https://issues.apache.org/jira/browse/PDFBOX-5112
> > X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> > 
> 
> Hi,
> 
> I took a look at this and I think the best thing to do for our users is
> to upload 2.0.23 instead of trying pick backport just the CVE changes
> from this set of commits [1].
> 
> The 2.0.23 package builds without any other changes and doesn't
> introduce any API changes [2].  This will address both CVE-2021-27807
> and CVE-2021-27906.
> 
> I have an upload ready (using DEP-14 branches, so it won't change
> master).  I originally considered uploading 2.0.23 to experimental due
> to the freeze, but I think it should go to unstable and then we can
> discuss what we do for bullseye.

Do you by chance have any more details on CVE-2021-27807? The two
posts to oss-security were a bit scarce on details for CVE-2021-27807.
For CVE-2021-27906 at least there was a point to a respective upstream
issue.

Abuout the upload to unstable, would it maybe be sensible to ask first
of a pre-pprovial to the release team?

Regards,
Salvatore

Bug#986410: autopkg tests don't run with the same dependencies as during the build

[Matthias Klose]

On 4/5/21 3:30 PM, Andreas Tille wrote:
> Hi Matthias,
> 
> On Mon, Apr 05, 2021 at 02:46:41PM +0200, Matthias Klose wrote:
>> The autopkg tests don't run with the same dependencies as during the build. 
>> Just
>> noticed because the python3-renderpm dependency seems to be necessary with 
>> the
>> reportlab package from experimental.
>>
>> But in general, please run the autopkg tests with the same packages as done
>> during the build.
> 
> Could you please be more verbose.  The Build-Depends and Depends string
> do not do any specific version specification.  Python3-reportlab was
> added to Depends since it is really needed while python3-renderpm is
> fine as "Suggests".  Which change would you recommend to solve that bug?

please re-read. This is not about package dependencies or suggestions. All the
 build dependencies should be added as autopkg test dependencies to
test the same stuff you test during the build, unless there's a specific reason
not to do so.

Matthias

Bug#986351: (no subject)

[slow_speed]

The command completed:

sudo lpadmin -p PRINTQ -v 
"usb://HP/Photosmart%20C3100%20series?serial=CN668B721G04KV&interface=1" 
-E -m "drv:///hpcups.drv/hp-photosmart_c3100_series.ppd"


Then the print command completed:

  lp -d PRINTQ /etc/nsswitch.conf
request id is PRINTQ-544 (1 file(s))

But then paper was pulled and the printing stopped and the power button 
light is flashing.  (No error light.)



Tried again, and this time it worked fine.

What does this tell you?

Bug#986351: (no subject)

[slow_speed]

Meant to say that I shut down the printer, waited for the process to 
finish, then turned it on again before retrying.

Bug#986371: qemu-system-x86: /proc/stat on host does not show guest cpu usage

[Thomas Scholz]

Thanks a lot for your explanation! 

So, if I understand correctly, you say, it is a kernel-issue, because the 
standard-kernel does not include these counters for x86 and the Ubuntu-team 
obviously has done some special „hack“ to provide those counters also for x86.

Although I’m a programmer, I have no idea whatsoever of the linux kernel. Could 
you please point me to these modules you mentioned for ia64/powerpc/s390x that 
have the counting and the module for x86 that doesn’t? Then I can try to find 
out what the Ubuntu guys had done there.

If I manage to get to this point, I will get in contact with the Debian kernel 
team.

Kind regards,
Tom



Am 05.04.2021 um 10:49 schrieb Michael Tokarev :

Control: tag -1 + moreinfo
Control: severity -1 wishlist

04.04.2021 18:23, Thomas Scholz wrote:
> Package: qemu-system-x86
> Version: 1:5.2+dfsg-9
> Severity: normal
> Dear Maintainer,
>   * What led up to the situation?
> I have two hosts, running several KVM/qemu guests. The first host runs on 
> Ubuntu 20.10 and shows
> under /proc/stat in the 9th column the values for the CPU-usage of the guests.
> The other host (=this host) under Debian testing does not show these values, 
> rather the guest's
> CPU-usage is included in the system-stat (3rd column).

I see what you're talking about. I've no idea what does ubuntu do to provide 
this information.

In the stock linux kernel, as far as I can see, there's no counting for this 
info for x86
architecture, - it is only counted for ia64, powerpc and s390x architectures.

I'm not an expert in this area, maybe you can find out what ubuntu does here 
and ask debian
kernel guys to include the same in debian. As far as I can see, there's nothing 
qemu can do
about it as long as kernel itself does not provide a way to update this 
information.

/mjt

Bug#986420: ModuleNotFoundError: No module named 'gi' (missing dependency on python3-gi ?)

[Alexis Murzeau]

Package: smart-notifier
Version: 0.28-6
Severity: important

Dear Maintainer,

smart-notifier does not depend on python3-gi.
When running smart-notifier, it fails:

$ smart-notifier
Traceback (most recent call last):
  File "/usr/bin/smart-notifier", line 13, in 
import smart_notifier.gui
  File "/usr/share/smart-notifier/smart_notifier/gui.py", line 23, in 
from gi.repository import Gtk
ModuleNotFoundError: No module named 'gi'


After installing python3-gi, smart-notifier runs fine and is able to show
notifications.

So I think smart-notifier should depend on python3-gi as it seems to be required
for proper GUI operation.
The failing import is made here:
https://sources.debian.org/src/smart-notifier/0.28-6/src/smart_notifier/gui.py/#L23

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (950, 'unstable'), (500, 'unstable-debug'), (500, 'testing'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages smart-notifier depends on:
ii  dbus1.12.20-1
ii  gir1.2-gtk-3.0  3.24.24-3
ii  python3 3.9.2-2
ii  python3-dbus1.2.16-4
ii  smartmontools   7.2-1

smart-notifier recommends no packages.

smart-notifier suggests no packages.

-- no debconf information

Bug#986419: python3-botocore: Version of python3-botocore in stable does not support IMDSv2

[Shane Frasier]

Package: python3-botocore
Version: 1.12.103+repack-1
Severity: normal

Dear Maintainer,

Version 1.12.103 of this package is sufficiently old that it does not
support the more secure IMDSv2.  Is it possible to get the testing 
version (1.20.0) into stable-backports?  This seems like it would help 
many (especially cloud) users.

I'm able to build a new deb package for stable-backports using the
instructions here:
https://wiki.debian.org/BuildingFormalBackports
I can't upload it, though, since I'm new to Debian contribution process.
I'm happy to help in any way I can.

Thanks,
Shane


-- System Information:
Debian Release: 10.9
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-16-cloud-amd64 (SMP w/2 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-botocore depends on:
ii  python3   3.7.3-1
ii  python3-dateutil  2.7.3-3
ii  python3-docutils  0.14+dfsg-4
ii  python3-jmespath  0.9.4-1
ii  python3-requests  2.21.0-1
ii  python3-urllib3   1.24.1-1

python3-botocore recommends no packages.

python3-botocore suggests no packages.

-- no debconf information

Bug#986417: system-information kernel-resume

[Andi Glaeser mobil]

andrew@eb8440p:~$ sudo lspci -vn
00:00.0 0600: 8086:0044 (rev 02)
Subsystem: 103c:172a
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0c 

00:02.0 0300: 8086:0046 (rev 02) (prog-if 00 [VGA controller])
Subsystem: 103c:172a
Flags: bus master, fast devsel, latency 0, IRQ 32
Memory at d000 (64-bit, non-prefetchable) [size=4M]
Memory at c000 (64-bit, prefetchable) [size=256M]
I/O ports at 5050 [size=8]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915

00:16.0 0780: 8086:3b64 (rev 06)
Subsystem: 103c:172a
Flags: bus master, fast devsel, latency 0, IRQ 33
Memory at d4724000 (64-bit, non-prefetchable) [size=16]
Capabilities: [50] Power Management version 3
Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: mei_me
Kernel modules: mei_me

00:19.0 0200: 8086:10ea (rev 05)
Subsystem: 103c:172a
Flags: bus master, fast devsel, latency 0, IRQ 30
Memory at d470 (32-bit, non-prefetchable) [size=128K]
Memory at d472a000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 5020 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
Kernel driver in use: e1000e
Kernel modules: e1000e

00:1a.0 0c03: 8086:3b3c (rev 05) (prog-if 20 [EHCI])
Subsystem: 103c:172a
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at d4729000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1b.0 0403: 8086:3b56 (rev 05)
Subsystem: 103c:172a
Flags: bus master, fast devsel, latency 0, IRQ 34
Memory at d472 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 0604: 8086:3b42 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 27
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: d460-d46f
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: 103c:172a
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport

00:1c.1 0604: 8086:3b44 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 28
Bus: primary=00, secondary=02, subordinate=42, sec-latency=0
I/O behind bridge: 3000-4fff
Memory behind bridge: d060-d45f
Prefetchable memory behind bridge: d490-d4af
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: 103c:172a
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport

00:1c.3 0604: 8086:3b48 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 29
Bus: primary=00, secondary=43, subordinate=43, sec-latency=0
Memory behind bridge: d050-d05f
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: 103c:172a
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport

00:1d.0 0c03: 8086:3b34 (rev 05) (prog-if 20 [EHCI])
Subsystem: 103c:172a
Flags: bus master, medium devsel, latency 0, IRQ 20
Memory at d4728000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1e.0 0604: 8086:2448 (rev a5) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=44, subordinate=45, sec-latency=64
I/O b

Bug#986008: libpdfbox2-java: CVE-2021-27906

[tony mancill]

On Mon, Apr 05, 2021 at 09:37:41AM +0200, Markus Koschany wrote:
> Am Sonntag, den 04.04.2021, 21:05 -0700 schrieb tony mancill:
> > On Sat, Mar 27, 2021 at 07:54:11PM +0100, Salvatore Bonaccorso wrote:
> > > Source: libpdfbox2-java
> > > Version: 2.0.22-1
> > > Severity: important
> > > Tags: security upstream
> > > Forwarded: https://issues.apache.org/jira/browse/PDFBOX-5112
> > > X-Debbugs-Cc: car...@debian.org, Debian Security Team <
> > > t...@security.debian.org>
> > 
> > Hi,
> > 
> > I took a look at this and I think the best thing to do for our users is
> > to upload 2.0.23 instead of trying pick backport just the CVE changes
> > from this set of commits [1].
> > 
> > The 2.0.23 package builds without any other changes and doesn't
> > introduce any API changes [2].  This will address both CVE-2021-27807
> > and CVE-2021-27906.
> 
> That sounds reasonable to me. Thanks for the update!
 
Hi Markus,

It is done.

The only thing that's a little weird about switching over the DEP-14
layout is that the "upstream" branch gets renamed to "upstream/latest"
and I don't know how to do that without deleting the (bare) "upstream"
branch.  Everything should be correct in Salsa for a new checkout, but
you might run into some git unhappiness when updating your local repo.

Cheers,
tony


signature.asc
Description: PGP signature

Bug#986418: Acknowledgement (libreoffice-impress: Impress cannot reduce table row size)

[Drew Parsons]

In fact this commit for 7.0.5 is more correct,
https://git.libreoffice.org/core/commit/51e4f716ea8416a1a8d90f8063a51ad130bd1743

Though it's essentially the same,

diff --git a/svx/source/table/tablelayouter.cxx 
b/svx/source/table/tablelayouter.cxx

index 2d0fc0f..ed54499 100644
--- a/svx/source/table/tablelayouter.cxx
+++ b/svx/source/table/tablelayouter.cxx

@@ -788,7 +788,7 @@ void TableLayouter::LayoutTableHeight( 
tools::Rectangle& rArea, bool bFit )

// Case 2: * Row has "Heigth" property
// * Calculated minimum heigth is bigger 
than Height propery value and
// * Row has not any text of any cell in 
edit mode in the row (means completely empty)
-if ((nMinHeight < nRowPropHeight && nRowPropHeight 
> 0 ) ||
+if ((nMinHeight < nRowPropHeight && nRowPropHeight 
> 0 && (bRowHasText || bRowHasCellInEditMode)) ||
(nMinHeight > nRowPropHeight && nRowPropHeight > 
0 && (!bRowHasText && !bRowHasCellInEditMode)))

{
nMinHeight = nRowPropHeight;

Bug#986417: system-information about kernel-resume

[Andi Glaeser mobil]

andrew@eb8440p:~$ sudo lspci -vn
00:00.0 0600: 8086:0044 (rev 02)
Subsystem: 103c:172a
Flags: bus master, fast devsel, latency 0
Capabilities: [e0] Vendor Specific Information: Len=0c 

00:02.0 0300: 8086:0046 (rev 02) (prog-if 00 [VGA controller])
Subsystem: 103c:172a
Flags: bus master, fast devsel, latency 0, IRQ 32
Memory at d000 (64-bit, non-prefetchable) [size=4M]
Memory at c000 (64-bit, prefetchable) [size=256M]
I/O ports at 5050 [size=8]
[virtual] Expansion ROM at 000c [disabled] [size=128K]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 2
Capabilities: [a4] PCI Advanced Features
Kernel driver in use: i915
Kernel modules: i915

00:16.0 0780: 8086:3b64 (rev 06)
Subsystem: 103c:172a
Flags: bus master, fast devsel, latency 0, IRQ 33
Memory at d4724000 (64-bit, non-prefetchable) [size=16]
Capabilities: [50] Power Management version 3
Capabilities: [8c] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: mei_me
Kernel modules: mei_me

00:19.0 0200: 8086:10ea (rev 05)
Subsystem: 103c:172a
Flags: bus master, fast devsel, latency 0, IRQ 30
Memory at d470 (32-bit, non-prefetchable) [size=128K]
Memory at d472a000 (32-bit, non-prefetchable) [size=4K]
I/O ports at 5020 [size=32]
Capabilities: [c8] Power Management version 2
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [e0] PCI Advanced Features
Kernel driver in use: e1000e
Kernel modules: e1000e

00:1a.0 0c03: 8086:3b3c (rev 05) (prog-if 20 [EHCI])
Subsystem: 103c:172a
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at d4729000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1b.0 0403: 8086:3b56 (rev 05)
Subsystem: 103c:172a
Flags: bus master, fast devsel, latency 0, IRQ 34
Memory at d472 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [100] Virtual Channel
Capabilities: [130] Root Complex Link
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 0604: 8086:3b42 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 27
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Memory behind bridge: d460-d46f
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: 103c:172a
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport

00:1c.1 0604: 8086:3b44 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 28
Bus: primary=00, secondary=02, subordinate=42, sec-latency=0
I/O behind bridge: 3000-4fff
Memory behind bridge: d060-d45f
Prefetchable memory behind bridge: d490-d4af
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: 103c:172a
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport

00:1c.3 0604: 8086:3b48 (rev 05) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 29
Bus: primary=00, secondary=43, subordinate=43, sec-latency=0
Memory behind bridge: d050-d05f
Capabilities: [40] Express Root Port (Slot+), MSI 00
Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [90] Subsystem: 103c:172a
Capabilities: [a0] Power Management version 2
Kernel driver in use: pcieport

00:1d.0 0c03: 8086:3b34 (rev 05) (prog-if 20 [EHCI])
Subsystem: 103c:172a
Flags: bus master, medium devsel, latency 0, IRQ 20
Memory at d4728000 (32-bit, non-prefetchable) [size=1K]
Capabilities: [50] Power Management version 2
Capabilities: [58] Debug port: BAR=1 offset=00a0
Capabilities: [98] PCI Advanced Features
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1e.0 0604: 8086:2448 (rev a5) (prog-if 01 [Subtractive decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=44, subordinate=45, sec-latency=64
I/O b

Bug#986418: libreoffice-impress: Impress cannot reduce table row size

[Drew Parsons]

Package: libreoffice-impress
Version: 1:7.0.4-3
Severity: important
Control: forwarded -1 https://bugs.documentfoundation.org/show_bug.cgi?id=139511
Control: tags -1 + patch bullseye

LibreOffice (7.0.4) cannot reduce the size of table rows in Impress.

Apparently this is a known bug, fixed upstream and fixed in 7.1.1,
https://bugs.documentfoundation.org/show_bug.cgi?id=139511

It's quite a serious bug in terms of usability of this part of the
package.  Can the patch be applied to 7.0.4 in unstable targetted for
inclusion in the bullseye stable release?

The patch applied to 7.1.1 is
https://git.libreoffice.org/core/+/edc5ea345446fc0ca484a9c854d65dc5c1a39793%5E%21

It is trivial:

diff --git a/svx/source/table/tablelayouter.cxx 
b/svx/source/table/tablelayouter.cxx
index 80d0a52..2d8de0c 100644
--- a/svx/source/table/tablelayouter.cxx
+++ b/svx/source/table/tablelayouter.cxx

@@ -789,7 +789,7 @@ void TableLayouter::LayoutTableHeight( tools::Rectangle& 
rArea, bool bFit )
// Case 2: * Row has "Height" property
// * Calculated minimum height is bigger than 
Height property value and
// * Row has not any text of any cell in edit 
mode in the row (means completely empty)
-if ((nMinHeight < nRowPropHeight && nRowPropHeight > 0 ) ||
+if ((nMinHeight < nRowPropHeight && nRowPropHeight > 0 && 
(bRowHasText || bRowHasCellInEditMode)) ||
(nMinHeight > nRowPropHeight && nRowPropHeight > 0 && 
(!bRowHasText && !bRowHasCellInEditMode)))
{
nMinHeight = nRowPropHeight;




-- Package-specific info:

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-5-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libreoffice-impress depends on:
ii  libc62.31-11
ii  libepoxy01.5.5-1
ii  libetonyek-0.1-1 0.1.9-4
ii  libgcc-s110.2.1-6
ii  libmwaw-0.3-30.3.17-1
ii  libodfgen-0.1-1  0.1.8-2
ii  libreoffice-common   1:7.0.4-3
ii  libreoffice-core 1:7.0.4-3
ii  libreoffice-draw 1:7.0.4-3
ii  librevenge-0.0-0 0.0.4-6+b1
ii  libstaroffice-0.0-0  0.0.7-1
ii  libstdc++6   10.2.1-6
ii  libuno-cppu3 1:7.0.4-3
ii  libuno-cppuhelpergcc3-3  1:7.0.4-3
ii  libuno-sal3  1:7.0.4-3
ii  libuno-salhelpergcc3-3   1:7.0.4-3
ii  ucf  3.0043
ii  uno-libs-private 1:7.0.4-3

libreoffice-impress recommends no packages.

Versions of packages libreoffice-impress suggests:
ii  bluez  5.55-3

Versions of packages libreoffice-core depends on:
ii  fontconfig  2.13.1-4.2
ii  fonts-opensymbol2:102.11+LibO7.0.4-3
ii  libboost-locale1.74.0   1.74.0-9
ii  libc6   2.31-11
ii  libcairo2   1.16.0-5
ii  libclucene-contribs1v5  2.3.3.4+dfsg-1+b1
ii  libclucene-core1v5  2.3.3.4+dfsg-1+b1
ii  libcmis-0.5-5v5 0.5.2-3
ii  libcups22.3.3op2-3
ii  libcurl3-gnutls 7.74.0-1.1
ii  libdbus-1-3 1.12.20-2
ii  libdconf1   0.38.0-2
ii  libeot0 0.01-5+b1
ii  libepoxy0   1.5.5-1
ii  libexpat1   2.2.10-2
ii  libexttextcat-2.0-0 3.4.5-1
ii  libfontconfig1  2.13.1-4.2
ii  libfreetype62.10.4+dfsg-1
ii  libgcc-s1   10.2.1-6
ii  libglib2.0-02.66.8-1
ii  libgpgmepp6 1.14.0-1+b2
ii  libgraphite2-3  1.3.14-1
ii  libgstreamer-plugins-base1.0-0  1.18.3-1
ii  libgstreamer1.0-0   1.18.3-1
ii  libharfbuzz-icu02.7.4-1
ii  libharfbuzz0b   2.7.4-1
ii  libhunspell-1.7-0   1.7.0-3
ii  libhyphen0  2.8.8-7
ii  libice6 2:1.0.10-1
ii  libicu6767.1-6
ii  libjpeg62-turbo 1:2.0.6-4
ii  liblcms2-2  2.12~rc1-2
ii  libldap-2.4-2   2.4.57+dfsg-2
ii  libmythes-1.2-0 2:1.2.4-3+b1
ii  libneon27-gnutls0.31.2-1
ii  libnspr42:4.29-1
ii  libnss3 2:3.63-1
ii  libnumbertext-1.0-0 1.0.7-1
ii  liborcus-0.16-0 0.16.1-3+b2
ii  liborcus-parser-0.16-0  0.16.1-3+b2
ii  libpn

Bug#939763: sphinxsearch: Still maintained (same version since stretch)?

[Thijs Kinkhorst]

severity 939763 serious
thanks

Hi,

Salvatore Bonaccorso wrote:
> Is sphinxsearch still of use or should it be removed from unstable and
> not included in bullseye?

I'm raising this to serious because I think the situation of the
sphinxsearch package is not good and we would need to explicitly want to
decide to _do_ ship the package in bullseye.

A summary of the issues: the package is the same version since stretch (no
uploads since 2017). It has several important issues, most notably that it
crashes everytime you restart it (e.g. after logrotate). This bug has been
raised two years ago without any maintainer comment.

Fixing the package is also unlikely since upstream has gone closed source.
So even if there's interest in fixing this, it would be by packaging the
free alternative (fork) that has been suggested in this thread.


Kind regards,
Thijs

Bug#985942: kodi: Cannot shutdown computer from kodi

[Libor Klepáč]

Hi,
after lots of debuging with Vasyl Gello (thanks!), it seems, everything
is ok on kodi package and system side, problem is probably with add-on
"Skin helper service" or "Embuary helper" - after disabling those two,
power related commands started to work

I will investigate more

Thanks,
Libor

Bug#986417: linux-image-5.10.0-5-amd64: resuming/waking up from hibernation is unreliable

[andrew glaeser]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: src:linux
Version: 5.10.24-1
Severity: normal
X-Debbugs-Cc: b...@irregulaire.info

Dear Maintainer,


The issue was already reported as bug #953305, and correctly marked as done,
because it mainly referred to to the stable version of linux-image. I have
tried the backported linux-image 5.10.0-0.bpo.4-amd64 and the issue seemed to
be resolved, but it turned out instead of defunct wakeup/resume, now the
functionality is unreliable, failing now and then only, so to speak.

I'll give you additional information from the mobile device, that is affected
in a separate E-Mail.



- -- Package-specific info:
** Version:
Linux version 5.10.0-5-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP
Debian 5.10.24-1 (2021-03-19)

** Command line:
BOOT_IMAGE=/@rootfs/boot/vmlinuz-5.10.0-5-amd64
root=UUID=ce6a1442-b441-48a0-99d8-9d6e071cfdf2 ro rootflags=subvol=@rootfs
quiet

** Not tainted

** Kernel log:
[5.234418] systemd[1]: Starting Journal Service...
[5.235929] systemd[1]: Starting Load Kernel Modules...
[5.237275] systemd[1]: Starting Remount Root and Kernel File Systems...
[5.238478] systemd[1]: Starting Coldplug All udev Devices...
[5.247591] systemd[1]: Mounted Huge Pages File System.
[5.247854] systemd[1]: Mounted POSIX Message Queue File System.
[5.248158] systemd[1]: Mounted Kernel Debug File System.
[5.248416] systemd[1]: Mounted Kernel Trace File System.
[5.248877] systemd[1]: Finished Create list of static device nodes for
the current kernel. [5.249410] systemd[1]: modprobe@configfs.service:
Succeeded. [5.249734] systemd[1]: Finished Load Kernel Module configfs.
[5.266332] fuse: init (API version 7.32)
[5.275108] systemd[1]: modprobe@drm.service: Succeeded.
[5.280636] systemd[1]: Finished Load Kernel Module drm.
[5.282298] systemd[1]: modprobe@fuse.service: Succeeded.
[5.283652] systemd[1]: Finished Load Kernel Module fuse.
[5.285723] BTRFS info (device sda2): disk space caching is enabled
[5.293545] systemd[1]: Finished Remount Root and Kernel File Systems.
[5.295419] systemd[1]: Mounting FUSE Control File System...
[5.302393] systemd[1]: Mounting Kernel Configuration File System...
[5.307088] systemd[1]: Condition check resulted in Rebuild Hardware
Database being skipped. [5.307166] systemd[1]: Condition check resulted
in Platform Persistent Storage Archival being skipped. [5.308259]
systemd[1]: Starting Load/Save Random Seed... [5.309487] systemd[1]:
Starting Create System Users... [5.311563] systemd[1]: Mounted FUSE
Control File System. [5.314809] systemd[1]: Mounted Kernel Configuration
File System. [5.319069] lp: driver loaded but no devices found
[5.351115] ppdev: user-space parallel port driver
[5.363532] systemd[1]: Finished Create System Users.
[5.364606] systemd[1]: Starting Create Static Device Nodes in /dev...
[5.389610] RPC: Registered named UNIX socket transport module.
[5.389613] RPC: Registered udp transport module.
[5.389614] RPC: Registered tcp transport module.
[5.389615] RPC: Registered tcp NFSv4.1 backchannel transport module.
[5.389977] systemd[1]: Finished Load Kernel Modules.
[5.391138] systemd[1]: Starting Apply Kernel Variables...
[5.393399] systemd[1]: Mounted RPC Pipe File System.
[5.415355] systemd[1]: Finished Apply Kernel Variables.
[5.422765] systemd[1]: Finished Create Static Device Nodes in /dev.
[5.424727] systemd[1]: Starting Rule-based Manager for Device Events and
Files... [5.477409] systemd[1]: Finished Coldplug All udev Devices.
[5.478637] systemd[1]: Starting Helper to synchronize boot up for
ifupdown... [5.493104] systemd[1]: Finished Helper to synchronize boot up
for ifupdown. [5.529036] systemd[1]: Started Journal Service.
[5.556065] systemd-journald[239]: Received client request to flush
runtime journal. [5.696175] acpi_cpufreq: overriding BIOS provided _PSD
data [5.792725] sd 1:0:0:0: Attached scsi generic sg0 type 0
[5.860754] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
[5.860863] sp5100-tco sp5100-tco: Using 0xfed80b00 for watchdog MMIO
address [5.867697] input: PC Speaker
as /devices/platform/pcspkr/input/input3 [5.872134] sp5100-tco
sp5100-tco: initialized. heartbeat=60 sec (nowayout=0) [5.879730] pstore:
Using crash dump compression: deflate [5.879741] pstore: Registered efi
as persistent store backend [5.919649] cryptd: max_cpu_qlen set to 1000
[6.006870] AVX version of gcm_enc/dec engaged.
[6.006873] AES CTR mode by8 optimization enabled
[6.021847] snd_hda_intel :00:01.1: enabling device ( -> 0002)
[6.021978] snd_hda_intel :00:01.1: Force to non-snoop mode
[6.053767] input: HDA ATI HDMI HDMI/DP,pcm=3
as /devices/pci:00/:00:01.1/sound/card0/input4 [6.096798] Addi

Bug#939579: Your software is still bugged !?!?

[Chris Hofstaedtler]

Hi,

* pham...@bluewin.ch  [210405 14:21]:
> It will soon be 1 year and a half that your software is bugged, would you be 
> kind enough to do something to make it finally work correctly ? 
> Regards.

This form of communication does not help. Right now there is no real
maintainer for gdebi, so no one is really looking after this package.
If you want this bug fixed, please provide more details on the crash
and the workarounds that have been tried.
The python backtrace might be useful, for example.

For the next person wondering, the patch applied by MX Linux is
attached (basically runs gdebi under gksu, probably side-stepping
some permission issue).

Chris

diff -Nru gdebi-0.9.5.7+nmu4/data/gdebi.applications gdebi-0.9.5.7+nmu3+mx19/data/gdebi.applications
--- gdebi-0.9.5.7+nmu4/data/gdebi.applications	2021-01-13 18:45:14.0 +
+++ gdebi-0.9.5.7+nmu3+mx19/data/gdebi.applications	2019-07-14 01:36:50.0 +
@@ -1,6 +1,6 @@
 
 gdebi
-	command=gdebi-gtk
+	command=gksu gdebi-gtk
 	name=Install Package (gdebi)
 	can_open_multiple_files=false
 	expects_uris=false
diff -Nru gdebi-0.9.5.7+nmu4/data/gdebi.desktop.in gdebi-0.9.5.7+nmu3+mx19/data/gdebi.desktop.in
--- gdebi-0.9.5.7+nmu4/data/gdebi.desktop.in	2021-01-13 18:45:14.0 +
+++ gdebi-0.9.5.7+nmu3+mx19/data/gdebi.desktop.in	2019-07-14 01:36:50.0 +
@@ -2,7 +2,7 @@
 _Name=GDebi Package Installer
 _GenericName=Package Installer
 _Comment=Install and view software packages
-Exec=gdebi-gtk %f
+Exec=gksu gdebi-gtk %f
 Icon=gnome-mime-application-x-deb
 Terminal=false
 Type=Application
diff -Nru gdebi-0.9.5.7+nmu4/data/gdebi-kde.desktop.in gdebi-0.9.5.7+nmu3+mx19/data/gdebi-kde.desktop.in
--- gdebi-0.9.5.7+nmu4/data/gdebi-kde.desktop.in	2021-01-13 18:45:14.0 +
+++ gdebi-0.9.5.7+nmu3+mx19/data/gdebi-kde.desktop.in	2019-07-14 01:36:50.0 +
@@ -2,7 +2,7 @@
 _Name=GDebi Package Installer
 _GenericName=Package Installer
 _Comment=Install and view software packages
-Exec=gdebi-kde
+Exec=gksu gdebi-kde
 Icon=application-x-deb
 Terminal=false
 Type=Application

Bug#986416: pam: Updated debconf PO translation to Romanian

[Andrei POPESCU]

Package: src:pam
Version: 1.4.0-6
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

Please find attached updated Romanian translation for the debconf 
template.

Kind regards,
Andrei

-- System Information:
Debian Release: 10.9
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: arm64 (aarch64)

Kernel: Linux 3.18.0-12-ARCH (SMP w/4 CPU cores; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=ro_RO.UTF-8, LC_CTYPE=ro_RO.UTF-8 (charmap=UTF-8), 
LANGUAGE=ro_RO.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
# Romanian translation of pam debconf templates
# Debconf questions for the Linux-PAM package.
# Copyright (C) 2007 Steve Langasek 
# This file is distributed under the same license as the pam package.
#
# Igor Stirbu , 2008.
# Eddy Petrișor , 2009.
msgid ""
msgstr ""
"Project-Id-Version: pam 1.0.1-7\n"
"Report-Msgid-Bugs-To: p...@packages.debian.org\n"
"POT-Creation-Date: 2021-02-26 10:32-0500\n"
"PO-Revision-Date: 2021-04-05 16:44+0300\n"
"Last-Translator: Andrei POPESCU \n"
"Language-Team: Romanian \n"
"Language: ro\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.4\n"
"Plural-Forms:  nplurals=3; plural=n==1 ? 0 : (n==0 || (n%100 > 0 && n%100 < "
"20)) ? 1 : 2;\n"

#. Type: string
#. Description
#: ../libpam0g.templates:1001
msgid "Services to restart for PAM library upgrade:"
msgstr "Serviciile repornite la actualizarea bibliotecii PAM:"

#. Type: string
#. Description
#: ../libpam0g.templates:1001
msgid ""
"Most services that use PAM need to be restarted to use modules built for "
"this new version of libpam.  Please review the following space-separated "
"list of  services to be restarted now, and correct it if needed."
msgstr ""
"Majoritatea serviciilor ce folosesc PAM trebuie repornite pentru a folosi "
"modulele pentru noua versiune de libpam. Verificați și ajustați după caz "
"lista următoare (separată prin spațiu) cu servicii care trebuie repornite."

#. Type: error
#. Description
#: ../libpam0g.templates:2001
msgid "Display manager must be restarted manually"
msgstr "Administratorul de ecran trebuie repornit manual"

#. Type: error
#. Description
#: ../libpam0g.templates:2001
msgid ""
"The wdm and xdm display managers require a restart for the new version of "
"libpam, but there are X login sessions active on your system that would be "
"terminated by this restart.  You will therefore need to restart these "
"services by hand before further X logins will be possible."
msgstr ""
"Administratorii de ecran wdm și xdm trebuie reporniți pentru ca să "
"folosească noua versiune de libpam, dar sunt sesiuni active de X pe sistemul "
"dumneavoastră care ar fi oprite odată cu această repornire. Drept urmare, "
"trebuie să reporniți manual aceste servicii înainte ca autentificările X "
"ulterioare să fie posibile."

#. Type: error
#. Description
#: ../libpam0g.templates:3001
msgid "Failure restarting some services for PAM upgrade"
msgstr "Eșec la repornirea unor servicii la actualizarea PAM"

#. Type: error
#. Description
#: ../libpam0g.templates:3001
msgid ""
"The following services could not be restarted for the PAM library upgrade:"
msgstr ""
"Următoarele servicii nu au putut fi repornite la actualizarea bibliotecii "
"PAM:"

#. Type: error
#. Description
#: ../libpam0g.templates:3001
msgid ""
"You will need to start these manually by running '/etc/init.d/ "
"start'."
msgstr ""
"Trebuie să reporniți manual aceste servicii rulând „/etc/init.d/ "
"start”"

#. Type: boolean
#. Description
#: ../libpam0g.templates:4001
msgid "Restart services during package upgrades without asking?"
msgstr ""
"Să se repornească serviciile fără confirmare în timpul unei actualizări?"

#. Type: boolean
#. Description
#: ../libpam0g.templates:4001
msgid ""
"There are services installed on your system which need to be restarted when "
"certain libraries, such as libpam, libc, and libssl, are upgraded. Since "
"these restarts may cause interruptions of service for the system, you will "
"normally be prompted on each upgrade for the list of services you wish to "
"restart.  You can choose this option to avoid being prompted; instead, all "
"necessary restarts will be done for you automatically so you can avoid being "
"asked questions on each library upgrade."
msgstr ""
"Pe acest sistem sunt instalate servicii care trebuie repornite atunci când "
"anumite biblioteci, cum ar fi libpam, libc și libssl sunt actualizate. "
"Deoarece aceste reporniri pot cauza întreruperi în furnizarea serviciului în "
"mod normal se solicită confirmarea listei de servicii pe care doriți să le "
"reporniți la fiecare actualizare. Puteți alege această opțiune pentru a "
"evita confirmarea. În schimb toate repornirile necesare vor fi executate "
"automat pentru a evita întrebările la fiecare actualizare de biblioteci."

#. Type: title
#. 

Bug#986400: lintian: false positive about permissions for read-only GNAT .ali files

[Nicolas Boulenguez]

> Thanks! Why are ADA libraries installed with non-standard permissions,
> please? A quick online search turned up only this reasoning. [1] Why
> is that not a bug in GNAT, please?

Why is that a bug in the first place, please?

In GNAT, the compiler also deals with dependencies and rebuild order.
The .ali files contain the dependency information required to detect
if a .o is more recent than the closure of all sources it depends
upon, or if it should be rebuilt.
By convention, a read-only .ali file tells GNAT to fail if the .o is
obsolete or unavailable, instead of attempting to rebuild.  This is
recommended for packaged libraries (the .so or .a are available but
not the .o files).
This convention may seem bizarre according to modern standards, but it
has been in use for 25 years, so Adacore would probably need a
compelling reason to break it.

For more Debian context:
https://people.debian.org/~lbrenta/debian-ada-policy.html#Ada-Library-Information-files-2

Bug#986415: Updating the auto-07p Uploaders list

[Pierre-Elliott Bécue]

Source: auto-07p
Version: 0.9.1+dfsg-7 0.9.2+dfsg-3
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Sergey B Kirpichev  has retired, so can't work on
the auto-07p package anymore (at least with this address).

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#986413: O: parser -- Parser 3, HTML-embedded scripting language (metapackage)

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of parser, Sergey B Kirpichev ,
has retired.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: parser
Binary: parser3, parser3-common, parser3-cgi, libapache2-mod-parser3, 
parser3-dev
Version: 3.4.5-4
Maintainer: Sergey B Kirpichev 
Build-Depends: debhelper (>= 9), g++ (>= 4:4.4.5), libltdl-dev, libgc-dev, 
libpcre3-dev, libxml2-dev, libxslt1-dev, dh-apache2, apache2-dev (>= 2.4.2-1~), 
dh-autoreconf
Architecture: any all
Standards-Version: 4.1.4
Format: 3.0 (quilt)
Files:
 207c5fee45dde65298d8e0cfe4bc47f2 2182 parser_3.4.5-4.dsc
 6cc4fac678edbb843e3aecd29754eedc 1468271 parser_3.4.5.orig.tar.gz
 bcead1de513d37aaf4f1a8ae8ddd6cf5 45192 parser_3.4.5-4.debian.tar.xz
Vcs-Browser: https://salsa.debian.org/sk-guest/parser
Vcs-Git: https://salsa.debian.org/sk-guest/parser.git
Checksums-Sha256:
 b11b5143151daf640b7ae1b13825de770d9fc6303faaea4b3190f088bc5d7d1b 2182 
parser_3.4.5-4.dsc
 dc73a437cbbd68ecd9becc4ad192b87f2679f0b129f57c98e8bd778e123e0edb 1468271 
parser_3.4.5.orig.tar.gz
 513c7bfa4b78bf97c39b0f3bc6178f294f6f418a17d5b6b32f3ae2f3dd080825 45192 
parser_3.4.5-4.debian.tar.xz
Homepage: http://www.parser.ru/en/
Package-List: 
 libapache2-mod-parser3 deb httpd optional arch=any
 parser3 deb web optional arch=all
 parser3-cgi deb web optional arch=any
 parser3-common deb web optional arch=any
 parser3-dev deb devel optional arch=any
Directory: pool/main/p/parser
Priority: source
Section: web

Package: parser
Binary: parser3, parser3-common, parser3-cgi, libapache2-mod-parser3, 
parser3-dev
Version: 3.4.6-2
Maintainer: Sergey B Kirpichev 
Build-Depends: debhelper-compat (= 13), g++ (>= 4:4.4.5), libltdl-dev, 
libgc-dev, libpcre3-dev, libxml2-dev, libxslt1-dev, dh-apache2, apache2-dev (>= 
2.4.2-1~), dh-autoreconf
Architecture: any all
Standards-Version: 4.5.1
Format: 3.0 (quilt)
Files:
 a82278a9424e89623295599d97464323 2189 parser_3.4.6-2.dsc
 f59498398918ccf0b07d5cabb278ded9 1519387 parser_3.4.6.orig.tar.gz
 ffd16b1c31d8ee436b6e846f697709dc 43492 parser_3.4.6-2.debian.tar.xz
Vcs-Browser: https://salsa.debian.org/sk-guest/parser
Vcs-Git: https://salsa.debian.org/sk-guest/parser.git
Checksums-Sha256:
 21f47fa2fce6be23c231d8f0c0754b497e1235c8426eb9643ef03929a08d1590 2189 
parser_3.4.6-2.dsc
 b326b403d0a9e6d14aa10f927b0ed9ccaf44d295f1495c3f9966e9463ee640ae 1519387 
parser_3.4.6.orig.tar.gz
 9f5f38999ce04051ee2a97f08e05aead2d68a65d3649fe78e9bf9348ca09de57 43492 
parser_3.4.6-2.debian.tar.xz
Homepage: http://www.parser.ru/en/
Package-List: 
 libapache2-mod-parser3 deb httpd optional arch=any
 parser3 deb web optional arch=all
 parser3-cgi deb web optional arch=any
 parser3-common deb web optional arch=all
 parser3-dev deb devel optional arch=all
Directory: pool/main/p/parser
Priority: source
Section: web

Package: parser3
Source: parser
Version: 3.4.6-2
Installed-Size: 6
Maintainer: Sergey B Kirpichev 
Architecture: all
Depends: parser3-cgi (>= 3.4.6-2), parser3-common (>= 3.4.6-2)
Description-en: Parser 3, HTML-embedded scripting language (metapackage)
 This is a metapackage that, when installed, guarantees that you have
 at least one of the server-side versions of the Parser 3 interpreter
 installed. Removing this package won't remove Parser 3 from your
 system, but it may remove other packages that depend on this one.
 .
 Parser 3 - simple and convenient object-oriented language which
 allows creating good sites in short time.
 .
 Available features:
  * XML, XSL, XPath and DOM support
  * Available in documented source code
  * Uniformed database support
  * Support of object-oriented programmers
  * Detailed language documentation (160 pages!)
  * UTF-8 support
Description-md5: 281433133b551d8a2f944ae5ae78b83f
Homepage: http://www.parser.ru/en/
Tag: devel::interpreter, devel::runtime, implemented-in::c++,
 role::metapackage, role::program, web::scripting
Section: web
Priority: optional
Filename: pool/main/p/parser/parser3_3.4.6-2_all.deb
Size: 1220
MD5sum: 3d663539dd198c3b9a26d2d7c5fcfe68
SHA256: 7166699cec20b8013e56b8fe05257fd596a609afeb9bbcbe8f8f1b09aaa54aad

Package: parser3
Source: parser
Version: 3.4.5-4
Installed-Size: 6
Maintainer: Sergey B Kirpichev 
Architecture: all
Depends: parser3-cgi (>= 3.4.5-4), parser3-common (>= 3.4.5-4)
Description-en: Parser 3, HTML-embedded scripting language (metapackage)
 This is a metapackage that, when installed, guarantees that you have
 at least one of the server-side versions of the Parser 3 interpreter
 installed. Removing this package won't remove Parser 3 from your
 system, but it may remove other packages that depend on this one.
 .
 Parser 3 - simple and convenient object-oriented language which
 allows c

Bug#986414: O: parser-mysql -- MySQL driver for Parser 3

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of parser-mysql, Sergey B Kirpichev 
,
has retired.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: parser-mysql
Binary: parser3-mysql
Version: 10.7-4
Maintainer: Sergey B Kirpichev 
Build-Depends: debhelper (>= 10), parser3-dev (>= 3.4.2), 
default-libmysqlclient-dev, libltdl-dev
Architecture: any
Standards-Version: 4.3.0
Format: 3.0 (quilt)
Files:
 78400eb8ec74b49dee018af54920e44b 1933 parser-mysql_10.7-4.dsc
 c10d412cf1e2718698c63728153a83fc 630420 parser-mysql_10.7.orig.tar.gz
 3638e5e55226c43451bbe3ebdc079797 3664 parser-mysql_10.7-4.debian.tar.xz
Vcs-Browser: https://salsa.debian.org/sk-guest/parser-mysql
Vcs-Git: https://salsa.debian.org/sk-guest/parser-mysql.git
Checksums-Sha256:
 f66d102e82c936b80ba69047702046da438fc3a2f40f5d25754999ed408554ca 1933 
parser-mysql_10.7-4.dsc
 aafd1c5b0b1f6c0b5f1297c75cd471e19996d63e4719108baf4b548bad0ad88c 630420 
parser-mysql_10.7.orig.tar.gz
 518bfd6c378d181bc4cc3fdbde9b2d1ce5630cf24fcaf8dfcb782bf827e7ea37 3664 
parser-mysql_10.7-4.debian.tar.xz
Homepage: http://www.parser.ru/en/download/src/
Package-List: 
 parser3-mysql deb web optional arch=any
Directory: pool/main/p/parser-mysql
Priority: source
Section: web

Package: parser-mysql
Binary: parser3-mysql
Version: 10.8-3
Maintainer: Sergey B Kirpichev 
Build-Depends: debhelper-compat (= 13), parser3-dev (>= 3.4.2), 
libmariadb-dev-compat, libltdl-dev
Architecture: any
Standards-Version: 4.5.1
Format: 3.0 (quilt)
Files:
 8563096afdc8c48d1a7b1c3618efdd5b 1934 parser-mysql_10.8-3.dsc
 6acf267f83fe12f46aca012860f400cb 631626 parser-mysql_10.8.orig.tar.gz
 56550d2d238f1cc56d657ad7a16f6a62 3560 parser-mysql_10.8-3.debian.tar.xz
Vcs-Browser: https://salsa.debian.org/sk-guest/parser-mysql
Vcs-Git: https://salsa.debian.org/sk-guest/parser-mysql.git
Checksums-Sha256:
 1b8c59f2edf78f8f1a46c38d498c384851c667836b3d27dec269a20244fb6ad1 1934 
parser-mysql_10.8-3.dsc
 18ace4dccd3e10f1ff18e8cbc83a99d93239642e332b69482237fc2f3d244bc4 631626 
parser-mysql_10.8.orig.tar.gz
 39294ba70f4bee86a85048eab8d851aa5472c8ad046d2ff7f889a5dd2f0e9f9c 3560 
parser-mysql_10.8-3.debian.tar.xz
Homepage: http://www.parser.ru/en/download/src/
Package-List: 
 parser3-mysql deb web optional arch=any
Directory: pool/main/p/parser-mysql
Priority: source
Section: web

Package: parser3-mysql
Source: parser-mysql
Version: 10.8-3
Installed-Size: 46
Maintainer: Sergey B Kirpichev 
Architecture: amd64
Depends: libc6 (>= 2.14), libltdl7 (>= 2.4.6), libstdc++6 (>= 4.1.1), 
parser3-common (>= 3.3.0), libmariadb-dev-compat
Description-en: MySQL driver for Parser 3
 This package provides driver for MySQL database connections directly
 from Parser 3 scripts.
 .
 Parser 3 - simple and convenient object-oriented language which
 allows creating good sites in short time.
 .
 Available features:
  * XML, XSL, XPath and DOM support
  * Available in documented source code
  * Uniformed database support
  * Support of object-oriented programmers
  * Detailed language documentation (160 pages!)
  * UTF-8 support
Description-md5: d75b039dd00d2183a76eef0a76a72fcc
Homepage: http://www.parser.ru/en/download/src/
Tag: devel::interpreter, implemented-in::c++, role::plugin
Section: web
Priority: optional
Filename: pool/main/p/parser-mysql/parser3-mysql_10.8-3_amd64.deb
Size: 15556
MD5sum: 470fcfc2ddafb083d6fc9a21ca37d409
SHA256: 46f40fb4261293f0b94414130352559c4053e4d31975f4bb6930b336aa8090f6

Package: parser3-mysql
Source: parser-mysql
Version: 10.7-4
Installed-Size: 42
Maintainer: Sergey B Kirpichev 
Architecture: amd64
Depends: libc6 (>= 2.14), libgcc1 (>= 1:3.0), libltdl7 (>= 2.4.6), libstdc++6 
(>= 5), parser3-common (>= 3.3.0)
Description-en: MySQL driver for Parser 3
 This package provides driver for MySQL database connections directly
 from Parser 3 scripts.
 .
 Parser 3 - simple and convenient object-oriented language which
 allows creating good sites in short time.
 .
 Available features:
  * XML, XSL, XPath and DOM support
  * Available in documented source code
  * Uniformed database support
  * Support of object-oriented programmers
  * Detailed language documentation (160 pages!)
  * UTF-8 support
Description-md5: d75b039dd00d2183a76eef0a76a72fcc
Homepage: http://www.parser.ru/en/download/src/
Tag: devel::interpreter, implemented-in::c++, role::plugin
Section: web
Priority: optional
Filename: pool/main/p/parser-mysql/parser3-mysql_10.7-4_amd64.deb
Size: 14708
MD5sum: 61eb96b63404ca241b40f0d338135da1
SHA256: 565ba83707cbe79acb4861afe149f10d854c51934745dcf1cdf9411d83142682

Package: parser3-mysql
Source: parser-mysql
Version: 10.8-3
Installed-Size: 46
Maintainer: Sergey B Kirpichev 
Architecture: amd64
Depends:

Bug#986412: O: monit -- utility for monitoring and managing daemons or similar programs

[Pierre-Elliott Bécue]

Package: wnpp

The current maintainer of monit, Sergey B Kirpichev ,
has retired.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: monit
Binary: monit
Version: 1:5.27.1-1~bpo10+1
Maintainer: Sergey B Kirpichev 
Build-Depends: debhelper-compat (= 13), libssl-dev, zlib1g-dev, libpam-dev, 
libkvm-dev [kfreebsd-any], libdevstat-dev [kfreebsd-any]
Architecture: any
Standards-Version: 4.5.0
Format: 3.0 (quilt)
Vcs-Browser: https://salsa.debian.org/sk-guest/monit
Vcs-Git: https://salsa.debian.org/sk-guest/monit.git
Checksums-Sha256:
 2ac68e746694e08048a6c2a152412728fad90c04031f21df0620585faf61827f 1933 
monit_5.27.1-1~bpo10+1.dsc
 f57408d16185687513a3c4eb3f2bb72eef76331ac16210e9652e846e5c84ed51 1459360 
monit_5.27.1.orig.tar.gz
 adfcf3211496067424710c26038f4099fb259f70fac6539c0df72d4dc85a058a 29252 
monit_5.27.1-1~bpo10+1.debian.tar.xz
Homepage: https://mmonit.com/monit/
Package-List: 
 monit deb admin optional arch=any
Directory: pool/main/m/monit
Priority: extra
Section: misc

Package: monit
Binary: monit
Version: 1:5.27.2-1
Maintainer: Sergey B Kirpichev 
Build-Depends: debhelper-compat (= 13), libssl-dev, zlib1g-dev, libpam-dev, 
libkvm-dev [kfreebsd-any], libdevstat-dev [kfreebsd-any]
Architecture: any
Standards-Version: 4.5.1
Format: 3.0 (quilt)
Files:
 2946aafbcbf6ca261bbe11ee25141010 1901 monit_5.27.2-1.dsc
 13a0804dae18ef08198c3ace72f9dd60 1463790 monit_5.27.2.orig.tar.gz
 0e22194de932dc02ddd5a838e4f148ac 29184 monit_5.27.2-1.debian.tar.xz
Vcs-Browser: https://salsa.debian.org/sk-guest/monit
Vcs-Git: https://salsa.debian.org/sk-guest/monit.git
Checksums-Sha256:
 8564e8a3d9b7118c4263d95f60e52c62b03e1ea1a2455cc90ee6c43ff34536b5 1901 
monit_5.27.2-1.dsc
 d8809c78d5dc1ed7a7ba32a5a55c5114855132cc4da4805f8d3aaf8cf46eaa4c 1463790 
monit_5.27.2.orig.tar.gz
 8331edb7e2136029bf04d6ff7df8d6d3315c12a1ae1ef998db4d910e36d8693e 29184 
monit_5.27.2-1.debian.tar.xz
Homepage: https://mmonit.com/monit/
Package-List: 
 monit deb admin optional arch=any
Directory: pool/main/m/monit
Priority: source
Section: admin

Package: monit
Version: 1:5.27.2-1
Installed-Size: 999
Maintainer: Sergey B Kirpichev 
Architecture: amd64
Depends: libc6 (>= 2.27), libcrypt1 (>= 1:4.1.0), libpam0g (>= 0.99.7.1), 
libssl1.1 (>= 1.1.0), zlib1g (>= 1:1.2.0), lsb-base (>= 3.2-13)
Pre-Depends: init-system-helpers (>= 1.54~)
Suggests: default-mta | postfix | mail-transport-agent, sysvinit-core
Description-en: utility for monitoring and managing daemons or similar programs
 monit is a utility for monitoring and managing daemons or similar
 programs running on a Unix system. It will start specified programs
 if they are not running and restart programs not responding.
 .
 monit supports:
  * Daemon mode - poll programs at a specified interval
  * Monitoring modes - active, passive or manual
  * Start, stop and restart of programs
  * Group and manage groups of programs
  * Process dependency definition
  * Logging to syslog or own logfile
  * Configuration - comprehensive controlfile
  * Runtime and TCP/IP port checking (tcp and udp)
  * SSL support for port checking
  * Unix domain socket checking
  * Process status and process timeout
  * Process cpu usage
  * Process memory usage
  * Process zombie check
  * Check the systems load average
  * Check a file or directory timestamp
  * Alert, stop or restart a process based on its characteristics
  * MD5 checksum for programs started and stopped by monit
  * Alert notification for program timeout, restart, checksum, stop
resource and timestamp error
  * Flexible and customizable email alert messages
  * Protocol verification. HTTP, FTP, SMTP, POP, IMAP, NNTP, SSH, DWP,
LDAPv2 and LDAPv3
  * An http interface with optional SSL support to make monit
accessible from a webbrowser
Description-md5: 2230ee5609e2789db9ac60b0d3fbac89
Homepage: https://mmonit.com/monit/
Tag: admin::monitoring, implemented-in::c, interface::daemon,
 network::hiavailability, network::server, role::program, use::monitor,
 works-with::software:running
Section: admin
Priority: optional
Filename: pool/main/m/monit/monit_5.27.2-1_amd64.deb
Size: 347432
MD5sum: 295458042a012fed7e8ee752d6a8da60
SHA256: 768253cc80823fc098dd8d862a1643283d6700469bbc9439db35579cc435322d

Package: monit
Version: 1:5.27.1-1~bpo10+1
Installed-Size: 995
Maintainer: Sergey B Kirpichev 
Architecture: amd64
Depends: libc6 (>= 2.27), libpam0g (>= 0.99.7.1), libssl1.1 (>= 1.1.0), zlib1g 
(>= 1:1.2.0), lsb-base (>= 3.2-13)
Pre-Depends: init-system-helpers (>= 1.54~)
Suggests: default-mta | postfix | mail-transport-agent, sysvinit-core
Description-en: utility for monitoring and managing daemons or similar programs
 monit is a utility for

Bug#986410: autopkg tests don't run with the same dependencies as during the build

[Andreas Tille]

Hi Matthias,

On Mon, Apr 05, 2021 at 02:46:41PM +0200, Matthias Klose wrote:
> The autopkg tests don't run with the same dependencies as during the build. 
> Just
> noticed because the python3-renderpm dependency seems to be necessary with the
> reportlab package from experimental.
> 
> But in general, please run the autopkg tests with the same packages as done
> during the build.

Could you please be more verbose.  The Build-Depends and Depends string
do not do any specific version specification.  Python3-reportlab was
added to Depends since it is really needed while python3-renderpm is
fine as "Suggests".  Which change would you recommend to solve that bug?

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#986411: unblock: pristine-lfs/20210404.0-1

[Andrej Shadura]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Please unblock package pristine-lfs

[ Reason ]
Not knowing that pristine-lfs is considered a key package, I made
changes upstream and uploaded a new release into Debian, fixing a few
bugs and improving the exported API to make the future integration
with git-buildpackage easier.

[ Impact ]
The direct impact in the event the unblock is not granted is low,
since the new features aren’t used yet and the bugs have been previously
worked around specifically in Debian bullseye.

On the other hand, for the outlined reasons the impact on unblocking
will also be very low.

[ Tests ]
- - There’s a test of tests running upstream on four Python releases (3.7,
  3.8, 3.9 and 3.10-rc) and in Debian on the current Python release at
  build time; these tests cover all features but test them directly in
  Python
- - The Debian package ships autopkgtests testing some of the basic
  features through the command-line interface.
- - The upstream Ci runs mypy static type checks.

[ Risks ]
The changes are not trivial but OTOH not big and covered by tests; the
overall test coverage has increased since the last upload, hence the
risks of accepting this package into bullseye should be relatively low.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

unblock pristine-lfs/20210404.0-1


-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQSD3NF/RLIsyDZW7aHoRGtKyMdyYQUCYGsP6AAKCRDoRGtKyMdy
Yc+rAQCsmONKT1dDAIwolvhF5uMJXtR9KiqIOyQi1DSosoJ1ZgEA+bf359mV6UDQ
+g2N6APILtvME0Agpz62ZKDz4YqI6wo=
=5H1H
-END PGP SIGNATURE-
diff --git a/PKG-INFO b/PKG-INFO
index 8db2f11..5b3e484 100644
--- a/PKG-INFO
+++ b/PKG-INFO
@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: pristine-lfs
-Version: 20210222.0
+Version: 20210404.0
 Summary: a pristine-tar replacement that works with Git LFS
 Home-page: https://salsa.debian.org/pristine-lfs-team/pristine-lfs
 Author: Andrej Shadura
diff --git a/debian/changelog b/debian/changelog
index 9804ad5..1afd619 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+pristine-lfs (20210404.0-1) unstable; urgency=medium
+
+  * New upstream release.
+
+ -- Andrej Shadura   Sun, 04 Apr 2021 22:15:42 
+0200
+
 pristine-lfs (20210222.0-1) unstable; urgency=medium
 
   * New upstream release.
diff --git a/pristine_lfs.egg-info/PKG-INFO b/pristine_lfs.egg-info/PKG-INFO
index 8db2f11..5b3e484 100644
--- a/pristine_lfs.egg-info/PKG-INFO
+++ b/pristine_lfs.egg-info/PKG-INFO
@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: pristine-lfs
-Version: 20210222.0
+Version: 20210404.0
 Summary: a pristine-tar replacement that works with Git LFS
 Home-page: https://salsa.debian.org/pristine-lfs-team/pristine-lfs
 Author: Andrej Shadura
diff --git a/pristine_lfs.egg-info/SOURCES.txt 
b/pristine_lfs.egg-info/SOURCES.txt
index 70a9467..2f79c38 100644
--- a/pristine_lfs.egg-info/SOURCES.txt
+++ b/pristine_lfs.egg-info/SOURCES.txt
@@ -6,8 +6,10 @@ pristine-lfs.rst
 setup.cfg
 setup.py
 pristine_lfs/__init__.py
+pristine_lfs/errors.py
 pristine_lfs/gitwrap.py
 pristine_lfs/gitwrap.pyi
+pristine_lfs/log.py
 pristine_lfs/main.py
 pristine_lfs/util.py
 pristine_lfs.egg-info/PKG-INFO
diff --git a/pristine_lfs.egg-info/requires.txt 
b/pristine_lfs.egg-info/requires.txt
index b065e88..9a19637 100644
--- a/pristine_lfs.egg-info/requires.txt
+++ b/pristine_lfs.egg-info/requires.txt
@@ -1,2 +1,2 @@
 python-debian
-sh
+sh>=1.14
diff --git a/pristine_lfs/__init__.py b/pristine_lfs/__init__.py
index 6df221a..ded6987 100644
--- a/pristine_lfs/__init__.py
+++ b/pristine_lfs/__init__.py
@@ -1,5 +1,6 @@
 from .main import (  # noqa: F401
 do_commit,
+do_commit_files,
 do_checkout,
 do_list,
 do_import,
diff --git a/pristine_lfs/errors.py b/pristine_lfs/errors.py
new file mode 100644
index 000..ca1db96
--- /dev/null
+++ b/pristine_lfs/errors.py
@@ -0,0 +1,67 @@
+# pristine-lfs
+#
+# errors for pristine-lfs
+#
+# Copyright (C) 2021 Collabora Ltd
+# Copyright (C) 2021 Andrej Shadura 
+#
+# SPDX-License-Identifier: GPL-2.0-or-later
+
+from __future__ import annotations
+
+from gettext import gettext as _
+
+from sh import ErrorReturnCode as CommandFailed  # noqa: F401
+
+
+class DifferentFilesExist(Exception):
+files: list[str]
+
+def __init__(self, files: list[str]):
+self.files = files
+
+def __str__(self):
+return _("would overwrite files: {files}").format(files=', 
'.join(self.files))
+
+
+class UnsupportedHashAlgorithm(Exception):
+algo: str
+
+def __init__(self, algo: str):
+self.algo = algo
+
+def __str__(self):
+return _("unsupported hash algorithm {algo}").format(
+algo=self.algo,
+)
+
+
+class GitError(Exception):
+pass
+
+
+class GitFileNotFound(GitError):
+filename: s

Bug#986410: autopkg tests don't run with the same dependencies as during the build

[Matthias Klose]

Package: src:python-biopython
Version: 1.78+dfsg-4

The autopkg tests don't run with the same dependencies as during the build. Just
noticed because the python3-renderpm dependency seems to be necessary with the
reportlab package from experimental.

But in general, please run the autopkg tests with the same packages as done
during the build.

Bug#986409: unblock: azure-cosmos-python/3.1.1-4

[Luca Boccassi]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

Please unblock package azure-cosmos-python

The new upload fixes a warning that appears to users on every package
installation/upgrade.
See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985021
It also updates the source package metadata after the (somewhat) recent re-
organization of Python packages on Salsa.

unblock azure-cosmos-python/3.1.1-4
diff -Nru azure-cosmos-python-3.1.1/debian/changelog 
azure-cosmos-python-3.1.1/debian/changelog
--- azure-cosmos-python-3.1.1/debian/changelog  2020-03-07 10:58:01.0 
+
+++ azure-cosmos-python-3.1.1/debian/changelog  2021-03-12 12:02:24.0 
+
@@ -1,3 +1,22 @@
+azure-cosmos-python (3.1.1-4) unstable; urgency=medium
+
+  [ Debian Janitor ]
+  * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
+Repository-Browse.
+
+  [ Ondřej Nový ]
+  * d/control: Update Maintainer field with new Debian Python Team
+contact address.
+  * d/control: Update Vcs-* fields with new Debian Python Team Salsa
+layout.
+
+  [ Luca Boccassi ]
+  * Bump Standards-Version to 4.5.1, no changes
+  * Bump debhelper-compat to 13
+  * Add patch to fix syntax warning on package install (Closes: #985021)
+
+ -- Luca Boccassi   Fri, 12 Mar 2021 12:02:24 +
+
 azure-cosmos-python (3.1.1-3) unstable; urgency=medium
 
   * Remove build-dependency on pytest, all tests require connection to
diff -Nru azure-cosmos-python-3.1.1/debian/control 
azure-cosmos-python-3.1.1/debian/control
--- azure-cosmos-python-3.1.1/debian/control2020-03-07 10:57:39.0 
+
+++ azure-cosmos-python-3.1.1/debian/control2021-03-12 12:01:33.0 
+
@@ -1,18 +1,18 @@
 Source: azure-cosmos-python
-Maintainer: Debian Python Modules Team 

+Maintainer: Debian Python Team 
 Uploaders: Luca Boccassi ,
-Build-Depends: debhelper-compat (= 12),
+Build-Depends: debhelper-compat (= 13),
dh-python,
python3-all,
python3-setuptools,
python3-sphinx,
-Standards-Version: 4.5.0
+Standards-Version: 4.5.1
 Section: python
 Priority: optional
 Rules-Requires-Root: no
 Homepage: https://github.com/Azure/azure-cosmos-python
-Vcs-Browser: https://salsa.debian.org/python-team/modules/azure-cosmos-python
-Vcs-Git: https://salsa.debian.org/python-team/modules/azure-cosmos-python.git
+Vcs-Browser: https://salsa.debian.org/python-team/packages/azure-cosmos-python
+Vcs-Git: https://salsa.debian.org/python-team/packages/azure-cosmos-python.git
 Testsuite: autopkgtest-pkg-python
 
 Package: python3-azure-cosmos
diff -Nru azure-cosmos-python-3.1.1/debian/patches/series 
azure-cosmos-python-3.1.1/debian/patches/series
--- azure-cosmos-python-3.1.1/debian/patches/series 1970-01-01 
01:00:00.0 +0100
+++ azure-cosmos-python-3.1.1/debian/patches/series 2021-03-12 
12:01:33.0 +
@@ -0,0 +1 @@
+syntax_warning.patch
diff -Nru azure-cosmos-python-3.1.1/debian/patches/syntax_warning.patch 
azure-cosmos-python-3.1.1/debian/patches/syntax_warning.patch
--- azure-cosmos-python-3.1.1/debian/patches/syntax_warning.patch   
1970-01-01 01:00:00.0 +0100
+++ azure-cosmos-python-3.1.1/debian/patches/syntax_warning.patch   
2021-03-12 12:02:09.0 +
@@ -0,0 +1,15 @@
+Author: Luca Boccassi 
+Forwarded: https://github.com/Azure/azure-cosmos-python/pull/207
+Description: fix syntax warning
+Bug-Debian: https://bugs.debian.org/985021
+--- a/azure/cosmos/session.py
 b/azure/cosmos/session.py
+@@ -183,7 +183,7 @@
+ session_token = 
response_headers[http_constants.HttpHeaders.SessionToken]
+ 
+ id_to_sessionlsn = {}
+-if session_token is not '':
++if session_token != '':
+ ''' extract id, lsn from the token. For p-collection,
+ the token will be a concatenation of pairs for each collection'''
+ token_pairs = session_token.split(',')
diff -Nru azure-cosmos-python-3.1.1/debian/upstream/metadata 
azure-cosmos-python-3.1.1/debian/upstream/metadata
--- azure-cosmos-python-3.1.1/debian/upstream/metadata  1970-01-01 
01:00:00.0 +0100
+++ azure-cosmos-python-3.1.1/debian/upstream/metadata  2021-03-12 
12:01:33.0 +
@@ -0,0 +1,5 @@
+---
+Bug-Database: https://github.com/Azure/azure-cosmos-python/issues
+Bug-Submit: https://github.com/Azure/azure-cosmos-python/issues/new
+Repository: https://github.com/Azure/azure-cosmos-python.git
+Repository-Browse: https://github.com/Azure/azure-cosmos-python

Bug#985358: pitivi: A/V out of sync in rendered videos

[Antonio Terceiro]

On Sat, Mar 20, 2021 at 10:43:05AM +0200, Sebastian Dröge wrote:
> On Tue, 2021-03-16 at 13:39 -0300, Antonio Terceiro wrote:
> 
> As a user, I don't even know about all the stuff that could be better;
> pitivi worked ok for me as an amateur video editor. It just failed at
> the end of the process, rendering the video. So from my PoV, the
> version in bullseye is fine once this is fixed.
> 
> Of course the latest and greatest if always better, but that's
> incompatible with a stable release. We just have to cut it at some
> point.
> 
> While that's true, in this case I'm mostly concerned about all the
> bugfixes that happened in the meantime.
> 
> In any case, would you be interested in helping maintaining this
> package? I don't have much time for that these days.

I already maintain quite a few packages, I'm not sure I will be able to.

Thanks for fixing this!


signature.asc
Description: PGP signature

Bug#986408: mali-midgard-dkms: Fail to install/build

[Christian Marillat]

Package: mali-midgard-dkms
Version: 16.0+pristine-4
Severity: serious

Dear Maintainer,

This package fail to install/build with :

$ sudo apt-get dist-upgrade 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] 
Setting up mali-midgard-dkms (16.0+pristine-4) ...
Building for 5.10.0-5-arm64
Traceback (most recent call last):
  File "/usr/bin/lsb_release", line 95, in 
main()
  File "/usr/bin/lsb_release", line 59, in main
distinfo = lsb_release.get_distro_information()
  File "/usr/lib/python3/dist-packages/lsb_release.py", line 356, in 
get_distro_information
distinfo = guess_debian_release()
  File "/usr/lib/python3/dist-packages/lsb_release.py", line 246, in 
guess_debian_release
get_distro_info(distinfo['ID'])
  File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in 
get_distro_info
RELEASES_ORDER.sort(key=lambda n: float(n[0]))
  File "/usr/lib/python3/dist-packages/lsb_release.py", line 48, in 
RELEASES_ORDER.sort(key=lambda n: float(n[0]))
ValueError: could not convert string to float: '6.06 LTS'
/usr/lib/dkms/common.postinst: 236: [: =: unexpected operator
Building for architecture arm64
This package appears to be a binaries-only package
 you will not be able to build against kernel 5.10.0-5-arm64
 since the package source was not provided
Removing old mali-midgard-16.0 DKMS files...

--
Deleting module version: 16.0
completely from the DKMS tree.
--
Done.
Loading new mali-midgard-16.0 DKMS files...
Building for 5.10.0-5-arm64
Building initial module for 5.10.0-5-arm64
Error! Bad return status for module build on kernel: 5.10.0-5-arm64 (aarch64)
Consult /var/lib/dkms/mali-midgard/16.0/build/make.log for more information.
dpkg: error processing package mali-midgard-dkms (--configure):
 installed mali-midgard-dkms package post-installation script subprocess 
returned error exit status 10
Errors were encountered while processing:
 mali-midgard-dkms
E: Sub-process /usr/bin/dpkg returned an error code (1)

Christian

-- System Information:
Debian Release: bullseye/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: arm64 (aarch64)

Kernel: Linux 5.10.0-5-arm64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mali-midgard-dkms depends on:
ii  dkms  2.8.4-3

mali-midgard-dkms recommends no packages.

mali-midgard-dkms suggests no packages.

-- no debconf information

Bug#986400: lintian: false positive about permissions for read-only GNAT .ali files

[Felix Lechner]

Hi,

On Mon, Apr 5, 2021 at 5:12 AM Nicolas Boulenguez  wrote:
>
> This affects all packages containing an Ada library.

Thanks! Why are ADA libraries installed with non-standard permissions,
please? A quick online search turned up only this reasoning. [1] Why
is that not a bug in GNAT, please?

Kind regards
Felix Lechner

[1] https://stackoverflow.com/a/33626086

Bug#986400: lintian: false positive about permissions for read-only GNAT .ali files

[Nicolas Boulenguez]

> We cannot investigate your claim without more data. Which package is
> so affected, please? Thanks!

Sorry, I should have given the reference. All lines in
  https://lintian.debian.net/tags/non-standard-file-perm
matching
  W non-standard-file-perm usr/lib/*.ali 0444 != 0644
are recent false alerts.
This affects all packages containing an Ada library.

Bug#985592: unblock: libnbd/1.6.2-1

[Salvatore Bonaccorso]

Hi Hilko,

On Thu, Mar 25, 2021 at 10:04:46PM +0100, Salvatore Bonaccorso wrote:
> Hi Hilko,
> 
> On Sat, Mar 20, 2021 at 06:24:57PM +0100, Sebastian Ramacher wrote:
> > Control: tags -1 + moreinfo
> > 
> > On 2021-03-20 15:27:28 +0100, Salvatore Bonaccorso wrote:
> > > Package: release.debian.org
> > > Severity: normal
> > > User: release.debian@packages.debian.org
> > > Usertags: unblock
> > > X-Debbugs-Cc: car...@debian.org,ben...@debian.org
> > > 
> > > Hi Release team
> > > 
> > > [Disclaimer, not the maintainer requesting the unblock, but I'm CC'ing
> > > Hilko to confirm].
> > > 
> > > Please unblock package libnbd
> > > 
> > > [ Reason ]
> > > The new upstream version uploaded libnbd/1.6.2-1 contains as fix for
> > > CVE-2021-20286. I was announced as
> > > https://listman.redhat.com/archives/libguestfs/2021-March/msg00092.html
> > > . An isolated fix was
> > > https://gitlab.com/nbdkit/libnbd/-/commit/2216190ecbbd853648df6a3280c17b345b0907a0
> > > . The request is done to have bullseye without this CVE open.
> > > 
> > > [ Impact ]
> > > Denial of service.
> > > 
> > > [ Tests ]
> > > I have not performed tests specific to the version update 1.6.1 to
> > > 1.6.2.
> > > 
> > > [ Risks ]
> > > Arguably there is a new upstream version, but the attached debdiff
> > > collects all the changes additionally done.
> > > 
> > > Again, Hilko is CC'ed to confirm if this is safe for bullseye.
> > > 
> > > [ Checklist ]
> > >   [ ] all changes are documented in the d/changelog
> > >   [ ] I reviewed all changes and I approve them
> > >   [x] attach debdiff against the package in testing
> > > 
> > > [ Other info ]
> > > It should propably have an explicit acknowledgment for the unblock
> > > from Hilko.
> > 
> > Please remove the moreinfo tag once ACKed by Hilko.
> 
> Any input on this? Or was the version not aimed for bullseye?

Friendly ping. Di you got my email?

Now there was a new upstream version uploaded to unstable, so this is
going to be a bigger diff.

Regards,
Salvatore