Bug#992394: RM: tinyca -- ROM; Depends on libgtk2-perl (deprecated upstream + GNOME team's goal of reducing gtk2 use in Debian)

[intrigeri]

Package: ftp.debian.org
Severity: normal

Hi,

I'm splitting #986109, as Sean kindly requested.

The bug report about this package's dependency on libgtk2-perl is #912889.

I'll share some extra information here on top of what's already on #986109,
because among the reverse dependencies of libgtk2-perl, this one is kind of
a special case, for 2 reasons.

First, "ROM" is clearly overstated here: tinyca is not maintained by a team I'm
part of. However, I'm the maintainer for libgtk2-perl.

Second, among the reverse dependencies of libgtk2-perl for which I just filed RM
bug reports, this is the only one where some effort to port the package to
current GTK happened. However, the product of this effort does not appear to
have been published yet, and the information I see leads me to suspect this
effort has been stalled since 11 months:

  https://bugs.debian.org/912889#36

So while there's some hope tinyca makes it back into Debian at some point,
I don't think it warrants blocking the libgtk2-perl removal project which
I started in November 2018. The package has not been installable on sid
since October 2019 so removing it now won't change the situation for users.

Thanks!

Bug#992393: RM: libcircle-fe-gtk-perl -- ROM; Depends on libgtk2-perl (deprecated upstream + GNOME team's goal of reducing gtk2 use in Debian)

[intrigeri]

Package: ftp.debian.org
Severity: normal

Hi,

I'm splitting #986109, as Sean kindly requested.

The bug report about this package's dependency on libgtk2-perl is #932220
(compared to the other libgtk2-perl reverse dependencies that have 33 months old
bug reports about it, this one was filed only 2 years ago, because the package
was first uploaded to Debian 8 months after I announced that libgtk2-perl was
going away).

Thanks!

Bug#992392: RM: libdata-treedumper-renderer-gtk-perl -- ROM; Depends on libgtk2-perl (deprecated upstream + GNOME team's goal of reducing gtk2 use in Debian)

[intrigeri]

Package: ftp.debian.org
Severity: normal

Hi,

I'm splitting #986109, as Sean kindly requested.

The bug report about this package's dependency on libgtk2-perl is #912874.
The only reverse-dependency is asciio, whose removal I just requested.

Thanks!

Bug#992391: RM: asciio -- ROM; Depends on libgtk2-perl (deprecated upstream + GNOME team's goal of reducing gtk2 use in Debian)

[intrigeri]

Package: ftp.debian.org
Severity: normal

Hi,

I'm splitting #986109, as Sean kindly requested.

The bug report about this package's dependency on libgtk2-perl is #912870.

Unfortunately, the RFH I filed a year ago (#968843) was not sufficient.

Thanks!

Bug#992390: RM: libkavorka-perl -- ROM; depends on libparse-keyword-perl, whose upstream says "DO NOT USE!"

[intrigeri]

Package: ftp.debian.org
Severity: normal

Hi,

I'm splitting #986107 as requested by Sean.

Thanks!

Bug#992389: RM: libmoops-perl -- ROM; Please enter the reason for removal: depends on libparse-keyword-perl, whose upstream says "DO NOT USE!"

[intrigeri]

Package: ftp.debian.org
Severity: normal

Hi,

I'm splitting #986107 as requested by Sean.

Thanks!

Bug#992388: RM: libnet-dns-cloudflare-ddns-perl -- RoQA; depends on libparse-keyword-perl, whose upstream says "DO NOT USE!"

[intrigeri]

Package: ftp.debian.org
Severity: normal

Hi,

I'm splitting #986107 as requested by Sean.

Thanks!

Bug#992387: RM: libcloudflare-client-perl -- ROM; unusable, seemingly dead upstream, depends on deprecated libparse-keyword-perl

[intrigeri]

Package: ftp.debian.org
Severity: normal

Hi,

I'm splitting #986107 as Sean kindly requested.

On top of the reasons mentioned there, this package has been completely unusable
since 3 years: #983473.

Thanks!

Bug#992386: has a duplicated changelog

[Marco d'Itri]

Package: debianutils
Version: 5.0.1-1
Severity: normal

Only one should be installed:

31bf287ed7a39cc395f6d91002ca8155  /usr/share/doc/debianutils/changelog.Debian.gz
31bf287ed7a39cc395f6d91002ca8155  /usr/share/doc/debianutils/changelog.gz

-- 
ciao,
Marco


signature.asc
Description: PGP signature

Bug#954598: [Debian-lego-team] Bug#954598: nxt-firmware: FTBFS: readr.c:49: undefined reference to `_read'

[Petter Reinholdtsen]

Hi,

[Nicolas Schodet]
> I just upgraded to bullseye and saw this.
>
> I have made a fix on my git repo:
>
> https://git.ni.fr.eu.org/nxt-firmware.git/log/
>
> Now I need to update the website and do a real release.

Nice!  What can be changed to ensure you discover such issues before
releases in the future?

For the record, this is the patch:

diff --git a/AT91SAM7S256/SAM7S256/gcc/Makefile 
b/AT91SAM7S256/SAM7S256/gcc/Makefile
index f236a08..ed52112 100644
--- a/AT91SAM7S256/SAM7S256/gcc/Makefile
+++ b/AT91SAM7S256/SAM7S256/gcc/Makefile
@@ -45,7 +45,7 @@ ASFLAGS = -g -mcpu=$(MCU) $(THUMB) $(THUMB_INTERWORK)
 CPPFLAGS = $(INCLUDES) $(DEFINES) -MMD
 LDSCRIPT = nxt.ld
 LDFLAGS = -nostdlib -T $(LDSCRIPT) -Wl,--gc-sections
-LDLIBS = -lc -lm -lgcc
+LDLIBS = -lc -lm -lgcc -lnosys
 
 ifeq ($(ARMDEBUG),y)
 ASM_ARM_SOURCE += abort_handler.S undef_handler.S debug_hexutils.S \

-- 
Happy hacking
Petter Reinholdtsen

Bug#992385: x11-common: use of deprecated tempfile breaks login

[duck]

Package: x11-common
Version: 1:7.7+22
Severity: grave


Quack,

Since debianutils has dropped the deprecated `tempfile` in 5.0-1 
/etc/X11/Xsession fails around the WRITE_TEST and this breaks graphical 
login completely. Commenting this section allowed me to log in. There is 
another call line 85 that needs to be changed too.


Regards.
\_o<

--
Marc Dequènes

Bug#992384: isc-dhcp-client: default domain-search incorrectly appends a period

[Martin-Éric Racine]

Package: isc-dhcp-client
Version: 4.4.1-2.3
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I added those options to the configuration:

default domain-name "lan";
default domain-search "lan";

What I get as a result:

domain lan
search lan.
nameserver 62.241.198.245
nameserver 62.241.198.246

There is an extraneous period that should not be there.

- -- System Information:
Debian Release: 11.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages isc-dhcp-client depends on:
ii  debianutils4.11.2
ii  iproute2   5.10.0-4
ii  libc6  2.31-13
ii  libdns-export1110  1:9.11.19+dfsg-2.1
ii  libisc-export1105  1:9.11.19+dfsg-2.1

Versions of packages isc-dhcp-client recommends:
ii  isc-dhcp-common  4.4.1-2.3

Versions of packages isc-dhcp-client suggests:
pn  avahi-autoipd 
pn  isc-dhcp-client-ddns  
pn  resolvconf

- -- Configuration Files:
/etc/dhcp/dhclient.conf changed:
option rfc3442-classless-static-routes code 121 = array of unsigned integer 8;
send host-name = gethostname();
request subnet-mask, broadcast-address, time-offset, routers,
domain-name, domain-name-servers, domain-search, host-name,
dhcp6.name-servers, dhcp6.domain-search, dhcp6.fqdn, dhcp6.sntp-servers,
netbios-name-servers, netbios-scope, interface-mtu,
rfc3442-classless-static-routes, ntp-servers;
default domain-name "lan";
default domain-search "lan";


- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmEcjzEACgkQrh+Cd8S0
17bbEhAAi4610ot7kI5Gje38DUz8dSkBcswK/ajfRNOrX2dcmE3tgJLLbzfHYKV7
FfAIoQjN0j7Fn57c6N07ATVEDgvG1mcuuvHe5HgspDbPS0EYeCnicWvd9qUrZFwR
jQ6uwzsm0iAzUjQJzRs8SGX2mJDqek81aqO4X9Snx+5KFrn6h2/M3BzS49Jpxzwd
jrFxDkWgkVqRzLMyD4Oc9W+bCo6/57b4y8oPrH0IK1ie25Pn28NkYo7kaCJl29GZ
z7qyzsOPMuxo+UzAULcRZswqvwzzprJGWXCIf7i2FvXPPGGvPgGtKUrf9Xeeiivc
Wstyw+cLBb55N/5WmNIBZn2750EjR0v6hTLEorpDptnkjcvdbdlTp7+ACXfKIV9z
ETbL50bFD4a3vL+Nbut6PK1la99UjqNQ+DpDi4Len6IDQ9XXOFLYIPGNDvokxby9
3X1Bs6l2G4XfS2jJ1DxJbSmAQSe5+XC+VIrYQv7of85g6Xi4Pp6Pj5GMWv35tShN
y5PKptOUCm586JqHboIGmauUqYKCUsHaS8om2CF/fk90bSWIHaYY+38aL+pQC8RC
HpAtvLvcACzMHoQ87zAwRYqqpZ+WDSw8Haa+zLbWqze75GB+53t/tHEberxhFwXh
xMQ0x7d9xBQu4FPYeLzmuJJfpdXAYbRNrLs8kGDh4Ii+7jRtWks=
=xmgh
-END PGP SIGNATURE-

Bug#992383: debianutils: which is noisy and doesn't suggest a different option

[Norbert Preining]

Package: debianutils
Version: 5.0.1-1
Severity: important

Hi,

it seems that /usr/bin/which from debianutils has been deprecated, which
is ok, but being noisy about it on any invocation, **without** providing
an alternative is a no go, since it might break scripts that parse
output including stderr.

Please use NEWS, or whatever other channels, and above all, **provide
information on a replacement!**

Thanks

Norbert



-- System Information:
Debian Release: 11.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.13.11+ (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages debianutils depends on:
ii  libc6  2.31-15

debianutils recommends no packages.

debianutils suggests no packages.

-- no debconf information

Bug#992379: bind9: bind-9.16.15 + dnssec-policy in options{} = assertion failure abort/crash

[raf]

Package: bind9
Version: 1:9.16.15-1
Severity: important

Dear Maintainer,

Bind has a dnssec-policy {} stanza for defining your
own policy if you're feeling adventurous, but there's
also a default policy. And there's a dnssec-policy
usage directive to specify which dnssec-policy should
be applied to zones.

Bind's documentation says that the dnssec-policy usage
directive can either appear in the options {} stanza,
so as to apply to all zones, or it can appear in
individual zone {} stanzas.

My advice is:

  DO NOT PUT DNSSEC-POLICY IN THE OPTIONS {} STANZA.
  ONLY PUT DNSSEC-POLICY IN THE ZONE {} STANZAS.

I put it in the options {} stanza, not realising that
"all zones" doesn't just mean all of *my* authoritative
zones. It really means ALL zones. That means every zone
/etc/bind/named.conf.local (i.e. my zones), as well as
every zone in /etc/bind/named.conf.default-zones i.e.:

  localhost
  127.in-addr.arpa
  0.in-addr.arpa
  255.in-addr.arpa

And, if you uncomment the include "/etc/bind/zones.rfc1918"
in /etc/bind/named.conf.local, then it also means all of
those zones as well:

  16.172.in-addr.arpa
  17.172.in-addr.arpa
  ...
  31.172.in-addr.arpa
  168.192.in-addr.arpa

What happens next is that bind tries and fails to
create .jnl files in /etc/bind for these zones.
Apparmor or the directory permissions prevents it.
This sort of thing appears in the logs:

  general: error: /etc/bind/db.empty.jnl: create: permission denied
  general: error: /etc/bind/db.255.jnl: create: permission denied

Then bind gets an assertion failure and exits:

  general: notice: all zones loaded
  general: notice: running
  general: critical: rbtdb.c:6780: REQUIRE(((rbtnode->nsec == DNS_RBT_NSEC_NSEC3
&& (rdataset->type == ((dns_rdatatype_t)dns_rdatatype_nsec3) || 
rdataset->covers
== ((dns_rdatatype_t)dns_rdatatype_nsec3))) || (rbtnode->nsec != 
DNS_RBT_NSEC_NSEC3
&& rdataset->type != ((dns_rdatatype_t)dns_rdatatype_nsec3) && 
rdataset->covers
!= ((dns_rdatatype_t)dns_rdatatype_nsec3 failed, back trace
  general: critical: #0 0x558ce49ffeed in ??
  general: critical: #1 0x7fd079be6d9a in ??
  general: critical: #2 0x7fd079d7f73c in ??
  general: critical: #3 0x7fd079e45680 in ??
  general: critical: #4 0x7fd079c1b720 in ??
  general: critical: #5 0x7fd079c20f52 in ??
  general: critical: #6 0x7fd07995cea7 in ??
  general: critical: #7 0x7fd079590def in ??
  general: critical: exiting (due to assertion failure)

This repeats again and again until you work out what
happened, clean everything up, remove the dnssec-policy
from the options {} stanza, and restart bind.

And, unless I went temporarily insane, it even managed
somehow to overwrite my source zonefiles with signed
versions, and I had to restore them from backup. When
it works properly, it puts the signed versions in
separate files.

However, if you put the dnssec-policy usage directive in the
zone {} stanzas instead, it's absolutely brilliant.

But that's just a workaround. A fix would be to patch bind
so that the dnssec-policy directive in the options {} stanza
does not apply to the localhost zone or any .in-addr.arpa zones.

cheers,
raf

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

Kernel: Linux 5.10.0-8-amd64 (SMP w/1 CPU thread)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages bind9 depends on:
ii  adduser3.118
ii  bind9-libs 1:9.16.15-1
ii  bind9-utils1:9.16.15-1
ii  debconf [debconf-2.0]  1.5.77
ii  dns-root-data  2021011101
ii  init-system-helpers1.60
ii  iproute2   5.10.0-4
ii  libc6  2.31-13
ii  libcap21:2.44-1
ii  libfstrm0  0.6.0-1+b1
ii  libjson-c5 0.15-2
ii  liblmdb0   0.9.24-1
ii  libmaxminddb0  1.5.2-1
ii  libprotobuf-c1 1.3.3-1+b2
ii  libssl1.1  1.1.1k-1
ii  libuv1 1.40.0-2
ii  libxml22.9.10+dfsg-6.7
ii  lsb-base   11.1.0
ii  netbase6.3
ii  zlib1g 1:1.2.11.dfsg-2

bind9 recommends no packages.

Versions of packages bind9 suggests:
pn  bind-doc   
ii  bind9-dnsutils [dnsutils]  1:9.16.15-1
ii  dnsutils   1:9.16.15-1
pn  resolvconf 
pn  ufw

-- Configuration Files:
/etc/apparmor.d/local/usr.sbin.named changed [not included]
/etc/apparmor.d/usr.sbin.named changed [not included]
/etc/bind/named.conf.local changed [not included]
/etc/bind/named.conf.options changed [not included]

-- debconf information:
  bind9/run-resolvconf: false
  bind9/different-configuration-file:
  bind9/start-as-user: bind

Bug#976367: cruft-ng: add support for plocate

[Paul Wise]

Control: severity -1 serious

On Sun, 06 Jun 2021 13:07:39 +0800 Paul Wise wrote:

> plocate now Breaks: mlocate, which means that both plocate and mlocate
> cannot be installed on the same system. That change makes it much more
> important that cruft-ng add support for plocate too, bumping severity.

plocate has now taken over the mlocate binary, which likely means that
cruft-ng no longer works in Debian unstable, because IIRC it relies on
the mlocate database format, so I am upgrading the severity of this bug.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#992382: transition: granite

[Boyuan Yang]

Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: by...@debian.org
Severity: normal

Dear Release Team,

I plan to start the transition as listed on this page: 

https://release.debian.org/transitions/html/auto-granite.html .

The transition comes with SONAME bump in the new version of libgranite. There
are 6 reverse build-dependencies, and I have verified that they can all be
built successfully with libgranite in experimental:

akira (ok)
bookworm (ok)
budgie-extras (ok)
easyssh (ok)
minder (ok)
sequeler (ok)

Ben file (the auto-generated one already looks ok):

title = "granite";
is_affected = .depends ~ "libgranite5" | .depends ~ "libgranite6";
is_good = .depends ~ "libgranite6";
is_bad = .depends ~ "libgranite5";

The dependency chain is straightforward and we only needs binNMUs, so I expect
it to be a smooth transition.


Thanks,
Boyuan Yang


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

Bug#964785: I'd like to create a shutter package and add it to the Debian package.

[jiho lee]

I didn't add one of the required dependencies to the control file, and this
package is called libgtk3-imageview-perl . When I tried packaging in
Buster, this package was not in Buster, so I had to build it separately,
but fortunately it was in Bullseye.


There is a future society, but my future is not what others do.
Dept. of Information Science, Graduate School, Korea National Open
University


2021년 8월 18일 (수) 오전 5:55, Michael Kogan 님이 작성:

> I see, thanks for clarifying this! We have documented the dependencies
> here: https://shutter-project.org/downloads/dependencies/ Most of them
> are actually named in Debian/Ubuntu naming style, as far as I know.
>
> As jiho lee already mentioned, it would be necessary to package
> https://metacpan.org/dist/GooCanvas2-CairoTypes and add it as dependency.
>
> The dependency gir1.2-appindicator3-0.1 is necessary for core
> functionality (showing the tray icon) but only for Gnome users. Don't know
> what the best way to deal with this is... In the Ubuntu PPA this is a
> "Recommended" dependency, in Arch Linux an optional one.
>
> Am Di., 17. Aug. 2021 um 22:30 Uhr schrieb Andrej Shadura <
> and...@shadura.me>:
>
>> Hi
>>
>> Unfortunately, that packaging isn’t well-commented, so it’s not easy to
>> verify what exactly is needed and what isn’t.
>> It would be much better if you as the upstream documented the exact
>> dependencies and other requirement, preferably in some standard format e.g.
>> (probably? I’m not a Perl expert) META.yml or something, or at least in the
>> README file.
>>
>> --
>> Cheers,
>>   Andrej
>>
>>

Bug#990694: unison -addversionno option broken

[Vincent Lefevre]

Control: severity -1 important

On 2021-07-04 22:29:30 +0100, Ken Milmore wrote:
> The -addversionno option of unison attempts to invoke the same
> version of unison on the server as on the client, to prevent version
> mismatches.

It mainly allows one to select the expected version on the server
when several versions are installed (because of various kinds of
machines to synchronize).

> A workaround is to install the symlink manually, e.g.:
> 
> $sudo ln -s ../../bin/unison-2.51+4.11.1 /usr/local/bin/unison-2.51

This currently works, but will fail if the OCaml version is upgraded,
so that one has unison-2.51+X and unison-2.51+Y on the server,
with some clients having unison-2.51+X and other clients having
unison-2.51+Y. In short, this defeats the purpose of having the
OCaml version added to the version number for compatibility.
Thus...

> Suggested possible bug fixes:
> 
> 1) Install an additional /usr/bin/unison-2.51 symbolic link in the package, or

This solution is incorrect.

> 2) Modify the unison source to invoke "unison-2.51+4.11.1" instead
> of "unison-2.51" when the -addversionno option is supplied

This is the only correct way (the client needs to announce in some way
the OCaml version).

> (however this might break compatibility with other systems).

Such systems implicitly assume some fixed OCaml version. So there is
already no guarantee that they won't break anything.

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

Bug#992381: freefem++: missing comma in Uploaders field

[Paul Wise]

Source: freefem++
Version: 4.9+dfsg1-1
Severity: serious
Usertags: uploaders
X-Debbugs-CC: Francois Mazen 

freefem++ 4.9+dfsg1-1 introduced an invalid uploaders field, that is
missing a comma between Ricardo Mones & Joseph Nahmias.

   $ apt-cache showsrc freefem++ | grep -E '^$|^Version|^Uploaders'
   Version: 3.61.1+dfsg1-6
   Uploaders: Christophe Trophime , 
Dimitrios Eftaxiopoulos 
   
   Version: 4.9+dfsg1-1
   Uploaders: Christophe Trophime , 
Dimitrios Eftaxiopoulos  Francois Mazen 

According to Debian policy 5.6.3 the Uploaders field must separate
individual uploaders using commas:

   List of the names and email addresses of co-maintainers of the
   package, if any. ... The format of each entry is the same as that of
   the Maintainer field, and multiple entries must be comma separated.
  
https://www.debian.org/doc/debian-policy/ch-controlfields.html#uploaders

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#992380: dpigs: use numfmt?

[Trent W. Buck]

Package: debian-goodies
Version: 0.87
Severity: wishlist
File: /usr/bin/dpigs
Tags: patch

Just a suggestion, but numfmt is super awesome and obviates the awk blob.

  fi | if [ $HUMAN -eq 1 ]; then
- awk '{ if ($1 > 1024*1024*1024)
-   printf("% 6.1fT %s\n", $1/(1024*1024*1024), $2);
-else if ($1 > 1024*1024)
-   printf("% 6.1fG %s\n", $1/(1024*1024), $2);
-else if ($1 > 1024)
-   printf("% 6.1fM %s\n", $1/1024, $2);
-else
-   printf("% 6.1ik %s\n", $1, $2); }'
+ numfmt --from-unit=Ki --to=iec-i --suffix=B --padding=6


Proof of concept:

bash5$ dpigs -H
 326.4M fonts-noto-extra
 287.6M linux-image-5.10.0-8-amd64
 287.5M linux-image-5.10.0-7-amd64
 209.1M llvm-11-dev
 204.9M fonts-noto-cjk-extra
 204.9M firefox
 195.3M firefox-esr
 194.1M ansible
 188.0M chromium
 178.3M ansible-doc

bash5$ dpigs | numfmt --from-unit=Ki --to=iec-i --suffix=B --padding=6
327MiB fonts-noto-extra
288MiB linux-image-5.10.0-8-amd64
288MiB linux-image-5.10.0-7-amd64
210MiB llvm-11-dev
205MiB fonts-noto-cjk-extra
205MiB firefox
196MiB firefox-esr
195MiB ansible
189MiB chromium
179MiB ansible-doc




-- System Information:
Debian Release: 11.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-security'), (500, 
'proposed-updates'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

debian-goodies depends on no packages.

Versions of packages debian-goodies recommends:
ii  apt2.2.4
ii  curl   7.74.0-1.3+b1
ii  dctrl-tools2.24-3+b1
ii  elfutils   0.183-1
ii  equivs 2.3.1
ii  libfile-slurper-perl   0.012-1
ii  libfile-which-perl 1.23-1
ii  libipc-system-simple-perl  1.30-1
ii  man-db 2.9.4-2
ii  perl   5.32.1-4
ii  popularity-contest 1.71
ii  procps 2:3.3.17-5
ii  python33.9.2-3
ii  sensible-utils 0.0.14
ii  whiptail   0.52.21-4+b3
ii  zenity 3.32.0-6

Versions of packages debian-goodies suggests:
ii  apt-file   3.2.2
ii  chromium [www-browser] 90.0.4430.212-1
ii  firefox [www-browser]  88.0.1-1
ii  firefox-esr [www-browser]  78.12.0esr-1
pn  konqueror  
ii  lsb-release11.1.0
ii  lsof   4.93.2+dfsg-1.1
ii  lynx [www-browser] 2.9.0dev.6-2
ii  midori [www-browser]   7.0-2.1
ii  netrik [www-browser]   1.16.1-2+b2
ii  openssh-client 1:8.4p1-5
ii  sudo   1.9.5p2-3
ii  w3m [www-browser]  0.5.3+git20210102-6
ii  xdg-utils  1.1.3-4.1

-- no debconf information

Bug#991549: libpmix-dev: missing Breaks+Replaces: libpmix2 (<< 4.1)

[Stuart Prescott]

This bug now affects bookworm->sid and (old)sid->sid 
upgrades.

-- 
Stuart Prescotthttp://www.nanonanonano.net/   
stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ 
stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 
7EBB 1396 F2F7

Bug#992280: cdrom: Debian 11 installer fails to produce usable display

[Mike Perrin]

Cyril,

I may have a clue as to what is going on. I tried booting Clonezilla 
Live at 800x600 resolution and got a similar shredded raster image as 
with the Debian installer. Then I booted Clonezilla with the 1024x768 
option and the display was perfect.


Mike

Bug#992378: /etc/apparmor.d/usr.sbin.cupsd: Prevents Let's Encrypt certificates from being used

[Roger Lynn]

Package: cups-daemon
Version: 2.3.3op2-3+deb11u1
Severity: normal
File: /etc/apparmor.d/usr.sbin.cupsd

Adding
  /etc/letsencrypt/archive/** r,
seems to fix this.

I only discovered what was causing the problem when I stumbled across
https://askubuntu.com/questions/1079957

Thanks,

Roger

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

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages cups-daemon depends on:
ii  adduser3.118
ii  bc 1.07.1-2+b2
ii  init-system-helpers1.60
ii  libavahi-client3   0.8-5
ii  libavahi-common3   0.8-5
ii  libc6  2.31-13
ii  libcups2   2.3.3op2-3+deb11u1
ii  libdbus-1-31.12.20-2
ii  libelogind0 [libsystemd0]  246.9.1-1+debian1
ii  libgssapi-krb5-2   1.18.3-6
ii  libpam0g   1.4.0-9
ii  libpaper1  1.1.28+b1
ii  lsb-base   11.1.0
ii  procps 2:3.3.17-5
ii  ssl-cert   1.1.0+nmu1

Versions of packages cups-daemon recommends:
pn  avahi-daemon  
pn  colord
pn  cups-browsed  
pn  ipp-usb   

Versions of packages cups-daemon suggests:
ii  cups   2.3.3op2-3+deb11u1
ii  cups-bsd   2.3.3op2-3+deb11u1
ii  cups-client2.3.3op2-3+deb11u1
ii  cups-common2.3.3op2-3+deb11u1
ii  cups-filters   1.28.7-1
pn  cups-pdf   
ii  cups-ppdc  2.3.3op2-3+deb11u1
ii  cups-server-common 2.3.3op2-3+deb11u1
ii  foomatic-db-compressed-ppds [foomatic-db]  20200820-1
ii  ghostscript9.53.3~dfsg-7
ii  poppler-utils  20.09.0-3.1
pn  smbclient  
ii  udev   247.3-6

-- Configuration Files:
/etc/cups/cups-files.conf changed:
CreateSelfSignedCerts no
SystemGroup lpadmin
LogFileGroup adm
AccessLog /var/log/cups/access_log
ErrorLog /var/log/cups/error_log
PageLog /var/log/cups/page_log


-- no debconf information

Bug#992364: libreoffice: Libreoffice fails to start - can't cd to ../lib/libreoffice/program

[A Ozbay]

Package: libreoffice
Version: 1:7.0.4-4
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: ago_debian...@protonmail.com

Libreoffice fails to launch with the following error:

"/usr/local/bin/libreoffice: 52: cd: can't cd to ../lib/libreoffice/program"

Attempting to launch Libreoffice by double clicking on e.g. an .ods file from 
Gnome fails as well. 

Flatpak version, meanwhile, launches and runs without any issues. (Issue sprang 
up before installing Flatpak version, so not related to installing both 
simultaneously)



-- System Information:
Debian Release: 11.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-security'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.13.4 (SMP w/24 CPU threads)
Kernel taint flags: 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
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libreoffice depends on:
ii  libreoffice-base1:7.0.4-4
ii  libreoffice-calc1:7.0.4-4
ii  libreoffice-core1:7.0.4-4
ii  libreoffice-draw1:7.0.4-4
ii  libreoffice-impress 1:7.0.4-4
ii  libreoffice-math1:7.0.4-4
ii  libreoffice-report-builder-bin  1:7.0.4-4
ii  libreoffice-writer  1:7.0.4-4
ii  python3-uno 1:7.0.4-4

Versions of packages libreoffice recommends:
ii  fonts-crosextra-caladea 20130214-2.1
ii  fonts-crosextra-carlito 20130920-1.1
ii  fonts-dejavu2.37-2
ii  fonts-liberation1:1.07.4-11
ii  fonts-liberation2   2.1.3-1
ii  fonts-linuxlibertine5.3.0-6
ii  fonts-noto-core 20201225-1
ii  fonts-noto-extra20201225-1
ii  fonts-noto-mono 20201225-1
ii  fonts-noto-ui-core  20201225-1
ii  fonts-sil-gentium-basic 1.102-1.1
ii  libreoffice-java-common 1:7.0.4-4
ii  libreoffice-nlpsolver   0.9+LibO7.0.4-4
ii  libreoffice-report-builder  1:7.0.4-4
ii  libreoffice-script-provider-bsh 1:7.0.4-4
ii  libreoffice-script-provider-js  1:7.0.4-4
ii  libreoffice-script-provider-python  1:7.0.4-4
ii  libreoffice-sdbc-mysql  1:7.0.4-4
ii  libreoffice-sdbc-postgresql 1:7.0.4-4
ii  libreoffice-wiki-publisher  1.2.0+LibO7.0.4-4

Versions of packages libreoffice suggests:
pn  cups-bsd
ii  default-jre [java8-runtime] 2:1.11-72
ii  firefox-esr 78.12.0esr-1
ii  ghostscript 9.53.3~dfsg-7
ii  gnupg   2.2.27-2
pn  gpa 
ii  gstreamer1.0-libav  1.18.4-3
ii  gstreamer1.0-plugins-bad1.18.4-3
ii  gstreamer1.0-plugins-base   1.18.4-2
ii  gstreamer1.0-plugins-good   1.18.4-2
ii  gstreamer1.0-plugins-ugly   1.18.4-2
ii  hunspell-en-gb [hunspell-dictionary]1:7.1.0~rc3-3
ii  hunspell-en-us [hunspell-dictionary]1:2019.10.06-1
ii  hyphen-en-us [hyphen-hyphenation-patterns]  2.8.8-7
pn  imagemagick | graphicsmagick-imagemagick-compat 
ii  libgl1  1.3.2-1
pn  libofficebean-java  
pn  libreoffice-gnome | libreoffice-plasma  
pn  libreoffice-grammarcheck
pn  libreoffice-help
pn  libreoffice-l10n
pn  libreoffice-librelogo   
ii  libsane11.0.31-4.1
ii  libxrender1 1:0.9.10-1
pn  myspell-dictionary  
ii  mythes-en-us [mythes-thesaurus] 1:7.1.0~rc3-3
pn  openclipart2-libreoffice | openclipart-libreoffice  
ii  openjdk-11-jre [java8-runtime]  11.0.12+7-2
pn  pstoedit
pn  unixodbc

Versions of packages libreoffice-core depends on:
ii  fontconfig  2.13.1-4.2
ii  fonts-opensymbol2:102.11+LibO7.0.4-4
ii  libboost-locale1.74.0   1.74.0-9
ii  libc6   2.31-13
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+deb11u1
ii  libcurl3-gnutls   

Bug#992377: manpages-dev

[Dominique Brazziel]

Package: manpages-dev
Version: 5.10-1
Severity: normal
X-Debbugs-Cc: dbrazz...@snet.net

Dear Maintainer,

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

   * What led up to the situation?
Tried to compile the man 2 add_key example program

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
Compile error indicating include file 'keyutils.h' not found

   * What outcome did you expect instead?
Clean comile
*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-security'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-8-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULELocale: 
LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages manpages-dev depends on:
ii  manpages  5.10-1

manpages-dev recommends no packages.

Versions of packages manpages-dev suggests:
ii  man-db [man-browser]  2.9.4-2

-- no debconf information

Bug#984404: zxing-cpp: ftbfs with GCC-11

[John Scott]

This seems to be fixed in the version in experimental.


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

Bug#992363: qmenumodel FTBFS with recent glib2.0: error: template with C linkage

[Simon McVittie]

Control: tags -1 + bookworm sid patch

On Tue, 17 Aug 2021 at 22:11:34 +0200, Helmut Grohne wrote:
> | In file included from /usr/include/glib-2.0/glib/gatomic.h:31,
> |  from /usr/include/glib-2.0/glib/gthread.h:32,
> |  from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
> |  from /usr/include/glib-2.0/glib.h:32,
> |  from /usr/include/glib-2.0/gobject/gbinding.h:28,
> |  from /usr/include/glib-2.0/glib-object.h:22,
> |  from 
> /<>/libqmenumodel/src/qmenumodelevents.cpp:21:
> | /usr/include/c++/10/type_traits:2925:3: error: template with C linkage
> |  2925 |   template
> |   |   ^~~~
> | /<>/libqmenumodel/src/qmenumodelevents.cpp:20:1: note: ‘extern 
> "C"’ linkage started here
> |20 | extern "C" {
> |   | ^~
> 
> Similar bug with more details: #992246

Ubuntu has a patch which seems appropriate.
https://patches.ubuntu.com/q/qmenumodel/qmenumodel_0.8.0-2ubuntu1.patch
See #992246 for context and explanation.

It would also be good to define GLIB_VERSION_MIN_REQUIRED and
GLIB_VERSION_MAX_ALLOWED to avoid surprises in future, similar to
.

smcv

Bug#954598: nxt-firmware: FTBFS: readr.c:49: undefined reference to `_read'

[Nicolas Schodet]

> Thank you for discovering this issue.  I hope someone find a fix in time
> for the next Debian release.  I suspect I will not.

Hello,

I just upgraded to bullseye and saw this.

I have made a fix on my git repo:

https://git.ni.fr.eu.org/nxt-firmware.git/log/

Now I need to update the website and do a real release.

Nicolas.

Bug#980838: gpg-agent: generator 90gpg-agent without scdaemon generate annoying log

[Timo Sigurdsson]

Package: gpg-agent
Version: 2.2.27-2

I can confirm this issue. It still occurs on the newly released stable 
distribution (bullseye).
Linking /usr/lib/gnupg/scdaemon to /usr/bin/false works around the issue, but 
since I don't know whether that could have unwanted sideeffects, I'd very much 
prefer a fix in the package or script itself.

Thanks!

Bug#992376: systemd-standalone-{sysusers, tmpfiles}: missing Breaks+Replaces: systemd (<< 249.3-2)

[Michael Biebl]

Am 18.08.2021 um 01:18 schrieb Andreas Beckmann:

On 18/08/2021 01.09, Michael Biebl wrote:

It's not a package split.


It looked like one.

systemd-standalone-* are new packages. They follow the debian policy 
recommended way using C/R/P against a virtual package.


You still need versioned B+R (or similar) against systemd versions not 
providing the new virtual package.


This is only relevant for partial upgrades which are semi-supported.



OpenPGP_signature
Description: OpenPGP digital signature

Bug#992376: systemd-standalone-{sysusers, tmpfiles}: missing Breaks+Replaces: systemd (<< 249.3-2)

[Andreas Beckmann]

On 18/08/2021 01.09, Michael Biebl wrote:

It's not a package split.


It looked like one.

systemd-standalone-* are new packages. They follow the debian policy 
recommended way using C/R/P against a virtual package.


You still need versioned B+R (or similar) against systemd versions not 
providing the new virtual package.


Andreas

Bug#992376: systemd-standalone-{sysusers, tmpfiles}: missing Breaks+Replaces: systemd (<< 249.3-2)

[Michael Biebl]

Am 18.08.2021 um 01:03 schrieb Andreas Beckmann:

On 18/08/2021 00.41, Michael Biebl wrote:

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.


There is no version of systemd-standalone-* in sid so how can it fail 
an upgrade from sid to experimental?


Please suggest a better wording for the bug template that also covers 
this case of package splits with insufficient B+R.


It's not a package split.
systemd-standalone-* are new packages. They follow the debian policy 
recommended way using C/R/P against a virtual package.





OpenPGP_signature
Description: OpenPGP digital signature

Bug#992376: systemd-standalone-{sysusers, tmpfiles}: missing Breaks+Replaces: systemd (<< 249.3-2)

[Michael Biebl]

Am 18.08.2021 um 01:09 schrieb Michael Biebl:

Am 18.08.2021 um 01:03 schrieb Andreas Beckmann:

On 18/08/2021 00.41, Michael Biebl wrote:
during a test with piuparts I noticed your package fails to upgrade 
from

'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.


There is no version of systemd-standalone-* in sid so how can it fail 
an upgrade from sid to experimental?


Please suggest a better wording for the bug template that also covers 
this case of package splits with insufficient B+R.


It's not a package split.



I.e. systemd continues to ship the systemd-sysusers and systemd-tmpfiles 
binary.

Bug#897277: decrease e2fsprogs' Priority: required

[Faidon Liambotis]

Hi!

On Mon, Jan 11, 2021 at 12:48:25AM +0200, Faidon Liambotis wrote:
> On Mon, Aug 21, 2017 at 08:42:16AM -0400, Theodore Ts'o wrote:
> > So what I am currently thinking might be a viable first step is to
> > split out the translations for e2fsprogs and transition from
> > Essential: yes to Essential: no, since there is no controversy over
> > that step.  We can then decide whether or not it's worthwhile to try
> > to make the Priority: required -> Priority -> important transition
> > during Buster or not.
> 
> It's been a long while, and non-traditional installations are becoming
> even more prevalent (e.g. the uptake in containers). I'm wondering what
> are your latest thoughts on the aforementioned Priority:
> required->important transition.
> 
> For what it's worth, looking at Helmut's nonessentiale2fsprogs bug
> reports¹, it looks like all are either resolved, minor
> (suggests/recommends), false positives, or unrelated.
> 
> This audit is 2½ years old at this point, so it's possible more have
> creeped in since. I'm sure it's within reach for someone to rerun this
> and for us all to fix all the remaining occurences (if any), but not
> sure if there is much point for someone to go down that path unless
> changing the priority is something you'd be willing to do.
> 
> Also: the timing of the bullseye freeze is going to make this
> interesting; at worst we can start the work now and execute at the
> beginning of the bookworm cycle.
> 
> Do you see any other issues? Anything I missed?

I haven't received a response for this. We are now at the beginning of
the aforementioned bookworm cycle, so I thought it may be a good
opportunity to bump this :) Do you have any thoughts?

Thanks!
Faidon

Bug#992376: systemd-standalone-{sysusers, tmpfiles}: missing Breaks+Replaces: systemd (<< 249.3-2)

[Andreas Beckmann]

On 18/08/2021 00.41, Michael Biebl wrote:

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.


There is no version of systemd-standalone-* in sid so how can it fail an 
upgrade from sid to experimental?


Please suggest a better wording for the bug template that also covers 
this case of package splits with insufficient B+R.


Andreas

Bug#992334: blhc: False positive with ff-c++ from FreeFEM++ package

[François Mazen]

Hi Eriberto,

thanks for the pointer and the examples, and sorry for the noise!

Have a nice day,
François



Le mardi 17 août 2021 à 11:23 -0300, Eriberto Mota a écrit :
> Hi Francois,
> 
> blhc has a mechanism to  ignore false positives. Please, search for
> "FALSE POSITIVES" in manpage (man blhc) and see some examples
> here[1].
> 
> [1]
> https://codesearch.debian.net/search?q=blhc%3A+ignore-line-regexp=1=1
> 
> I am closing this bug. Feel free to reopen if needed.
> 
> Regards,
> 
> Eriberto



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

Bug#992376: systemd-standalone-{sysusers, tmpfiles}: missing Breaks+Replaces: systemd (<< 249.3-2)

[Michael Biebl]

Control: tags -1 + moreinfo

Am 18.08.2021 um 00:33 schrieb Andreas Beckmann:

Package: systemd-standalone-sysusers,systemd-standalone-tmpfiles
Version: 249.3-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.


There is no version of systemd-standalone-* in sid so how can it fail an 
upgrade from sid to experimental?

Bug#992376: systemd-standalone-{sysusers,tmpfiles}: missing Breaks+Replaces: systemd (<< 249.3-2)

[Andreas Beckmann]

Package: systemd-standalone-sysusers,systemd-standalone-tmpfiles
Version: 249.3-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

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

  Preparing to unpack .../systemd-standalone-sysusers_249.3-3_amd64.deb ...
  Unpacking systemd-standalone-sysusers (249.3-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/systemd-standalone-sysusers_249.3-3_amd64.deb 
(--unpack):
   trying to overwrite '/bin/systemd-sysusers', which is also in package 
systemd 247.9-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/systemd-standalone-sysusers_249.3-3_amd64.deb

  Preparing to unpack .../systemd-standalone-tmpfiles_249.3-3_amd64.deb ...
  Unpacking systemd-standalone-tmpfiles (249.3-3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/systemd-standalone-tmpfiles_249.3-3_amd64.deb 
(--unpack):
   trying to overwrite '/bin/systemd-tmpfiles', which is also in package 
systemd 247.9-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/systemd-standalone-tmpfiles_249.3-3_amd64.deb


249.3-2 seems to be the version that split out the two packages,
please adjust the version for the B+R if needed.


cheers,

Andreas
# Partial distribution upgrade
# * install sid: systemd (247.9-1)
# * pick experimental: systemd-standalone-sysusers (249.3-3)

0m0.0s INFO: 
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of 
this logfile.
0m0.0s INFO: FAQ available at https://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: The FAQ also explains how to contact us in case you think piuparts 
is wrong.
0m0.0s INFO: 
--
0m0.0s INFO: piuparts version 1.0.1~202108170201~0.95-51460-g807134c85 starting 
up.
0m0.0s INFO: Command line arguments: /srv/piuparts/sbin/piuparts 
--no-upgrade-test --warn-on-leftovers-after-purge --skip-logrotatefiles-test 
--scriptsdir /etc/piuparts/scripts/ --tmpdir /tmp/piupartss/dose --mirror 
http://ftp.de.debian.org/debian --basetgz 
/srv/piuparts/slave/basetgz/sid_amd64.tar.gz -d sid -i /etc/nsswitch.conf 
--log-file /tmp/tmp.f13PkTTlRJ --scriptsdir /tmp/tmp.ALTjEHowzD --apt hello
0m0.0s INFO: Running on: Linux zam378 5.10.40 #1 SMP Mon May 31 11:35:20 CEST 
2021 x86_64
0m0.0s DEBUG: Created temporary directory /tmp/piupartss/dose/tmpTXXz9I/chroot
0m0.0s DEBUG: Unpacking /srv/piuparts/slave/basetgz/sid_amd64.tar.gz into 
/tmp/piupartss/dose/tmpTXXz9I/chroot
0m0.0s DEBUG: Starting command: ['eatmydata', 'tar', '-C', 
'/tmp/piupartss/dose/tmpTXXz9I/chroot', '-zxf', 
'/srv/piuparts/slave/basetgz/sid_amd64.tar.gz']
0m1.1s DEBUG: Command ok: ['eatmydata', 'tar', '-C', 
'/tmp/piupartss/dose/tmpTXXz9I/chroot', '-zxf', 
'/srv/piuparts/slave/basetgz/sid_amd64.tar.gz']
0m1.1s DEBUG: Starting command: ['mount', '-t', 'proc', 'proc', 
'/tmp/piupartss/dose/tmpTXXz9I/chroot/proc']
0m1.1s DEBUG: Command ok: ['mount', '-t', 'proc', 'proc', 
'/tmp/piupartss/dose/tmpTXXz9I/chroot/proc']
0m1.1s DEBUG: Starting command: ['mount', '-t', 'devpts', '-o', 
'newinstance,noexec,nosuid,gid=5,mode=0620,ptmxmode=0666', 'devpts', 
'/tmp/piupartss/dose/tmpTXXz9I/chroot/dev/pts']
0m1.1s DEBUG: Command ok: ['mount', '-t', 'devpts', '-o', 
'newinstance,noexec,nosuid,gid=5,mode=0620,ptmxmode=0666', 'devpts', 
'/tmp/piupartss/dose/tmpTXXz9I/chroot/dev/pts']
0m1.1s DEBUG: Starting command: ['mount', '-o', 'bind', 
'/tmp/piupartss/dose/tmpTXXz9I/chroot/dev/pts/ptmx', 
'/tmp/piupartss/dose/tmpTXXz9I/chroot/dev/ptmx']
0m1.1s DEBUG: Command ok: ['mount', '-o', 'bind', 
'/tmp/piupartss/dose/tmpTXXz9I/chroot/dev/pts/ptmx', 
'/tmp/piupartss/dose/tmpTXXz9I/chroot/dev/ptmx']
0m1.1s DEBUG: Starting command: ['mount', '-o', 'bind', '/dev/pts/26', 
'/tmp/piupartss/dose/tmpTXXz9I/chroot/dev/console']
0m1.1s DEBUG: Command ok: ['mount', '-o', 'bind', '/dev/pts/26', 
'/tmp/piupartss/dose/tmpTXXz9I/chroot/dev/console']
0m1.1s DEBUG: Starting command: ['mount', '-t', 'tmpfs', '-o', 'size=65536k', 
'tmpfs', '/tmp/piupartss/dose/tmpTXXz9I/chroot/dev/shm']
0m1.1s DEBUG: Command ok: ['mount', '-t', 'tmpfs', '-o', 'size=65536k', 
'tmpfs', '/tmp/piupartss/dose/tmpTXXz9I/chroot/dev/shm']
0m1.1s DEBUG: Starting command: ['mount', '-t', 'sysfs', '-o', 
'nosuid,nodev,noexec', 'sysfs', '/tmp/piupartss/dose/tmpTXXz9I/chroot/sys']
0m1.1s DEBUG: 

Bug#983910: rpcsvc-proto: uninstallable due to Conflicts: libc6

[Andreas Beckmann]

Followup-For: Bug #983910
Control: found -1 1.4.2-2

>   * Replace the conflicts with libc6-dev by breaks + replaces on libc6-dev
> (<< 2.31-13).  Closes: #983910.

That is not sufficient:

  Selecting previously unselected package rpcsvc-proto.
  Preparing to unpack .../rpcsvc-proto_1.4.2-2_amd64.deb ...
  Unpacking rpcsvc-proto (1.4.2-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/rpcsvc-proto_1.4.2-2_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/rpcgen', which is also in package libc-dev-bin 
2.31-13
  Errors were encountered while processing:
   /var/cache/apt/archives/rpcsvc-proto_1.4.2-2_amd64.deb


Andreas

Bug#992347: open-iscsi on upgrades fail to finish postinst script

[Jose M Calhariz]

On Tue, Aug 17, 2021 at 11:13:36PM +0530, Ritesh Raj Sarraf wrote:
> Hello Jose,

Hi


> 
> Good to hear from you. I recollect having met you, in person, at
> Debconf Heidelberg or Debconf Capetown. I hope you are doing
> good. :-)


Yes, I am fine and you?  I was in both DebConfs but I remember meeting
you in Capetown.


> 
> On Tue, 2021-08-17 at 16:27 +0100, Jose M Calhariz wrote:
> > During upgrades of open-iscsi on my environment it fails to run
> > postinst with success.  I got the following messages:
> > 
> > Setting up open-iscsi (2.1.3-5) ...
> > open-iscsi postinst: since the check in preinst some iSCSI sessions
> > have
> >  failed. -> will wait 30s for automatic recovery
> > open-iscsi postinst: some sessions are still in failed state ->
> > iscsid
> >  will be restarted regardless, since that may
> >  actually help with the session recovery.
> > dpkg: error processing package open-iscsi (--configure):
> >  installed open-iscsi package post-installation script subprocess
> > returned error exit status 1
> > 
> > 
> > I have tried to change the postinst to wait for more time, for
> > example
> > 120s and it worked, after 40 seconds of wait.
> 
> Hmmm. Usually, the sessions should recover within a couple of seconds.
> IIRC, the check is every 5 seconds.
> 
> 
> Did you change/tweak any of the default timeout values ?
> 

Most probably, it is not me that usually setup the iSCSI connections.
What values do you want me to look into it and where?


Kind regards
Jose M Calhariz



-- 
--
É difícil dizer o que e impossivel, pois a fantasia de
ontem e a esperanca de hoje e a realidade de
amanha.
-- Robert H. Goddard


signature.asc
Description: PGP signature

Bug#992375: molly-brown: wrong package section: golang

[Jonas Smedegaard]

Package: molly-brown
Version: 0.0~git20210124.92cd40d-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package section should reflect what the package _does_, not how its source was 
composed.

Seems molly-brown belongs in package section net rather than golang.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmEcL50ACgkQLHwxRsGg
ASHyQg/+Pyvo1iYnx+6haDTrEi/qTUNWf+WfNWb3+Yq9U/NLlOJZiyZVh7mRBdB6
pIJ17JgxPJN0DufsBHeqqT19iWldt3BXsEaZdfw8YVtMsI4zCYNLEwkBmuiCq5dr
mN4AytOkE2ajwdQ69gxDGf0ZltZ4wDbtRQjCqOflRIQf6dmjgwCG2uU4T6tjH7QZ
OlSKZw0lAN9qfJPDzJSzO7Ch5mxPQJKfpp4GEhu2NWsauCtID2iE7Nfd12E16U3g
WlbS6Hc77CZyUdNMf/559EW/LlCX8QiX4X7I+9zcoRwVN/vpZgRX4qbfRv/HCUjm
5u5JEKHFqSgc0c/vBBnQAIfNBtIqfATOOwJB0BPAVlW6OsNSwGAlHV31lBR1xN9B
9Wrwkv1EoS7OPNuq5/cecmUTYm3ZDvcWEo2JDcLIWU7hr1k1byXEKAPVPsn3JKZJ
EBJItS+uWZhdYszEh/tzVUclNya5xcB4JVY2UWgfD3+0dFobsoClllIvKdv/2IWm
/0WRLTe0dw/HbcF/IOh3RimC3S3nDpHQthuTh3BfXFqZw9zi3Vc7W0xWObUrnnA3
XPd+egRu+Afw06m67VrtU+n3d128O6lhILxs6oYrrW3iGRCfHDhusnKP7aYMcW/E
Th9jf3uPHMp1uWBbmqprrkvBoGCuHXIHSUBPGNefeQOM3yt8tFw=
=vyf6
-END PGP SIGNATURE-

Bug#870395: hydrogen: Segmentation fault when creating or modifying drumkits

[Nicholas D Steeves]

Dear Roberto,

So sorry for the unreasonably long wait for a reply!  I confess to
taking a winter break from Debian around the time of your reply, and
then I was negligent in following up on non-RC bugs.  Sorry :-/

Reply follows inline:

Roberto  writes:

> Hi, thank you for adopting Hydrogen :)
>
> Yes, it still happens with 0.9.7-6 (not tried upstream git sources).
>

We now have the option of 1.0.1-3 on Bullseye (Debian 11) :-)  When you
have the time to upgrade to Bullseye, would you please update this bug
with your experience.

> Maybe the severity can be lowered, I've been using Hydrogen with the
> workaround of choosing samples in advance, never deleting layers when
> building an instrument, and it works. It seems that deleting a layer is
> the most risky task, probably when the sound is still playing.
>

That sounds like an unnecessarily cumbersome workaround, and I agree
that this bug is important :-) If two or more people could reproduce the
crash then I'd say it was an RC bug.  For what it's worth, I believe
that a hard to reproduce crash is *always* an important bug.

> Can't you reproduce it? It only took a few seconds to crash it, just a
> minute before writing this email. If this only happens to me, we could
> close the bug, though I wonder why are only my computers triggering the
> crash :/

I'm not sure why it crashes your system but not mine.  For what it's
worth, here is the setup on the system I record with: Jackdbus + the
PulseAudio jack bridge + custom 5.4 realtime kernel + Scarlett 2i2 (1st
gen) + rtirq.  I wonder if the reason you're able to trigger this issue
(I agree with your assessment and hypothesis, by the way) is because
your interface is taking slightly longer to process the packets/stream,
leading to a race->crash rather than a benign race?  If so, you have a
great setup for audio bug hunting! :-D

If you're comfortable installing individual packages from experimental,
and you're also able to reproduce the crash with 1.0.1-3 in Bullseye,
then would you please consider also testing 1.1.0~beta1-1~exp1 (from
experimental) to see if it's also affected?  If 1.1.0~beta1 is affected
then we'll need to contact upstream without delay, in the hopes of
getting the fix into the next stable release.

Kind regards, and sorry again for taking so long to reply,
Nicholas


signature.asc
Description: PGP signature

Bug#977486: sayonara: please make the build reproducible

[Boyuan Yang]

Control: tags -1 +fixed-upstream

The patch is forwarded upstream and applied in
https://gitlab.com/luciocarreras/sayonara-player/-/merge_requests/212 .

Thanks,
Boyuan Yang


On Tue, 15 Dec 2020 16:45:42 + "Chris Lamb"  wrote:
> Source: sayonara
> Version: 1.6.0~beta6+ds-1
> Severity: wishlist
> Tags: patch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: timestamps
> X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
> 
> Hi,
> 
> Whilst working on the Reproducible Builds effort [0] we noticed that
> sayonara could not be built reproducibly.
> 
> This is because it generated a manual page that included the current
> build date.
> 
> Patch attached that uses CMake's ability to respect the
> SOURCE_DATE_EPOCH environment variable [1].
> 
>  [0] https://reproducible-builds.org/
>  [1] https://reproducible-builds.org/specs/source-date-epoch/
> 
> 
> Regards,
> 
> -- 
>   ,''`.
>  : :'  : Chris Lamb
>  `. `'`  la...@debian.org / chris-lamb.co.uk
>    `-



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

Bug#992374: buster-pu: package nvidia-cuda-toolkit/9.2.148-7+deb10u1

[Andreas Beckmann]

Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

The ppc64el nvidia-cuda-toolkit package in buster does not ship the
customized nvcc.profile configuration file but the unmodified upstream
one which does not work with the FHS layout used by the Debian
packaging. #991592
Since some people actually use the ppc64el stable packages in production
environments, I'd like to fix that.

This problem is specific to the version in buster/ppc64el:
- newer releases (10+) don't provide incremental patch releases, they
  just release the full toolkit more frequently
- in newer (10+) toolkit releases, ppc64el has a .run installer like
  amd64, no more repacking of upstream .deb files needed

There is also some replacement of $< in debian/rules with the intended
value, since $< does not work for order-only prerequisites. (This only
affects verbose output, which contained a lot of incorrect noise.)

Andreas
diff --git a/debian/changelog b/debian/changelog
index cba0bf5..0bfbae6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+nvidia-cuda-toolkit (9.2.148-7+deb10u1) buster; urgency=medium
+
+  * [ppc64el]: Do not overwrite the customized nvcc.profile with the
+unmodified upstream copy from CUDA 9.2 Patch 1.  (Closes: #991592)
+
+ -- Andreas Beckmann   Tue, 17 Aug 2021 18:57:22 +0200
+
 nvidia-cuda-toolkit (9.2.148-7) unstable; urgency=medium
 
   * Use debianize.patch to customize paths etc. in nvcc.profile and the
diff --git a/debian/gbp.conf b/debian/gbp.conf
index 92b4ec0..db5c248 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -7,4 +7,4 @@ pristine-tar = False
 compression = gz
 tarball-dir = ../tarballs-nvidia-cuda-toolkit/%(version)s
 component = [ 'ppc64el', 'amd64-patch1', 'ppc64el-patch1', ]
-debian-branch = master
+debian-branch = buster
diff --git a/debian/rules b/debian/rules
index 7d28500..08ce2b6 100755
--- a/debian/rules
+++ b/debian/rules
@@ -65,7 +65,7 @@ nvidia-cuda-amd64-patch1: | nvidia-cuda-amd64
$(RM) -v $@.tmp/install_patch.pl
$(RM) -v $@.tmp/payload/install_manifest
mv $@.tmp $@
-   for f in $$(cd $@ && find . ! -type d) ; do test -e $

Bug#794042: hydrogen: Hydrogen segfault on adding from sound library

[Nicholas D Steeves]

Control: tags = unreproducible

Nicholas D Steeves  writes:
> On Wed, Jul 29, 2015 at 11:08:48PM -0400, Robbie Harwood wrote:
>> Package: hydrogen
>> Version: 0.9.6.1-1
>> Severity: important
>> 
>> Dear Maintainer,
>> 
>> Sporadically, hydrogen will crash.  This seems to be co-incident with adding
>> instruments to the current loop.  Here is a traceback:
>> 
>> Program received signal SIGABRT, Aborted.
>
> I recently adopted Hydrogen for Debian, and see that no one followed
> up on this bug.  0.9.7-1+b1 from Debian 9 (stretch) is the oldest
> supported release, but the oldest version I am able to test is
> 0.9.7-6, and I was not able to trigger this crash there.
>
> Please confirm if the issue still exists.  Without any communication I
> plan to close this bug in six months, or when Debian 11 (bullseye) is
> released.
>
> Thank you,
> Nicholas

Bullseye was released.  If this segfault can be reproduced on a
supported Debian release, then please file a new bug.

Thank you,
Nicholas


signature.asc
Description: PGP signature

Bug#992373: ITP: golang-github-mendersoftware-progressbar -- Minimal progressbar used in Mender projects

[Andreas Henriksson]

Package: wnpp
Severity: wishlist
Owner: Andreas Henriksson 

* Package name: golang-github-mendersoftware-progressbar
  Version : 0.0.3-1
  Upstream Author : Mender
* URL : https://github.com/mendersoftware/progressbar
* License : Apache-2.0
  Programming Lang: Go
  Description : Minimal progressbar used in Mender projects

 Progressbar: A simple and minimalistic Golang progressbar
 for Mendersoftware projects.
 .
 This is a dependency for updating the mender-client package to
 new upstream release 3.0.0.

Bug#992372: kst: Dirfile data sources (via libgetdata) are no longer recognized

[Graeme Smecher]

Package: kst
Version: 2.0.8-4+b1
Severity: important

Dear Maintainer,

KST used to recognize dirfile data sources via libgetdata. However, sometime
since I last used it (perhaps several years) it stopped. Dirfile is no longer
recognized in the data wizard.

In previous installations, I think this happened when libgetdata was not
installed. However, I've installed everything libgetdata-ish I can find and do
not see any change in behaviour.

I've just cross-checked against Ubuntu 20.04 and dirfiles are still recognized
there under the same conditions.

best,
Graeme



-- System Information:
Debian Release: 11.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.9.0-2-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kst depends on:
ii  libc62.31-11
ii  libcfitsio9  3.490-3
ii  libgcc-s110.2.1-6
ii  libgetdata++70.10.0-10
ii  libgsl25 2.6+dfsg-2
ii  libmatio11   1.5.19-2
ii  libqt5core5a 5.15.2+dfsg-5
ii  libqt5gui5   5.15.2+dfsg-5
ii  libqt5network5   5.15.2+dfsg-2
ii  libqt5printsupport5  5.15.2+dfsg-2
ii  libqt5widgets5   5.15.2+dfsg-2
ii  libqt5xml5   5.15.2+dfsg-5
ii  libstdc++6   10.2.1-6

Versions of packages kst recommends:
ii  kst-doc  2.0.8-4

kst suggests no packages.

-- no debconf information

Bug#992370: debhelper: Unexpected error in dpkg-deb (maintscript postinst permission). Regression?

[Boyuan Yang]

Package: debhelper
Version: 13.4
Severity: normal
X-Debbugs-CC: ni...@thykier.net

Dear debhelper maintainers,

After upgraded to debhelper 13.4, the following error always pops up even if I
did not wrote any postinst script under debian/ directory:

dpkg-deb: building package 'alltray-dbgsym' in '../alltray-dbgsym_0.71b-
2_amd64.deb'.
dpkg-deb: error: maintainer script 'postinst' has bad permissions 1363 (must
be >=0555 and <=0775)
dh_builddeb: error: dpkg-deb --build debian/alltray .. returned exit code 2
dh_builddeb: error: Aborting due to earlier error
make: *** [debian/rules:4: binary] Error 25

Downgrading to debhelper 13.3.4 solves the problem.




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

Bug#992371: transition: opensubdiv

[Matteo F. Vescovi]

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

Hi Release Team!

Following advice/request from fellow DD elbrus, I'm filing this
transition bug report to track down the one-package transition of
opensubdiv library.

The only reverse dependency for osd is blender, as in [1];
I've already test-built it to check any FTBFS and it builds fine.

Thanks for your time and patience.

mfv


[1] https://release.debian.org/transitions/html/auto-opensubdiv.html

Ben file:

title = "opensubdiv";
is_affected = .depends ~ "libosdcpu3.4.3" | .depends ~ "libosdgpu3.4.3" | 
.depends ~ "libosdcpu3.4.4" | .depends ~ "libosdgpu3.4.4";
is_good = .depends ~ "libosdcpu3.4.4" | .depends ~ "libosdgpu3.4.4";
is_bad = .depends ~ "libosdcpu3.4.3" | .depends ~ "libosdgpu3.4.3";


-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A


signature.asc
Description: PGP signature

Bug#992286: | dependency?

[Joseph Carter]

If not a switchover to the Samsung-written tools outright, perhaps an | 
dependency?

Joseph

Bug#992369: base-files: Release of a 12.x version now that bullseye has been released?

[Roland Clobus]

Package: base-files
Version: 11.1
Severity: normal

Hello maintainers of base-files,

now that bullseye has been released, would it be suitable to release a 12.x
version of base-files to unstable/testing?

I'm using 'unattended-upgrades' with testing, and that tool uses the
information from /etc/debian_version to decide which packages are eligible for
an upgrade.

With kind regards,
Roland Clobus

-- System Information:
Debian Release: 11.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages base-files depends on:
ii  gawk [awk]  1:5.1.0-1
ii  mawk [awk]  1.3.4.20200120-2

base-files recommends no packages.

base-files suggests no packages.

Bug#964785: I'd like to create a shutter package and add it to the Debian package.

[Michael Kogan]

I see, thanks for clarifying this! We have documented the dependencies
here: https://shutter-project.org/downloads/dependencies/ Most of them are
actually named in Debian/Ubuntu naming style, as far as I know.

As jiho lee already mentioned, it would be necessary to package
https://metacpan.org/dist/GooCanvas2-CairoTypes and add it as dependency.

The dependency gir1.2-appindicator3-0.1 is necessary for core functionality
(showing the tray icon) but only for Gnome users. Don't know what the best
way to deal with this is... In the Ubuntu PPA this is a "Recommended"
dependency, in Arch Linux an optional one.

Am Di., 17. Aug. 2021 um 22:30 Uhr schrieb Andrej Shadura :

> Hi
>
> Unfortunately, that packaging isn’t well-commented, so it’s not easy to
> verify what exactly is needed and what isn’t.
> It would be much better if you as the upstream documented the exact
> dependencies and other requirement, preferably in some standard format e.g.
> (probably? I’m not a Perl expert) META.yml or something, or at least in the
> README file.
>
> --
> Cheers,
>   Andrej
>
>

Bug#992368: RM: dash-functional-el -- ROM; functionality absorbed into elpa-dash

[Sean Whitton]

Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: debian-emac...@lists.debian.org

Hello,

Please remove dash-functional-el.  Per [1], its functionality has been
absorbed back into bin:elpa-dash, which now "Provides: elpa-dash-functional".

[1]  https://github.com/magnars/dash.el/wiki/Obsoletion-of-dash-functional.el

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#992367: ITP: flake8-builtins -- Check for python builtins being used as variables or parameters

[Jose Luis Rivero]

Package: wnpp
Severity: wishlist
Owner: Jose Luis Rivero 

* Package name: flake8-builtins
  Version : 1.5.3
  Upstream Author : Gil Forcada Codinachs
* URL : https://github.com/gforcada/flake8-builtins
* License : GPL2
  Programming Lang: Python
  Description : Check for python builtins being used as variables or 
parameters


Part of the available set of extensions for flake8

Bug#976960: Could the decision on systemd-userdbd and systemd-homed be reconsidered - IDMAPPED?

[Eugen Stan]

Hello,

Could the decision on packaging systemd-userdbd and systemd-homed be 
reconsidered?


There is also IDMAPPED functionality in the linux kernel targeted at 
fixing some of the current issues


https://www.phoronix.com/scan.php?page=news_item=IDMAPPED-Mounts-Linux-5.12

I for example would use this functionality on my desktop where I don't 
mind the downsides but I think that the new IDMAPPED functionality would 
also make homed more appealing.


Regards,
Eugen

Bug#964785: I'd like to create a shutter package and add it to the Debian package.

[Andrej Shadura]

Hi

On Tue, 17 Aug 2021, at 18:08, Michael Kogan wrote:
> logix2 has taken over the maintenance for the official Ubuntu PPA at 
> https://launchpad.net/~shutter/+archive/ubuntu/ppa/+packages?field.name_filter=_filter=published_filter=hirsute
>  recently.
> 
> I assume that the package names are valid for Debian as well, so the package 
> most probably could be reused for Debian with only minor modifications. 
> Here's a direct link to the actual Shutter package: 
> https://launchpad.net/~shutter/+archive/ubuntu/ppa/+sourcefiles/shutter/0.98-1~1ppa1~hirsute0/shutter_0.98-1~1ppa1~hirsute0.debian.tar.xz

Unfortunately, that packaging isn’t well-commented, so it’s not easy to verify 
what exactly is needed and what isn’t.
It would be much better if you as the upstream documented the exact 
dependencies and other requirement, preferably in some standard format e.g. 
(probably? I’m not a Perl expert) META.yml or something, or at least in the 
README file.

-- 
Cheers,
  Andrej

Bug#992366: ITP: flake8-blind-except -- A flake8 extension that checks for blind, catch-all except: and except Exception: statements.

[Jose Luis Rivero]

Package: wnpp
Severity: wishlist
Owner: Jose Luis Rivero 

* Package name: flake8-blind-except
  Version : 0.2.0
  Upstream Author : Elijah Andrews 
* URL : https://github.com/elijahandrews/flake8-blind-except
* License : MIT
  Programming Lang: python
  Description : A flake8 extension that checks for blind, catch-all except: 
and except Exception: statements.


As of pycodestyle 2.1.0, "E722 do not use bare except, specify exception
instead" is built-in. However, bare Exception and BaseException are
still allowed. This extension flags them as B902.

Using except without explicitly specifying which exceptions to catch is
generally considered bad practice, since it catches system signals like
SIGINT. You probably want to handle system interrupts differently than
exceptions occuring in your code.

It's also usually better style to have many small try-except blocks
catching specific exceptions instead of a giant try: block with a
catch-all except: at the bottom. It's also nicer to your fellow
programmers to be a bit more specific about what exceptions they can
expect in specific parts of the code, and what the proper course of
action is when they occur.

Bug#992365: ITP: ignition-plugin -- Library for registering plugin libraries and dynamically loading them at runtime

[Jose Luis Rivero]

Package: wnpp
Severity: wishlist
Owner: Jose Luis Rivero 

* Package name: ignition-plugin
  Version : 1.2.0
  Upstream Author : Open Robotics
* URL : https://github.com/ignitionrobotics/ign-plugin/
* License : Apache-2
  Programming Lang: C++
  Description : Library for registering plugin libraries and dynamically 
loading them at runtime


Library for registering plugin libraries and dynamically loading them at 
runtime.
Ignition Plugin is a component in the ignition framework, a set of libraries 
designed to rapidly develop robot applications.

Bug#989489: Good one sir

[Cézar]

That's one small step for a man and one giant step for bringing elmentary's 
desktop to Debian.

Bug#992363: qmenumodel FTBFS with recent glib2.0: error: template with C linkage

[Helmut Grohne]

Source: qmenumodel
Version: 0.8.0-2
Tags: ftbfs
X-Debbugs-Cc: Simon McVittie 

example error from a build log:

| In file included from /usr/include/glib-2.0/glib/gatomic.h:31,
|  from /usr/include/glib-2.0/glib/gthread.h:32,
|  from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
|  from /usr/include/glib-2.0/glib.h:32,
|  from /usr/include/glib-2.0/gobject/gbinding.h:28,
|  from /usr/include/glib-2.0/glib-object.h:22,
|  from 
/<>/libqmenumodel/src/qmenumodelevents.cpp:21:
| /usr/include/c++/10/type_traits:2925:3: error: template with C linkage
|  2925 |   template
|   |   ^~~~
| /<>/libqmenumodel/src/qmenumodelevents.cpp:20:1: note: ‘extern 
"C"’ linkage started here
|20 | extern "C" {
|   | ^~

Also seen by crossqa:
http://crossqa.debian.net/build/qmenumodel_0.8.0-2_armel_20210817195636.log

Similar bug with more details: #992246

Helmut

Bug#992362: release-notes: Out of step wuth apt maintainers

[Brian Potkin]

Package: release-notes
Severity: normal


Please see

  https://lists.debian.org/debian-doc/2021/08/msg00077.html

Then look at

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

How abut a bit of consistency?

-- 
Brian.

Bug#992334: blhc: False positive with ff-c++ from FreeFEM++ package

[Eriberto]

To help you a bit more... Note that debian/rules will write an
'ignore' line in the .build file. Considering your package has a long
time building process, to test, you can manually write a similar line
in .build and test using 'blhc --all --debian .build', before
changing the debian/rules. See below an example about what write in
.build file (see the middle line):

Makefile:894: warning: ignoring prerequisites on suffix rule definition
blhc: ignore-line-regexp: eval\ \./ff-c\+\+\ .*\.cpp.*
eval ./ff-c++ tetgen.cpp -ltet

Cheers,

Eriberto

Bug#992361: O: python-slip

[Michael Biebl]

Package: wnpp
Severity: normal
X-Debbugs-Cc: python-modules-t...@lists.alioth.debian.org, bi...@debian.org
Control: affects -1 src:python-slip

Hi,

I'm orphaning the python-slip package.
In the past, it was a dependency of firewalld, which is why I packaged
it for Debian.
Starting with firewalld 1.0, it no longer depends on python-slip [1].
I'm therefor orphaning the package.
The last upstream release is from 2017, upstream appears to be not that
active [2].

I've CCed the Python modules team, maybe they have an interest in taking
over the package.
I already asked Laurent Bigonville, the maintainer of selinux-dbus and
selinux-python (the remaining rdeps of python-slip), but he suggested to
orphan the package.

Regards,
Michael


[1] https://github.com/firewalld/firewalld/pull/793
[2] https://github.com/nphilipp/python-slip/commits/master

Bug#992347: open-iscsi on upgrades fail to finish postinst script

[Jose M Calhariz]

Package: open-iscsi
Version: 2.1.3-5
Severity: normal

During upgrades of open-iscsi on my environment it fails to run
postinst with success.  I got the following messages:

Setting up open-iscsi (2.1.3-5) ...
open-iscsi postinst: since the check in preinst some iSCSI sessions have
 failed. -> will wait 30s for automatic recovery
open-iscsi postinst: some sessions are still in failed state -> iscsid
 will be restarted regardless, since that may
 actually help with the session recovery.
dpkg: error processing package open-iscsi (--configure):
 installed open-iscsi package post-installation script subprocess returned 
error exit status 1


I have tried to change the postinst to wait for more time, for example
120s and it worked, after 40 seconds of wait.

Kind regards
Jose M Calhariz


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

Kernel: Linux 5.10.0-7-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8), LANGUAGE=en_IL:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages open-iscsi depends on:
ii  debconf [debconf-2.0]  1.5.77
ii  libc6  2.31-13
ii  libisns0   0.100-3
ii  libkmod2   28-1
ii  libmount1  2.36.1-8
ii  libopeniscsiusr2.1.3-5
ii  libssl1.1  1.1.1k-1
ii  libsystemd0247.3-6
ii  udev   247.3-6

open-iscsi recommends no packages.

open-iscsi suggests no packages.

-- debconf information:
  open-iscsi/upgrade_recovery_error:
  open-iscsi/upgrade_even_with_failed_sessions:
  open-iscsi/downgrade_and_break_system:
  open-iscsi/remove_even_with_active_sessions:

Bug#970380: xrdp: Newer version (0.9.14) available

[Link, Bruce]

I'd like to add that as per 
https://ddei5-0-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fneutrinolabs%2fxorgxrdp%2fissues%2f156=503431C4-C9C6-2805-86D7-D38FC443EA39=2628ad18b21f934c4a3f3bcb7fa326f6a4758e66-ee2307a34be4246e304542e194cb071a22ba5149,
 that Debian Bullseye is broken out of the box with the current version of xrdp 
and xorgxrdp installed. Migrating these to 0.9.14 corrects this issue.

Bug#992345: www.debian.org: bullseye release-notes are misleading about the needed disk space

[Vincent Lefevre]

Hi Cyril,

On 2021-08-17 18:01:44 +0200, Cyril Brulebois wrote:
> Hi Vincent,
> 
> Vincent Lefevre  (2021-08-17):
> > 649 upgraded, 113 newly installed, 11 to remove and 1 not upgraded.
> > Need to get 455 MB of archives.
> > After this operation, 558 MB of additional disk space will be used.
> > 
> > and I had around 650 MB free space
> 
> 455+558 >> 650 so it was very unlikely to work?

This is what I was wondering initially, but the release notes say:

  If you do not have enough space for the upgrade, apt will warn you
  with a message like this:
  E: You don't have enough free space in /var/cache/apt/archives/.

i.e. if the test was 455+558 < 650, the lack of space would be
detectable by apt, so that I should have got a warning. Since I
didn't get the warning, I supposed that the 455 MB were included in
the 558 MB (the last message is not clear: "additional disk space"
compared to the status before or after the download?).

> > I suspect that some packages like this one need a lot of temporary
> > disk space (could this be related to initrd before compression?).
> > But there is nothing about that in the release notes. And perhaps
> > a warning should have been output by apt.
> 
> There's one for the directory where debs are downloaded (which you
> didn't get since 455 << 650), but I suspect it's harder to estimate
> where the whole “additional disk space” is going to end up,
> depending on file system layout, etc.?

The text from the release notes clearly says "for the upgrade", not
"for the download of the archives". Thus the comparison would have
been 455+558 vs 650 if 455 is not included in the 558. Perhaps it
should assume that everything goes to the same partition since
AFAIK, this is the most common case (optionally check whether
/var/cache/apt/archives and / are on different partitions); this
is just a warning after all.

In my case, there's a second disk, but mounted on /srv. So this
shouldn't count.

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

Bug#992334: blhc: False positive with ff-c++ from FreeFEM++ package

[Eriberto]

Em ter., 17 de ago. de 2021 às 16:10, François Mazen  escreveu:
>
> Hi Eriberto,
>
> thanks for the pointer and the examples, and sorry for the noise!

You're welcome.

Bug#947261: ITP: python-poetry -- Python dependency management and packaging made easy

[Taihsiang Ho (tai271828)]

Hi Emmanuel,

Thank you for the update. Is this the DPT thread?
https://lists.debian.org/debian-python/2021/06/msg00017.html
If yes, I will give it a try and update my progress on the thread.

Cheers,
Tai

On Sun, Jun 20, 2021 at 12:12 AM Emmanuel Arias  wrote:

> Hello!
>
> On 6/17/21 6:00 PM, Taihsiang Ho (tai271828) wrote:
> > Hi Emmanuel,
> >
> > I can help as a poetry user for a while if you don't mind. It seems that
> I
> > could reproduce the pytest-mock issue by building this poetry deb
> source[1]
> > with Ubuntu 21.04. For better communication, I am wondering the following
>
> I fixed with this patch [0].
>
> I guess I finished a first complete package of poetry. Please look in
> the DPT
> mailing list.
>
>
> [0]
>
> https://salsa.debian.org/python-team/packages/poetry/-/blob/debian/master/debian/patches/0002-Fix-incompatibility-between-pytest-and-pytest-mock.patch
>
> Cheers
>
> --
> Emmanuel Arias
> @eamanu
> yaerobi.com
>
>

Bug#992192: cpio RCE Exploit Caused by Integer Overflow

[Diederik de Haas]

Looks very much like the same issue as mentioned here:
https://lists.gnu.org/archive/html/bug-cpio/2021-08/msg5.html

On Debian, the new problem is tracked at https://bugs.debian.org/992192 which 
is a 'continuation' of https://bugs.debian.org/992098

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

Bug#992360: xfce4-notes missing from bullseye

[Alan Burlison]

Package: xfce4-notes
Severity: serious
Justification: 3

Dear Maintainer,

   * What led up to the situation?
 Upgrade from buster to bullseye

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 standard upgrade procedure

   * What was the outcome of this action?
 xfce4-notes no longer available post upgrade.
 Tried manual reinstallation with the following results:

 # apt install xfce4-notes
 Reading package lists... Done
 Building dependency tree... Done
 Reading state information... Done
 Package xfce4-notes is not available, but is referred to by another
package.
 This may mean that the package is missing, has been obsoleted, or
 is only available from another source

 E: Package 'xfce4-notes' has no installation candidate
 #

   * What outcome did you expect instead?
 xfce4-notes still to be installed

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

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xfce4-notes depends on:
ii  libc6   2.31-13
ii  libcairo2   1.16.0-5
ii  libgdk-pixbuf2.0-0  2.40.2-2
ii  libglib2.0-02.66.8-1
ii  libgtk2.0-0 2.24.33-2
ii  libpango-1.0-0  1.46.2-3
pn  libunique-1.0-0 
ii  libx11-62:1.7.2-1
ii  libxfce4ui-1-0  4.12.1-3
ii  libxfce4util7   4.16.0-1
ii  libxfconf-0-2   4.12.1-1

xfce4-notes recommends no packages.

Bug#992300: ca-certificates: ca-certificate update fails because of missing /usr/bin/cert-sync

[Alex]

Am 17.08.21 um 16:32 schrieb Michael Shuler:
> Control: notfound -1 20210119
> Control: reassign -1 ca-certificates-mono
> Control: tags -1 + moreinfo
> 
> On 8/16/21 4:58 PM, Alex wrote:
>> ...
>> Updating Mono key store
>> /etc/ca-certificates/update.d/mono-keystore: 10: /usr/bin/cert-sync:
>> not found
>> Done
> 
> Reassigning to appropriate package, ca-certificates-mono.
> 
> Bug reporter's ca-certificates-mono version is unknown, but it appears
> that #902663 with the same error report was fixed in
> ca-certificates-mono 5.18.0.240+dfsg-2. Please, update bug report with
> the proper "found" version.

I am not sure if ca-certificates-mono was installed at all. I do not
have mono on the system.

$ dpkg -l|grep mono|grep -v fonts-|grep -v python3-monotonic
rc  ca-certificates-mono 4.6.2.7+dfsg-1
all  Common CA certificates (Mono keystore)
rc  mono-runtime-common  4.6.2.7+dfsg-1
amd64Mono runtime - common files


$ ls /etc/ca-certificates/update.d/mono-keystore /usr/bin/cert-sync
ls: cannot access '/usr/bin/cert-sync': No such file or directory
/etc/ca-certificates/update.d/mono-keystore


$ grep ca-certificates /var/log/dpkg.log
2021-08-16 22:31:53 upgrade ca-certificates:all 20200601~deb10u2 20210119
2021-08-16 22:31:53 status half-configured ca-certificates:all
20200601~deb10u2
2021-08-16 22:31:53 status unpacked ca-certificates:all 20200601~deb10u2
2021-08-16 22:31:53 status half-installed ca-certificates:all
20200601~deb10u2
2021-08-16 22:32:13 status unpacked ca-certificates:all 20210119
2021-08-16 23:50:04 configure ca-certificates:all 20210119 
2021-08-16 23:50:04 status unpacked ca-certificates:all 20210119
2021-08-16 23:50:05 status half-configured ca-certificates:all 20210119
2021-08-16 23:50:12 status installed ca-certificates:all 20210119
2021-08-16 23:50:12 status triggers-pending ca-certificates:all 20210119
2021-08-16 23:55:15 trigproc ca-certificates:all 20210119 
2021-08-16 23:55:15 status half-configured ca-certificates:all 20210119
2021-08-16 23:55:18 status installed ca-certificates:all 20210119

$ grep mono /var/log/dpkg.log|grep -v python-monotonic|grep -v
python3-monotonic|grep -v fonts-noto-mono
(empty)

with kind regards,
Alex

Bug#992359: spdlog: Please package new upstream version (1.8.5)

[Boyuan Yang]

Source: spdlog
Severity: normal
Version: 1:1.8.1+ds-2.1
X-Debbugs-CC: cru...@debian.org

Dear Debian spdlog package maintainers,

Current version of spdlog in Debian is 1.8.1, and a new version of 1.8.5 is
now available. One of my packages (flameshot) needs spdlog/1.8.5 in the new
version. Could you please update spdlog to at least 1.8.5?

I see that the git packaging repo in Salsa GitLab already has a 1.8.5 version
prepared. It would be great if it can be packaged in near future. Please let
me know if I can provide with any help (such as package sponsorship).

Thanks,
Boyuan Yang


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

Bug#992358: transition: pdal

[Bas Couwenberg]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: pkg-grass-de...@lists.alioth.debian.org
Control: forwarded -1 https://release.debian.org/transitions/html/auto-pdal.html

PDAL 2.3.0 has been in experimental for quite a while, I'd like to move it to 
unstable now.

All reverse dependencies built successfully with the version in experimental as 
summarized below.


Transition: pdal

 libpdal-base12 (2.2.0+ds-1+b1) -> libpdal-base13 (2.3.0+ds-1~exp1)
 libpdal-util12 (2.2.0+ds-1+b1) -> libpdal-util13 (2.3.0+ds-1~exp1)

The status of the most recent rebuilds is as follows.

 cloudcompare (2.10.3-4) OK
 grass(7.8.5-1)  OK
 paraview (5.9.0-2)  OK


Kind Regards,

Bas

Bug#906474: ircp-tray: FTBFS in buster/sid (linux/irda.h: No such file or directory)

[Daniele Napolitano]

I'm the developer of ircp-tray. Sadly the IrDA support has been
removed from the kernel.

See the removal of irda-utils:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955337

-- 
Daniele Napolitano
dna...@gmail.com

Bug#992356: kde-config-gtk-style-preview: GTK style preview doesn't work

[Alex Volkov]

Package: kde-config-gtk-style-preview
Version: 4:5.20.5-2
Severity: important

Dear Maintainer,

the said package shows empty panel in systemsettings and gives

./gtk3_preview

(gtk3_preview:2216): dbind-WARNING **: 22:43:19.869: AT-SPI: Error retrieving 
accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.a11y.Bus was not provided by any .service files

** (gtk3_preview:2216): WARNING **: 22:43:19.869: Failed to open file “/usr/
share/kcm-gtk-module//preview.ui”: No such file or directory
free(): invalid pointer
Aborted

at the attempt to start by command line.


-- System Information:
Debian Release: 11.0
  APT prefers stable
  APT policy: (991, 'stable'), (500, 'stable-security'), (500, 'oldstable'), 
(99, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.194-bootes0-p-1000 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en_US
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages kde-config-gtk-style-preview depends on:
ii  libc6 2.31-13
ii  libglib2.0-0  2.66.8-1
ii  libgtk-3-03.24.24-4

Versions of packages kde-config-gtk-style-preview recommends:
ii  kde-config-gtk-style  4:5.20.5-2

kde-config-gtk-style-preview suggests no packages.

-- no debconf information

Bug#992357: kde-config-gtk-style-preview: GTK style preview doesn't work

[Alex Volkov]

Package: kde-config-gtk-style-preview
Version: 4:5.20.5-2
Severity: important

Dear Maintainer,

the said package shows empty panel in systemsettings and gives

./gtk3_preview

(gtk3_preview:2216): dbind-WARNING **: 22:43:19.869: AT-SPI: Error retrieving 
accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.a11y.Bus was not provided by any .service files

** (gtk3_preview:2216): WARNING **: 22:43:19.869: Failed to open file 
“/usr/share/kcm-gtk-module//preview.ui”: No such file or directory
free(): invalid pointer
Aborted

at the attempt to start by command line.


-- System Information:
Debian Release: 11.0
  APT prefers stable
  APT policy: (991, 'stable'), (500, 'stable-security'), (500, 'oldstable'), 
(99, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.194-bootes0-p-1000 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en_US
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages kde-config-gtk-style-preview depends on:
ii  libc6 2.31-13
ii  libglib2.0-0  2.66.8-1
ii  libgtk-3-03.24.24-4

Versions of packages kde-config-gtk-style-preview recommends:
ii  kde-config-gtk-style  4:5.20.5-2

kde-config-gtk-style-preview suggests no packages.

-- no debconf information

Bug#992355: ITP: r-cran-spatstat.linnet -- linear networks functionality of the 'spatstat' family of GNU R

[Andreas Tille]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-spatstat.linnet -- linear networks functionality of the 
'spatstat' family of GNU R
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: r-cran-spatstat.linnet
  Version : 2.3
  Upstream Author : Adrian Baddeley,
* URL : https://cran.r-project.org/package=spatstat.linnet
* License : GPL-2+
  Programming Lang: GNU R
  Description : linear networks functionality of the 'spatstat' family of 
GNU R
 Defines types of spatial data on a linear network and provides
 functionality for geometrical operations, data analysis and modelling
 of data on a linear network, in the 'spatstat' family of packages.
 Contains definitions and support for linear networks, including
 creation of networks, geometrical measurements, topological
 connectivity, geometrical operations such as inserting and deleting
 vertices, intersecting a network with another object, and interactive
 editing of networks. Data types defined on a network include point
 patterns, pixel images, functions, and tessellations. Exploratory
 methods include kernel estimation of intensity on a network, K-
 functions and pair correlation functions on a network, simulation
 envelopes, nearest neighbour distance and empty space distance,
 relative risk estimation with cross-validated bandwidth selection.
 Formal hypothesis tests of random pattern (chi-squared, Kolmogorov-
 Smirnov, Monte Carlo, Diggle-Cressie-Loosmore-Ford, Dao-Genton, two-
 stage Monte Carlo) and tests for covariate effects (Cox-Berman-Waller-
 Lawson, Kolmogorov-Smirnov, ANOVA) are also supported. Parametric
 models can be fitted to point pattern data using the function lppm()
 similar to glm(). Only Poisson models are implemented so far. Models
 may involve dependence on covariates and dependence on marks. Models
 are fitted by maximum likelihood. Fitted point process models can be
 simulated, automatically. Formal hypothesis tests of a fitted model are
 supported (likelihood ratio test, analysis of deviance, Monte Carlo
 tests) along with basic tools for model selection (stepwise(), AIC())
 and variable selection (sdr). Tools for validating the fitted model
 include simulation envelopes, residuals, residual plots and Q-Q plots,
 leverage and influence diagnostics, partial residuals, and added
 variable plots. Random point patterns on a network can be generated
 using a variety of models.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-spatstat.linnet

Bug#989087: rtw_8822ce and rtw_8821ce: firmware crash

[Clément CACHINHO]

Package: firmware-realtek
Version: 20210315-3
Followup-For: Bug #989087
X-Debbugs-Cc: clement.cachi...@gmail.com

Dear Maintainer,

Google translate: There is probably the same problem as for the rtw_8821ce. The
driver works several minutes before crashing for no apparent reason (no
relation to a strong use of the connection or a temporal regularity.) The
firmware problem has been present since version 5.x of the kernel (I have
noticed it on all testing version of bulleyes).
The only way to fix the problem is to restart the computer.

Original: Il y a probablement le même problème que pour le rtw_8821ce. Le
driver fonctionne plusieurs minutes avant de crash sans raison apparentes
(aucun rapport avec une forte utilisation de la connexion ou une régularité
temporelle.) Le problème du firmware est présent depuis les versions 5.x du
kernel (je l'ai constaté sur toutes les versions testing de bulleyes).
Le seul moyen de résoudre le problème est de redémarrer l'ordinateur.


Attached are the full crash logs.
Thanks in advance if you find a solution.
Cordially.

-- System Information:
Debian Release: 11.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

firmware-realtek depends on no packages.

firmware-realtek recommends no packages.

Versions of packages firmware-realtek suggests:
ii  initramfs-tools  0.140
Aug 17 18:57:19 LenovoDebian kernel: [  598.927259] rtw_8821ce :07:00.0: 
timed out to flush queue 2
Aug 17 18:57:19 LenovoDebian kernel: [  599.075248] rtw_8821ce :07:00.0: 
timed out to flush queue 2
Aug 17 18:57:52 LenovoDebian kernel: [  631.555980] rtw_8821ce :07:00.0: 
timed out to flush queue 1
Aug 17 18:57:52 LenovoDebian kernel: [  631.699972] rtw_8821ce :07:00.0: 
timed out to flush queue 2
Aug 17 18:57:52 LenovoDebian kernel: [  631.843936] rtw_8821ce :07:00.0: 
timed out to flush queue 1
Aug 17 18:57:52 LenovoDebian kernel: [  631.38] rtw_8821ce :07:00.0: 
timed out to flush queue 2
Aug 17 18:57:54 LenovoDebian kernel: [  634.283743] rtw_8821ce :07:00.0: 
timed out to flush queue 1
Aug 17 18:57:54 LenovoDebian kernel: [  634.427662] rtw_8821ce :07:00.0: 
timed out to flush queue 2
Aug 17 18:57:55 LenovoDebian kernel: [  634.575654] rtw_8821ce :07:00.0: 
timed out to flush queue 1
Aug 17 18:57:55 LenovoDebian kernel: [  634.715656] rtw_8821ce :07:00.0: 
timed out to flush queue 2
Aug 17 18:58:38 LenovoDebian wpa_supplicant[906]: wlp7s0: CTRL-EVENT-BEACON-LOSS
Aug 17 18:58:38 LenovoDebian kernel: [  677.827347] [ cut here 
]
Aug 17 18:58:38 LenovoDebian kernel: [  677.827350] failed to read DBI 
register, addr=0x0719
Aug 17 18:58:38 LenovoDebian kernel: [  677.827399] WARNING: CPU: 3 PID: 5035 
at drivers/net/wireless/realtek/rtw88/pci.c:1173 
rtw_dbi_read8.constprop.0+0xa0/0xb0 [rtw88_pci]
Aug 17 18:58:38 LenovoDebian kernel: [  677.827400] Modules linked in: rfcomm 
md4 sha512_ssse3 sha512_generic nls_utf8 cifs dns_resolver fscache libdes 
xt_CHECKSUM nft_chain_nat xt_MASQ>
Aug 17 18:58:38 LenovoDebian kernel: [  677.827460]  
soundwire_generic_allocation intel_rapl_msr rtw88_pci irqbypass bluetooth 
snd_soc_core squashfs rtw88_core snd_compress soundwire_ca>
Aug 17 18:58:38 LenovoDebian kernel: [  677.827528]  ip_tables x_tables autofs4 
ext4 crc16 mbcache jbd2 crc32c_generic btrfs xor raid6_pq libcrc32c hid_generic 
usbhid sd_mod i915 crc32_>
Aug 17 18:58:38 LenovoDebian kernel: [  677.827577] CPU: 3 PID: 5035 Comm: 
kworker/u16:3 Tainted: PW  OE 5.10.0-8-amd64 #1 Debian 5.10.46-4
Aug 17 18:58:38 LenovoDebian kernel: [  677.827579] Hardware name: LENOVO 
INVALID/INVALID, BIOS BGCN34WW 05/21/2021
Aug 17 18:58:38 LenovoDebian kernel: [  677.827624] Workqueue: phy0 
ieee80211_beacon_connection_loss_work [mac80211]
Aug 17 18:58:38 LenovoDebian kernel: [  677.827630] RIP: 
0010:rtw_dbi_read8.constprop.0+0xa0/0xb0 [rtw88_pci]
Aug 17 18:58:38 LenovoDebian kernel: [  677.827633] Code: be ed 03 00 00 48 8b 
40 50 e8 3c c2 ef de 5b 5d 41 88 04 24 31 c0 41 5c c3 be 19 07 00 00 48 c7 c7 
c0 83 f0 c2 e8 e3 45 b7 de <>
Aug 17 18:58:38 LenovoDebian kernel: [  677.827635] RSP: 0018:bd87c5fafd68 
EFLAGS: 00010286
Aug 17 18:58:38 LenovoDebian kernel: [  677.827637] RAX:  RBX: 
 RCX: 9aece64d8a08
Aug 17 18:58:38 LenovoDebian kernel: [  677.827639] RDX: ffd8 RSI: 
0027 RDI: 9aece64d8a00
Aug 17 18:58:38 LenovoDebian kernel: [  677.827640] RBP: 9aeba0371f00 R08: 
 R09: bd87c5fafb88
Aug 17 18:58:38 LenovoDebian kernel: [  

Bug#992347: open-iscsi on upgrades fail to finish postinst script

[Ritesh Raj Sarraf]

Hello Jose,

Good to hear from you. I recollect having met you, in person, at
Debconf Heidelberg or Debconf Capetown. I hope you are doing good. :-)

On Tue, 2021-08-17 at 16:27 +0100, Jose M Calhariz wrote:
> During upgrades of open-iscsi on my environment it fails to run
> postinst with success.  I got the following messages:
> 
> Setting up open-iscsi (2.1.3-5) ...
> open-iscsi postinst: since the check in preinst some iSCSI sessions
> have
>  failed. -> will wait 30s for automatic recovery
> open-iscsi postinst: some sessions are still in failed state ->
> iscsid
>  will be restarted regardless, since that may
>  actually help with the session recovery.
> dpkg: error processing package open-iscsi (--configure):
>  installed open-iscsi package post-installation script subprocess
> returned error exit status 1
> 
> 
> I have tried to change the postinst to wait for more time, for
> example
> 120s and it worked, after 40 seconds of wait.

Hmmm. Usually, the sessions should recover within a couple of seconds.
IIRC, the check is every 5 seconds.


Did you change/tweak any of the default timeout values ?


-- 
Ritesh Raj Sarraf | http://people.debian.org/~rrs
Debian - The Universal Operating System


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

Bug#992354: lesspipe: Look for user-defined filter in $XDG_CONFIG_HOME

[Jeffery To]

Package: less
Version: 551-2
Severity: wishlist

Currently, lesspipe looks for a user-defined filter in the user's home
directory only (~/.lessfilter).

This change allows the user-defined filter to be placed at
$XDG_CONFIG_HOME/lessfilter (or ~/.config/lessfilter if
$XDG_CONFIG_HOME is empty or not defined), falling back to
~/.lessfilter if the filter is not found.
commit ff12f0e26ae7b35d7c04e9fec47718aa289a98b0
Author: Jeffery To 
Date:   Wed Aug 18 01:13:30 2021 +0800

lesspipe: Look for user-defined filter in $XDG_CONFIG_HOME

Currently, lesspipe looks for a user-defined filter in the user's home
directory only (~/.lessfilter).

This change allows the user-defined filter to be placed at
$XDG_CONFIG_HOME/lessfilter (or ~/.config/lessfilter if $XDG_CONFIG_HOME
is empty or not defined), falling back to ~/.lessfilter if the filter is
not found.

diff --git a/debian/lesspipe b/debian/lesspipe
index 98224b0..14b33f6 100644
--- a/debian/lesspipe
+++ b/debian/lesspipe
@@ -25,6 +25,7 @@
 #$2  filename that was created during LESSOPEN
 
 TMPDIR=${TMPDIR:-/tmp}
+CONFIGDIR=${XDG_CONFIG_HOME:-~/.config}
 BASENAME=`basename $0`
 LESSFILE=lessfile
 
@@ -60,9 +61,13 @@ if [ $# -eq 1 ] ; then
 		if [ $BASENAME = $LESSFILE ]; then exec > $TMPFILE; fi
 
 		# Allow for user defined filters
-		#if [ -x ~/.lessfilter -a -O ~/.lessfilter ]; then
-		if [ -x ~/.lessfilter ]; then
-			~/.lessfilter "$1"
+		if [ -x "$CONFIGDIR/lessfilter" ]; then
+			USERFILTER="$CONFIGDIR/lessfilter"
+		elif [ -x ~/.lessfilter ]; then
+			USERFILTER=~/.lessfilter
+		fi
+		if [ -n "$USERFILTER" ]; then
+			"$USERFILTER" "$1"
 			if [ $? -eq 0 ]; then
 if [ $BASENAME = $LESSFILE ]; then
 	if [ -s $TMPFILE ]; then

Bug#964785: I'd like to create a shutter package and add it to the Debian package.

[Michael Kogan]

logix2 has taken over the maintenance for the official Ubuntu PPA at
https://launchpad.net/~shutter/+archive/ubuntu/ppa/+packages?field.name_filter=_filter=published_filter=hirsute
recently.

I assume that the package names are valid for Debian as well, so the
package most probably could be reused for Debian with only minor
modifications. Here's a direct link to the actual Shutter package:
https://launchpad.net/~shutter/+archive/ubuntu/ppa/+sourcefiles/shutter/0.98-1~1ppa1~hirsute0/shutter_0.98-1~1ppa1~hirsute0.debian.tar.xz

Am Di., 17. Aug. 2021 um 13:30 Uhr schrieb jiho lee :

> Hi Andrej Shadura
>
> There is one package that I couldn't put in the control file. This package
> is a https://metacpan.org/dist/GooCanvas2-CairoTypes package. This
> package is essential for shutter use and is not currently packaged in the
> debian.
>
> 
> 
> There is a future society, but my future is not what others do.
> Dept. of Information Science, Graduate School, Korea National Open
> University
>
>
> 2021년 8월 17일 (화) 오후 8:27, Andrej Shadura 님이 작성:
>
>> Hi Michael,
>>
>> On Tue, 17 Aug 2021, at 12:22, Michael Kogan wrote:
>>
>> Thanks for your work on the Shutter package! I'm member of the Shutter
>> team (upstream), if there are any doubts or issues, please let me know here
>> or post a question at
>> https://github.com/shutter-project/shutter/issues/new/choose
>>
>>
>> It would be great if you could verify the list of dependencies in Jiho’s
>> package (the control file).
>>
>> Here’s the word diff compared to the dependencies of the old 0.94 version:
>>
>> Depends:
>> [-imagemagick,-]
>> [- libfile-basedir-perl,-]{+gir1.2-appindicator3-0.1,+}
>> {+ libcarp-always-perl,+}
>> {+ libextutils-depends-perl,+}
>> libfile-copy-recursive-perl,
>> [-libfile-which-perl,-]
>> [- libglib-perl,-]
>> [- libgnome2-canvas-perl,-]
>> [- libgnome2-gconf-perl,-]
>> [- libgnome2-perl,-]
>> [- libgnome2-vfs-perl,-]
>> [- libgnome2-wnck-perl,-]
>> [- libgtk2-imageview-perl,-]
>> [- libgtk2-perl,-]
>> [- libgtk2-unique-perl,-]{+libgoocanvas2-perl,+}
>> {+ libgtk3-perl,+}
>> libimage-magick-perl,
>> [-libjson-perl,-]
>> [- libjson-xs-perl,-]
>> [- liblocale-gettext-perl,-]{+libjson-maybexs-perl,+}
>> libnet-dbus-perl,
>> [-libnet-dropbox-api-perl,-]{+libnet-oauth-perl,+}
>> {+ libnet-oauth2-perl,+}
>> {+ libnumber-bytes-human-perl,+}
>> {+ libpango-perl,+}
>> libpath-class-perl,
>> [- libproc-processtable-perl,-]
>> libproc-simple-perl,
>> [- librsvg2-common,-]
>> [- libsort-naturally-perl,-]
>> libwww-mechanize-perl,
>> [- libwww-perl,-]
>> [- libx11-protocol-other-perl,-]
>> [- libx11-protocol-perl,-]
>> [- libxml-simple-perl,-]
>> [- procps,-]
>> [- xdg-utils,-]
>> ${misc:Depends},
>> ${shlibs:Depends},
>> [-Recommends:-]
>> [- libgoo-canvas-perl,-]
>> [- libgtk2-appindicator-perl,-]
>> [- libnet-oauth-perl,-]
>> Suggests:
>> [-gnome-web-photo,-]{+libimage-exif-perl,+}
>> libimage-exiftool-perl,
>> [- libnet-dbus-glib-perl,-]
>> nautilus-sendto,
>>
>> --
>> Cheers,
>>   Andrej
>>
>>

Bug#973312: gedit: Add gir1.2-tepl-5 package dependency

[Jeffery To]

Since upstream has removed the dependency on tepl[1] and this has been
backported to the Debian package[2], I think this issue can be closed.

[1]: 
https://gitlab.gnome.org/GNOME/gedit/-/commit/fa587e033c97fac65dacdb3c9520635beca68fbc
[2]: 
https://salsa.debian.org/gnome-team/gedit/-/commit/f70d7c12f4df479c580a1110ab86081623e5b119

Bug#992353: ITP: r-cran-spatstat.core -- core functionality of the 'spatstat' family of GNU R packages

[Andreas Tille]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-spatstat.core -- core functionality of the 'spatstat' 
family of GNU R packages
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: r-cran-spatstat.core
  Version : 2.3
  Upstream Author : Adrian Baddeley,
* URL : https://cran.r-project.org/package=spatstat.core
* License : GPL-2+
  Programming Lang: GNU R
  Description : core functionality of the 'spatstat' family of GNU R 
packages
 Functionality for data analysis and modelling of spatial data, mainly
 spatial point patterns, in the 'spatstat' family of packages. (Excludes
 analysis of spatial data on a linear network, which is covered by the
 separate package 'spatstat.linnet'.) Exploratory methods include quadrat
 counts, K-functions and their simulation envelopes, nearest neighbour
 distance and empty space statistics, Fry plots, pair correlation
 function, kernel smoothed intensity, relative risk estimation with cross-
 validated bandwidth selection, mark correlation functions, segregation
 indices, mark dependence diagnostics, and kernel estimates of covariate
 effects. Formal hypothesis tests of random pattern (chi-squared, Kolmogorov-
 Smirnov, Monte Carlo, Diggle-Cressie-Loosmore-Ford, Dao-Genton, two-
 stage Monte Carlo) and tests for covariate effects (Cox-Berman-Waller-
 Lawson, Kolmogorov-Smirnov, ANOVA) are also supported. Parametric models
 can be fitted to point pattern data using the functions ppm(), kppm(),
 slrm(), dppm() similar to glm(). Types of models include Poisson, Gibbs
 and Cox point processes, Neyman-Scott cluster processes, and
 determinantal point processes. Models may involve dependence on
 covariates, inter-point interaction, cluster formation and dependence on
 marks. Models are fitted by maximum likelihood, logistic regression,
 minimum contrast, and composite likelihood methods. A model can be
 fitted to a list of point patterns (replicated point pattern data) using
 the function mppm(). The model can include random effects and fixed
 effects depending on the experimental design, in addition to all the
 features listed above. Fitted point process models can be simulated,
 automatically. Formal hypothesis tests of a fitted model are supported
 (likelihood ratio test, analysis of deviance, Monte Carlo tests) along
 with basic tools for model selection (stepwise(), AIC()) and variable
 selection (sdr). Tools for validating the fitted model include
 simulation envelopes, residuals, residual plots and Q-Q plots, leverage
 and influence diagnostics, partial residuals, and added variable plots.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-spatstat.core

Bug#197427: We are fine here

[Maxwell Watford]

I was expecting to hear from you or call me, did you get my first mail.
Thanks
Maxwell Watford.

Bug#681177: closed by "Steinar H. Gunderson" (Closing mlocate bugs)

[Steinar H. Gunderson]

On Tue, Aug 17, 2021 at 06:34:54PM +0300, Martin-Éric Racine wrote:
> You might wanna consider adding Provides: mlocate
> 
> Right now, packages that depend on mlocate refuse to install if
> plocate is installed.

Hm, can you give an example of such a package? There's still a dummy
transition package mlocate that depends on plocate, and I thought that would
be enough.

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#992351: molly-guard dracut issue

[Anton Lundin]

Package: molly-guard
Version: 0.7.2

Hi.

When using molly-guard together with dracut machine fails to
poweroff/halt/reboot with a issue like:


[   67.897697] dracut Warning: Killing all remaining processes
dracut Warning: Killing all remaining processes
[   67.975525] dracut Warning: Unmounted /oldroot.
[   68.002391] dracut: Disassembling device-mapper devices
E: not a regular file: /lib/molly-guard/poweroff[   68.036575] dracut Warning: 
poweroff failed!

dracut Warning: poweroff failed!


[   68.039669] dracut Warning: 
dracut Warning: 


Generating "/run/initramfs/rdsosreport.txt"
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.

To get more debug information in the report,
reboot with "rd.debug" added to the kernel command line.

Dropping to debug shell.

shutdown:/# 


This is because the /lib/molly-guard/poweroff symlink isn't available in
the dracut initramfs.


This can be worked around by adding this:
install_items+=" /lib/molly-guard/poweroff /lib/molly-guard/reboot 
/lib/molly-guard/halt /lib/molly-guard/shutdown "

to

/etc/dracut.conf.d/20-molly-guard.conf


And rebuilding the initramfs.


//Anton

Bug#681177: closed by "Steinar H. Gunderson" (Closing mlocate bugs)

[Steinar H. Gunderson]

On Tue, Aug 17, 2021 at 06:52:23PM +0300, Martin-Éric Racine wrote:
> For instance, cruft-ng.

cruft-ng installs just fine here (by pulling in the mlocate dummy package).
It isn't actually useful due to #976367, though (it expects to be able to
read mlocate's private data format).

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#992350: ifupdown-extra: Hardcoded "wlan0" in /etc/network/if-up.d/10check-duplicate-ip6

[Matti Kurkela]

Package: ifupdown-extra
Version: 0.32
Severity: normal
Tags: ipv6 patch

Dear Maintainer,

When adding package "ifup-extra" on a fresh installation of Debian 11, 
I started getting error messages referring to "wlan0" at ifup time.
This was unexpected as this system had no interface named "wlan0"
at the time.

An easy grep revealed that /etc/network/if-up.d/10check-duplicate-ip6
had a hard-coded reference to network interface "wlan0" where a 
variable was supposed to be used.

Here's a patch to fix it:

--- 10check-duplicate-ip6.old   2021-08-17 18:22:03.02908 +0300
+++ 10check-duplicate-ip6   2021-08-17 18:22:53.037696969 +0300
@@ -70,7 +70,7 @@ do_ndisc() {
 
 # First determine physical interface in case aliased interfaces are used
 real_iface=$(echo "$IFACE" | sed -e 's|:[[:digit:]]\+||')
-link_address=$(ip link show wlan0 | grep link | awk '{print 
toupper($2)}')
+link_address=$(ip link show "$real_iface" | grep link | awk '{print 
toupper($2)}')
 
 if [ -z "`ip link show $real_iface up`" ]; then
 return

-- System Information:
Debian Release: 11.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 5.10.0-8-686 (SMP w/1 CPU thread)
Locale: LANG=en_US.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ifupdown-extra depends on:
ii  bind9-host [host]1:9.16.15-1
ii  curl 7.74.0-1.3+b1
ii  dpkg 1.20.9
ii  iproute2 5.10.0-4
ii  iputils-arping   3:20210202-1
ii  iputils-ping [ping]  3:20210202-1
ii  lsb-base 11.1.0
ii  net-tools1.60+git20181103.0eebece-1
ii  netcat-openbsd   1.217-3

Versions of packages ifupdown-extra recommends:
ii  ethtool  1:5.9-1
ii  ndisc6   1.0.4-2

ifupdown-extra suggests no packages.

-- Configuration Files:
/etc/network/if-up.d/10check-duplicate-ip6 changed:
DEFAULT=/etc/default/network-test
[ -r "$DEFAULT" ] && . $DEFAULT
[ "$DO_ARPING" = "no" ]  && exit 0
NDISC=/usr/bin/ndisc6
[ ! -x "$NDISC" ] && exit 0 # Silent exit if ndisc is not installed
DO_SYSLOG=${DO_SYSLOG:-yes}
VERBOSITY=${VERBOSITY:-0}
LC_ALL=C
export LC_ALL
if [ "$DO_SYSLOG" = "yes" ] ; then
OUTPUT="logger -i -p daemon.err -s"
else
OUTPUT="echo"
fi
do_ndisc() {
real_iface=$(echo "$IFACE" | sed -e 's|:[[:digit:]]\+||')
link_address=$(ip link show $real_iface | grep link | awk '{print 
toupper($2)}')
if [ -z "`ip link show $real_iface up`" ]; then
return
fi
for ADDR in $IF_ADDRESS; do
# Only check IP address if it is IPv6
if echo ${ADDR} | grep -q ":" ; then
[ "$VERBOSITY" -eq 1 ] && $OUTPUT "DEBUG: Sending arp pings 
through $real_iface (for $IFACE) to detect other systems using $ADDR"
dup_link_address=$($NDISC -q $ADDR $real_iface)
if [ $? -eq 0 ] ; then
# If the link address is the same as our address this is 
not a problem
# (ndisc returns it in at least Wireless interfaces), only 
report if the link 
# address does not match
if [ "$link_address" != "$dup_link_address" ] ; then
$OUTPUT "ERROR: Duplicate address $ADDR assigned in the 
network where $real_iface is connected to."
fi
fi
fi
done
}
find_ip6() {
   export IF_ADDRESS
   IF_ADDRESS=$(ip addr show "$IFACE" 2>/dev/null | sed -rne 
's|^[[:blank:]]*inet6[[:blank:]]+([^/]+)/.*|\1|p')
   return 0
}
if [ -z "$IFACE" ] ; then
echo "ERROR: Do not know what interface to check. IFACE environment 
variable is not defined!" >&2
exit 1
fi
case $IFACE in
sl* | ww* | lo*) exit 0 ;;
*) ;;
esac
[ -z "$IF_ADDRESS" ] && find_ip6
[ -z "$IF_ADDRESS" ] && exit 0
do_ndisc 
exit 0


-- no debconf information

Bug#992345: www.debian.org: bullseye release-notes are misleading about the needed disk space

[Cyril Brulebois]

Hi Vincent,

Vincent Lefevre  (2021-08-17):
> 649 upgraded, 113 newly installed, 11 to remove and 1 not upgraded.
> Need to get 455 MB of archives.
> After this operation, 558 MB of additional disk space will be used.
> 
> and I had around 650 MB free space

455+558 >> 650 so it was very unlikely to work?

But yeah, even if the release notes mention “After the download […]”
things, it could probably point out that you should look at both
numbers, instead of just using xx.x and AAA placeholders.

> I suspect that some packages like this one need a lot of temporary
> disk space (could this be related to initrd before compression?).
> But there is nothing about that in the release notes. And perhaps
> a warning should have been output by apt.

There's one for the directory where debs are downloaded (which you
didn't get since 455 << 650), but I suspect it's harder to estimate
where the whole “additional disk space” is going to end up, depending on
file system layout, etc.?


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Bug#984368: tpm2-pkcs11: ftbfs with GCC-11

[Simon Chopin]

This appears fixed upstream, see
https://github.com/tpm2-software/tpm2-pkcs11/pull/677

Bug#992349: libclang-common-11-dev: Cannot install amd64 and armhf together

[Anton]

Package: libclang-common-11-dev
Version: 1:11.0.1-2~bpo10+1
Severity: minor

Dear Maintainer,

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

   * What led up to the situation?
Try to install both packages.
apt install clang-11/buster-backports   
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Manually extract files from armhf pacakge and copy it
   * What was the outcome of this action?
I cannot install amd64 and armhf version together. It's a problem for 
cross-compilation with clang because you cannot link against compiler-rt.
 For example I have issue with m4 (libm4), m4 can be compiled with gcc 
and linked against libgcc, also it can be compiled with clang and linked 
against compiler-rt, but it cannot be compiled with clang and linked against 
libgcc. It leads to:
/usr/bin/arm-linux-gnueabihf-ld: symtab.o: in function `symtab_init':
symtab.c:(.text+0x34): undefined reference to `__mulodi4'
/usr/bin/arm-linux-gnueabihf-ld: ../lib/libm4.a(clean-temp.o): in function 
`create_temp_dir':
clean-temp.c:(.text+0x9c): undefined reference to `__mulodi4'
/usr/bin/arm-linux-gnueabihf-ld: ../lib/libm4.a(fatal-signal.o): in function 
`at_fatal_signal':
fatal-signal.c:(.text+0x190): undefined reference to `__mulodi4'
/usr/bin/arm-linux-gnueabihf-ld: ../lib/libm4.a(xmalloc.o): in function 
`xnmalloc':
xmalloc.c:(.text+0x30): undefined reference to `__mulodi4'
/usr/bin/arm-linux-gnueabihf-ld: ../lib/libm4.a(xmalloc.o): in function 
`xnrealloc':
xmalloc.c:(.text+0xe4): undefined reference to `__mulodi4'
/usr/bin/arm-linux-gnueabihf-ld: 
../lib/libm4.a(xmalloc.o):xmalloc.c:(.text+0x334): more undefined references to 
`__mulodi4' follow
Briefly speaking it leads to missing 
/usr/lib/llvm-11/lib/clang/11.0.1/lib/linux/libclang_rt.builtins-armhf.a
 
   * What outcome did you expect instead?
I didn't expect conflict between multiarch packages.


-- System Information:
Debian Release: 10.10
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

Kernel: Linux 4.19.0-17-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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)
LSM: AppArmor: enabled

Versions of packages libclang-common-11-dev depends on:
ii  libc6   2.28-10
ii  libgcc1 1:8.3.0-6
ii  libllvm11   1:11.0.1-2~bpo10+1
ii  libstdc++6  8.3.0-6

libclang-common-11-dev recommends no packages.

libclang-common-11-dev suggests no packages.

-- no debconf information

Bug#681177: closed by "Steinar H. Gunderson" (Closing mlocate bugs)

[Martin-Éric Racine]

For instance, cruft-ng.

ti 17. elok. 2021 klo 18.46 Steinar H. Gunderson (se...@debian.org) kirjoitti:
>
> On Tue, Aug 17, 2021 at 06:34:54PM +0300, Martin-Éric Racine wrote:
> > You might wanna consider adding Provides: mlocate
> >
> > Right now, packages that depend on mlocate refuse to install if
> > plocate is installed.
>
> Hm, can you give an example of such a package? There's still a dummy
> transition package mlocate that depends on plocate, and I thought that would
> be enough.
>
> /* Steinar */
> --
> Homepage: https://www.sesse.net/

Bug#530924: mlocate: Please add support for searching for files owned by a user

[Steinar H. Gunderson]

On Thu, May 28, 2009 at 08:42:16PM +0100, Dominic Hargreaves wrote:
> It would be really nice to have support for searching for files owned by
> a given user/group. Presumably the information is already in the database,
> for authorization reasons.

Hi,

As of bookworm, mlocate is removed from the archive in favor of plocate.
Is this bug still relevant for you? (If not, I will close it, along with the
other bugs inherited from plocate.)

Do note that the information is _not_ already in the database, neither for
mlocate nor plocate; authorization is done by checking every directory up
from the root, ie., effectively asking the kernel. (Notably, the file itself
isn't checked, since one doesn't need access to it to scan it.) Anything else
would be very difficult wrt. complicated ACLs, networked filesystems or
simply access rights that have been changed since the database was created.
Thus, if someone made such an option for plocate, it would be no more
efficient than piping the list of results through a shell script to check the
owner (and with ACLs, is the owner always what you want?).

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#681177: closed by "Steinar H. Gunderson" (Closing mlocate bugs)

[Martin-Éric Racine]

You might wanna consider adding Provides: mlocate

Right now, packages that depend on mlocate refuse to install if
plocate is installed.

ti 17. elok. 2021 klo 18.24 Debian Bug Tracking System
(ow...@bugs.debian.org) kirjoitti:
>
> This is an automatic notification regarding your Bug report
> which was filed against the mlocate package:
>
> #681177: mlocate: cron.daily job killed with error 137
>
> It has been closed by "Steinar H. Gunderson" .
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact "Steinar H. Gunderson" 
>  by
> replying to this email.
>
>
> --
> 681177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681177
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: "Steinar H. Gunderson" 
> To: 593431-d...@bugs.debian.org, 681177-d...@bugs.debian.org, 
> 746943-d...@bugs.debian.org, 926290-d...@bugs.debian.org, 
> 972980-d...@bugs.debian.org, 664206-d...@bugs.debian.org, 
> 784428-d...@bugs.debian.org, 925169-d...@bugs.debian.org, 
> 524134-d...@bugs.debian.org, 989574-d...@bugs.debian.org, 
> 472059-d...@bugs.debian.org, 969522-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Tue, 17 Aug 2021 17:05:16 +0200
> Subject: Closing mlocate bugs
> Hi,
>
> As of bookworm, mlocate no longer exists in Debian and is replaced by plocate.
> There's still an “mlocate” package, but it is only a transitional package
> to install plocate (and convert over the old database).
>
> Thus, I'm closing a series of bugs related to mlocate that I believe are
> either:
>
>  1. Already fixed in plocate, or
>  2. Related to implementation bugs in mlocate that are highly unlikely
> to reappear in plocate (which only shares configuration parsing code,
> no other internals).
>
> If you believe this is in error and the bug is relevant for plocate,
> please reopen it with a message as of why that is the case (and reassign it
> to plocate). Thanks!
>
> /* Steinar */
> --
> Homepage: http://www.sesse.net/
>
>
> -- Forwarded message --
> From: "Martin-Éric Racine" 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Wed, 11 Jul 2012 09:18:31 +0300
> Subject: mlocate: cron.daily job killed with error 137
> Package: mlocate
> Version: 0.23.1-1
> Severity: normal
>
> As mailed to me by cron:
>
> /etc/cron.daily/mlocate: line 36:29683 Killed $IONICE 
> /usr/bin/updatedb.mlocate
> run-parts: /etc/cron.daily/mlocate exited with return code 137
>
> -- System Information:
> Debian Release: wheezy/sid
>   APT prefers testing
>   APT policy: (1001, 'testing')
> Architecture: i386 (i586)
>
> Kernel: Linux 3.2.0-3-486
> Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages mlocate depends on:
> ii  adduser  3.113+nmu3
> ii  libc62.13-33
>
> mlocate recommends no packages.
>
> mlocate suggests no packages.
>
> -- no debconf information
>
>

Bug#992348: mapserver: please re-enable build of ruby-mapscript package

[Tomas Pospisek]

Source: mapserver
Version: 7.6.4-1
Severity: wishlist

Hi Debian GIS maintainers, hi Bas!

tldr: would it be possible to re-enable the ruby-mapscript package
build?

Extended explication: requiring a packaged version of ruby-mapscript
on Ubuntu 20.04 I today basically reverted commits [1] and [2] and
ruby-mapscript built just fine. A quick test showed ruby-mapscript
to work. Then I did the same thing on bullseye and again,
ruby-mapscript build fine.

Questions:

* would it be possible to start building the ruby-mapscript package again?

* I see commit [1] that says "Build Ruby MapScript only for default version",
  but it doesn't say why builds for other ruby versions are being dropped.
  What was the reason for dropping the build of ruby-mapscript for the
  various existing Ruby versions?

* half an hour later there's a commit [2] that drops ruby-mapscript
  alltogether. I couldn't find a log of the respective FTBS. But
  maybe it doesn't matter any more since it does seem to build just
  fine now.

So would it be possible to revert [1] and [2]? Or should I fork the
project on Salsa and file a PR?

Either way: *thanks a lot for maintaining mapserver*!!!

Greetings,
*t

[1] 
https://salsa.debian.org/debian-gis-team/mapserver/-/commit/45f6f67e4272122d9d9fa0c49f247d68690c659a
[2] 
https://salsa.debian.org/debian-gis-team/mapserver/-/commit/8d14c0fe55e33ef1922ac529e23cbb04776afd9a


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

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

Bug#992346: elpa-org: install script from elpa-org package failed

[Damien Couroussé]

Package: elpa-org
Version: 9.1.14+dfsg-3
Severity: important

The package install fails with the following error message:

ERROR: install script from elpa-org package failed
dpkg: error processing package elpa-org (--configure):
 installed elpa-org package post-installation script subprocess 
returned error exit status 1

Errors were encountered while processing:
 elpa-org
E: Sub-process /usr/bin/dpkg returned an error code (1)


Please find below the complete error log.

best,
Damien




-- System Information:
Debian Release: 10.10
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable'), (200, 
'testing'), (100, 'unstable'), (10, 'experimental')

Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), 
LANGUAGE=fr_FR.utf8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages elpa-org depends on:
ii  elpa-htmlize    1.54-1
ii  emacsen-common  3.0.4

Versions of packages elpa-org recommends:
ii  emacs  1:27.1+1-3~bpo10+1
ii  emacs-gtk [emacs]  1:27.1+1-3~bpo10+1

Versions of packages elpa-org suggests:
pn  ditaa  
ii  org-mode-doc   9.1.14-1
pn  texinfo    
ii  texlive-fonts-recommended  2018.20190227-2
ii  texlive-latex-extra    2018.20190227-2

-- no debconf information






# env LANG=C apt install elpa-org
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  elpa-htmlize
Suggested packages:
  ditaa texinfo
The following NEW packages will be installed:
  elpa-htmlize elpa-org
0 upgraded, 2 newly installed, 0 to remove and 219 not upgraded.
Need to get 0 B/1 080 kB of archives.
After this operation, 6 117 kB of additional disk space will be used.
Do you want to continue? [Y/n]
Selecting previously unselected package elpa-htmlize.
(Reading database ... 348317 files and directories currently installed.)
Preparing to unpack .../elpa-htmlize_1.54-1_all.deb ...
Unpacking elpa-htmlize (1.54-1) ...
Selecting previously unselected package elpa-org.
Preparing to unpack .../elpa-org_9.1.14+dfsg-3_all.deb ...
Unpacking elpa-org (9.1.14+dfsg-3) ...
Setting up elpa-htmlize (1.54-1) ...
Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
Install elpa-htmlize for emacs
install/htmlize-1.54: Handling install of emacsen flavor emacs
install/htmlize-1.54: byte-compiling for emacs
Setting up elpa-org (9.1.14+dfsg-3) ...
tsort: -: input contains a loop:
tsort: elpa-htmlize
tsort: emacsen-common
Install elpa-htmlize for emacs
install/htmlize-1.54: Handling install of emacsen flavor emacs
install/htmlize-1.54: byte-compiling for emacs
Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
Install elpa-org for emacs
install/org-9.1.14: Handling install of emacsen flavor emacs
install/org-9.1.14: byte-compiling for emacs

In org-babel-open-src-block-result:
ob-core.el:1039:25:Warning: `org-bracket-link-regexp' is an obsolete 
variable

    (as of Org 9.3); use `org-link-bracket-re' instead.

In org-babel-sha1-hash:
ob-core.el:1227:8:Warning: function org-babel-sha1-hash used to take 0-2
    arguments, now takes 0-1

In org-babel-params-from-properties:
ob-core.el:1430:8:Warning: function org-babel-params-from-properties used to
    take 0-2 arguments, now takes 0-1

In org-babel-parse-header-arguments:
ob-core.el:1534:8:Warning: function org-babel-parse-header-arguments used to
    take 1-2 arguments, now takes 1

In org-babel-demarcate-block:
ob-core.el:1879:42:Warning: `org-get-indentation' is an obsolete 
function (as

    of Org 9.2); use `current-indentation' instead.

In org-babel-read-element:
ob-core.el:2086:28:Warning: `org-bracket-link-regexp' is an obsolete 
variable

    (as of Org 9.3); use `org-link-bracket-re' instead.

In org-babel-read-link:
ob-core.el:2128:32:Warning: `org-bracket-link-regexp' is an obsolete 
variable

    (as of Org 9.3); use `org-link-bracket-re' instead.

In org-babel-insert-result:
ob-core.el:2276:33:Warning: `org-get-indentation' is an obsolete 
function (as

    of Org 9.2); use `current-indentation' instead.

In org-babel-result-end:
ob-core.el:2473:51:Warning: `org-bracket-link-regexp' is an obsolete 
variable

    (as of Org 9.3); use `org-link-bracket-re' instead.

In org-babel-update-block-body:
ob-core.el:2539:18:Warning: `org-get-indentation' is an obsolete 
function (as

    of Org 9.2); use `current-indentation' instead.

In org-babel-exp-process-buffer:
ob-exp.el:247:36:Warning: `org-get-indentation' is an obsolete function 
(as of

    Org 9.2); use `current-indentation' instead.

In org-babel-execute:haskell:
ob-haskell.el:86:22:Warning: `org-babel-strip-quotes' is an obsolete 

Bug#992300: ca-certificates: ca-certificate update fails because of missing /usr/bin/cert-sync

[Michael Shuler]

On 8/17/21 9:40 AM, Alex wrote:


I am not sure if ca-certificates-mono was installed at all. I do not
have mono on the system.


The machine did have the packages below installed at some point.


$ dpkg -l|grep mono|grep -v fonts-|grep -v python3-monotonic
rc  ca-certificates-mono 4.6.2.7+dfsg-1
all  Common CA certificates (Mono keystore)
rc  mono-runtime-common  4.6.2.7+dfsg-1
amd64Mono runtime - common files


The packages were removed (r), leaving behind configuration (c) files.


$ ls /etc/ca-certificates/update.d/mono-keystore /usr/bin/cert-sync
ls: cannot access '/usr/bin/cert-sync': No such file or directory
/etc/ca-certificates/update.d/mono-keystore


Version 4.6.2.7+dfsg-1 is listed on p.d.o as the latest version from 
Stretch, so it could have been quite some time ago and your logs for 
that were likely rotated, so not in the latest dpkg.log file. Purging 
packages would also remove configurations, so if you wish to do a little 
clean up:


  apt purge ca-certificates-mono mono-runtime-common

Seems this bug can likely be closed, the fix version for #902663 is 
later than the reporter's old "rc" remnants.


Kind regards,
Michael

Bug#992038: systemd: regression with systemd-networkd + dropbear initramfs and kernel ip autoconfig(?)

[Axel Scheepers]

Hi,

I've been trying to bisect but it's not going well. Maybe you can give
me a hand with this:

axel@nuc:~/src/Git/systemd$ git bisect start
axel@nuc:~/src/Git/systemd$ git bisect bad v248
axel@nuc:~/src/Git/systemd$ git bisect good v249
Bisecting: a merge base must be tested
[938bdfc0fa737d86eb3ecc70506e11e5f740e0dc] Merge pull request #19157
from keszybz/read-medium-sized-virtual-file

I did the bisect for the other commits by reverting bad/good but that
didn't work out and all builds failed. I'd like to try to bisect this
merge commit if that makes sense. If you have a better idea i'm all
ears. The setup will move next month however and then the fritzbox will
be out of the loop. I've also converted the production box to just
dhcpcd. When looking at the logs for that i notice:

Aug 17 16:40:47 amber dhcpcd[7852]: enp1s0: DHCPv6 REPLY: iana not found
Aug 17 16:40:47 amber dhcpcd[7852]: enp1s0: soliciting a DHCPv6 lease
Aug 17 16:40:48 amber dhcpcd[7852]: wlp2s0: DHCPv6 REPLY: iana not found
Aug 17 16:40:48 amber dhcpcd[7852]: wlp2s0: soliciting a DHCPv6 lease

Not sure if that is related. As dhcpcd works fine the issue is not
really relevant for me anymore but i still like to help resolve the
issue as long as time permits.

Kind regards,

Axel Scheepers

Bug#992345: www.debian.org: bullseye release-notes are misleading about the needed disk space

[Vincent Lefevre]

Package: www.debian.org
Severity: important

The bullseye release-notes at

  
https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html

are misleading about the needed disk space.

"apt -o APT::Get::Trivial-Only=true full-upgrade" was saying

649 upgraded, 113 newly installed, 11 to remove and 1 not upgraded.
Need to get 455 MB of archives.
After this operation, 558 MB of additional disk space will be used.

and I had around 650 MB free space, but the upgrade failed due to
lack of disk space when processing the new Linux kernel
(linux-image-5.10.0-8-amd64_5.10.46-4_amd64.deb). I tried to
complete the upgrade after another "apt clean", but this wasn't
enough (and increasing the disk space couldn't be done without
rebooting).

I suspect that some packages like this one need a lot of temporary
disk space (could this be related to initrd before compression?).
But there is nothing about that in the release notes. And perhaps
a warning should have been output by apt.

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

Bug#912271: newlib: diff for NMU version 3.3.0-1.1

[John Scott]

Control: tags 912271 + pending

Dear maintainer,

I've prepared an NMU for newlib (versioned as 3.3.0-1.1) and
uploaded it to DELAYED/15 via sponsorship. Please feel free
to tell me if I should delay it longer.

Regards.

diff -Nru newlib-3.3.0/debian/changelog newlib-3.3.0/debian/changelog
--- newlib-3.3.0/debian/changelog   2020-02-29 08:35:41.0 -0500
+++ newlib-3.3.0/debian/changelog   2021-06-08 17:17:43.0 -0400
@@ -1,3 +1,11 @@
+newlib (3.3.0-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Add newlib-source binary package to aid building for new targets.
+(Closes: #912271)
+
+ -- John Scott   Tue, 08 Jun 2021 17:17:43 -0400
+
 newlib (3.3.0-1) unstable; urgency=medium
 
   [ Agustin Henze ]
diff -Nru newlib-3.3.0/debian/control newlib-3.3.0/debian/control
--- newlib-3.3.0/debian/control 2020-02-29 08:35:41.0 -0500
+++ newlib-3.3.0/debian/control 2021-02-03 10:05:40.0 -0500
@@ -56,3 +56,14 @@
  .
  This package contains the newlib library compiled for Cortex-A*,
  Cortex-R4/R5/R7 and Cortex-M0/M0+/M3/M4 targets.
+
+Package: newlib-source
+Architecture: all
+Section: libdevel
+Description: C library and math library for embedded systems (source)
+ Newlib is a C library and math library intended for use on embedded systems.
+ It is a conglomeration of several library parts, all under free software
+ licenses that make them easily usable on embedded products.
+ .
+ This package contains the upstream source code suitable for targeting
+ new platforms.
diff -Nru newlib-3.3.0/debian/newlib-source.install 
newlib-3.3.0/debian/newlib-source.install
--- newlib-3.3.0/debian/newlib-source.install   1969-12-31 19:00:00.0 
-0500
+++ newlib-3.3.0/debian/newlib-source.install   2021-02-03 10:02:42.0 
-0500
@@ -0,0 +1 @@
+debian/newlib-*.tar.xz usr/src/newlib/
diff -Nru newlib-3.3.0/debian/rules newlib-3.3.0/debian/rules
--- newlib-3.3.0/debian/rules   2020-02-29 08:35:41.0 -0500
+++ newlib-3.3.0/debian/rules   2021-02-11 19:59:47.0 -0500
@@ -66,11 +66,14 @@
 %:
dh $@ -B$(BUILD_DIR) --with autotools-dev --parallel
 
+debian/newlib-$(DEB_VERSION_UPSTREAM).tar.xz:
+   tar -acf $@ --exclude=debian --exclude-vcs --exclude='*.dh-orig' 
`pwd`/../`basename $(TOP_DIR)`
+
 override_dh_clean:
dh_clean
-   rm -rf $(BUILD_DIR) $(BUILD_NANO_DIR) $(TMP_NANO_DIR)
+   rm -rf $(BUILD_DIR) $(BUILD_NANO_DIR) $(TMP_NANO_DIR) 
debian/newlib-*.tar.xz
 
-override_dh_auto_configure:
+override_dh_auto_configure: debian/newlib-$(DEB_VERSION_UPSTREAM).tar.xz
dh_auto_configure -B$(BUILD_DIR) -- $(CONFIGURE_FLAGS)
dh_auto_configure -B$(BUILD_NANO_DIR) -- $(CONFIGURE_FLAGS_NANO)