Bug#971623: review and simplify the /devel/wnpp section

[Carsten Schoenert]

Hello pabs,

Am 04.10.20 um 04:13 schrieb Paul Wise:
> wnpp.debian.net is an unofficial service that could go away at any
> moment if the Debian member sponsoring the domain leaves Debian or the
> contributor providing the service decides to shut it down.

yes you are right of course, that's no question.

> I think it would be better to not rely on it for things that we don't
> need to rely on it for and rely on it for things that aren't
> implemented anywhere else.
For me the question is "Need we this at all and in what way?"

Thomas (Lange) and myself have spoken and discussed a lot about the
structure of www.d.o and the first realization we came to was that the
website has a really complicated and bloated structure that is hindering
us in every small corner to make a visible progress in modernize and
update the content. And if "we" (means the rather long time members) do
it all on our own we also wont ever find new contributors for that
because it's to complicated and to expensive to dig in.

The solution for every big problem is to split of the big problem into
smaller problems. Cutting out the currently implemented wnpp part would
be one of the rather smaller problems on the road.

We can and should discuss how we can do this.

-- 
Regards
Carsten Schoenert

Bug#971649: RM: packer [mipsel] -- ROM; ANAIS; OOM when link on mipsel

[Shengjing Zhu]

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

Hi,

Please remove packer on mipsel. It seems the memory limit on buildd is met.

https://buildd.debian.org/status/fetch.php?pkg=packer=mipsel=1.6.4%2Bdfsg-2=1601747264=0
panic: cannot allocate memory

Thanks
Shengjing Zhu

Bug#971000: Acknowledgement (linux-image-5.8.0-2-amd64: Periodic networking failure with recent kernels in Testing)

[Ryan Thoryk]

This issue happened again on my system, and I was able to confirm that 
the system (and networking) recovers fine after unplugging the Netgear 
WNA3100M USB WIFI adapter.  That adapter uses the rtl8192cu driver.  I 
was connecting the system using the on-board ethernet and not that wifi 
adapter (the wifi was left unassociated).  I'll leave it unplugged and 
see if the system works fine now.


--
Ryan Thoryk
r...@thoryk.com
r...@tliquest.net

Bug#971648: wogerman: Spelling mistakes in German (old spelling rules) word list

[Thure Dührsen]

Package: wogerman
Version: 1:2-35
Severity: normal
Tags: l10n

Dear Maintainer,

While browsing the differences between Swiss and German (old spelling rules) 
dictionaries like this

cd /usr/share/dict; comm -13 <(sort swiss) <(sort ogerman) | grep -i ^ver | 
less

I noticed a number of words that all mistakenly lack the letter "i".

This, too, applies to version 1:2-36.

$ pwd
/home/tdu/Downloads/wogerman

$ grep ^Version ./control
Version: 1:2-36

$ grep -R ^verbt ./usr/share/dict | column -t -s':'
./usr/share/dict/ogerman  verbttere
./usr/share/dict/ogerman  verbttern
./usr/share/dict/ogerman  verbtternd
./usr/share/dict/ogerman  verbtternde
./usr/share/dict/ogerman  verbtterndem
./usr/share/dict/ogerman  verbtternden
./usr/share/dict/ogerman  verbtternder
./usr/share/dict/ogerman  verbtterndes
./usr/share/dict/ogerman  verbtterst
./usr/share/dict/ogerman  verbttert
./usr/share/dict/ogerman  verbtterte
./usr/share/dict/ogerman  verbttertem
./usr/share/dict/ogerman  verbtterten
./usr/share/dict/ogerman  verbtterter
./usr/share/dict/ogerman  verbttertes
./usr/share/dict/ogerman  verbttertest
./usr/share/dict/ogerman  verbttertet
./usr/share/dict/ogerman  verbttre

$


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

Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wogerman depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  dictionaries-common1.28.1
ii  perl   5.28.1-6

wogerman recommends no packages.

wogerman suggests no packages.

-- debconf information excluded

Bug#971647: lightdm-gtk-greeter: ignores system default theme

[Matt Beary]

Package: lightdm-gtk-greeter
Version: 2.0.6-1
Severity: normal

Dear Maintainer,

lightdm-gtk-greeter currently ignores the system default themes, due to a 
hardcoding of Adwaita in 
/usr/share/lightdm/lightdm-gtk-greeter.conf.d/01_debian.conf.
This can be seen in the source here: 
https://salsa.debian.org/xfce-extras-team/lightdm-gtk-greeter/-/blob/debian/master/debian/01_debian.conf#L6

removing this line causes the defaults set in /etc/gtk-3.0 to be used as 
expected

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

Kernel: Linux 4.19.0-11-amd64 (SMP w/4 CPU cores)
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.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lightdm-gtk-greeter depends on:
ii  libc6   2.28-10
ii  libcairo2   1.16.0-4
ii  libgdk-pixbuf2.0-0  2.38.1+dfsg-1
ii  libglib2.0-02.58.3-2+deb10u2
ii  libgtk-3-0  3.24.5-1
ii  libindicator3-7 0.5.0-4
ii  liblightdm-gobject-1-0  1.26.0-4
ii  libx11-62:1.6.7-1+deb10u1

Versions of packages lightdm-gtk-greeter recommends:
ii  adwaita-icon-theme  3.30.1-1
ii  desktop-base10.0.2
ii  gnome-themes-extra  3.28-1
ii  policykit-1 0.105-25

lightdm-gtk-greeter suggests no packages.

-- Configuration Files:
/etc/lightdm/lightdm-gtk-greeter.conf changed [not included]

-- no debconf information

Bug#971327: libopenshot dependency on libavresample

[FeRD]

Greetings, one of the libopenshot maintainers here.

libopenshot not only supports swresample, but uses it in place of
avresample for all LIBAVFORMAT_VERSION_MAJOR >= 57 (which corresponds to
slightly before the ffmpeg 3.0 release). The dependency on libavresample in
those cases is completely superfluous. Please do remove it from the package
configuration.

Bug#942926: adequate: Python2 removal in sid/bullseye

[Stuart Prescott]

Control: tags -1 + patch

A patch that seems to fix the Python-related problems is at

https://salsa.debian.org/debian/adequate/-/merge_requests/1

but note that there seem to be other changes (perhaps related to a change in 
GCC?) that must also be addressed.

-- 
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#971646: wogerman: Spelling mistake in German (old spelling rules) word list

[Thure Dührsen]

Package: wogerman
Version: 1:2-35
Followup-For: Bug #971646

Oh well, talk about spelling mistakes!

> The Swiss and German (new spelling rules) word lists are correct in this 
> regard, they say
> 
> Atomzerstrümmerung
> 
> instead.

That should read

> The Swiss and German (new spelling rules) word lists are correct in this 
> regard, they say
> 
> Atomzertrümmerung
> 
> instead.

instead, of course!

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

Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wogerman depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  dictionaries-common1.28.1
ii  perl   5.28.1-6

wogerman recommends no packages.

wogerman suggests no packages.

-- debconf information excluded

Bug#971646: wogerman: Spelling mistake in German (old spelling rules) word list

[Thure Dührsen]

Package: wogerman
Version: 1:2-35
Severity: normal
Tags: l10n

Dear Maintainer,

The file "/usr/share/dict/ogerman" contains the word

Atomzerstrümmerung

that I happened upon by chance and that misspells the word "Zertrümmerung".

I confirmed this is the case with version 1:2-36.

The Swiss and German (new spelling rules) word lists are correct in this 
regard, they say

Atomzerstrümmerung

instead.

grep -R ^A.*trümmer /usr/share/dict | column -t -s':'
/usr/share/dict/ogerman  Atomzerstrümmerung
/usr/share/dict/ngerman  Atomzertrümmerung
/usr/share/dict/swissAtomzertrümmerung

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

Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wogerman depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  dictionaries-common1.28.1
ii  perl   5.28.1-6

wogerman recommends no packages.

wogerman suggests no packages.

-- debconf information excluded

Bug#971623: review and simplify the /devel/wnpp section

[Paul Wise]

On Sat, Oct 3, 2020 at 9:45 AM Laura Arjona Reina wrote:

> Having a look at both the resulting listings that we provide in
> www.debian.org/devel/wnpp, and the ones provided in wnpp.debian.net, I
> think maybe we could review our old approach and remove most of the
> listings we were providing, and link to wnpp.debian.net instead.

wnpp.debian.net is an unofficial service that could go away at any
moment if the Debian member sponsoring the domain leaves Debian or the
contributor providing the service decides to shut it down. I think it
would be better to not rely on it for things that we don't need to
rely on it for and rely on it for things that aren't implemented
anywhere else.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#971645: sshfs: truncates timestamps to whole seconds

[Adam Borowski]

Package: sshfs
Version: 3.7.0+repack-1
Severity: normal

Hi!
sshfs sets the sub-second part of timestamps to 0.  This happens both
on read (stat) and on write (utimensat).

This means, the metadata of a file copied over sshfs will be different,
causing unnecessary whole-file comparisons, etc.

Strictly speaking, some historic filesystems have a large granularity
(FAT has 2s...), but anything Unixy has standardized on 1ns since a long
time ago, thus too many things assume timestamps to pass through
uncorrupted.

And sshfs has no historic wire protocols to care about, thus this piece
of metadata loss doesn't seem intentional.


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

Kernel: Linux 5.9.0-rc7-00045-g6b19fa129f99 (SMP w/64 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages sshfs depends on:
ii  fuse3   3.9.3-1
ii  libc6   2.31-3
ii  libfuse3-3  3.9.3-1
ii  libglib2.0-02.66.0-2
ii  openssh-client  1:8.3p1-1

sshfs recommends no packages.

sshfs suggests no packages.

-- no debconf information

Bug#971640: firejail: Build profile command no longer works

[Chris Dufrenne]

Package: firejail
Version: 0.9.58.2-2+deb10u1
Severity: normal

Dear Maintainer,

When using the --build option firejail spits out this message for every program 
I've tried it on:

2:strace:exec /usr/bin/strace:0
2:strace:fopen64  /tmp/firejail-strace.XX:(nil)
/usr/bin/strace: Can't fopen ' /tmp/firejail-strace.XX': No such file or 
directory
Error: cannot run the sandbox

In the previous version it worked.

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

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

Versions of packages firejail depends on:
ii  libapparmor1  2.13.2-10
ii  libc6 2.28-10

Versions of packages firejail recommends:
ii  firejail-profiles  0.9.58.2-2+deb10u1
ii  iproute2   4.20.0-2
ii  iptables   1.8.2-4
ii  xauth  1:1.0.10-1
ii  xpra   2.4.3+dfsg1-1

firejail suggests no packages.

-- Configuration Files:
/etc/apparmor.d/firejail-default changed [not included]
/etc/apparmor.d/local/firejail-default changed [not included]
/etc/firejail/0ad.profile changed [not included]
/etc/firejail/2048-qt.profile changed [not included]
/etc/firejail/7z.profile changed [not included]
/etc/firejail/7za.profile changed [not included]
/etc/firejail/7zr.profile changed [not included]
/etc/firejail/Cyberfox.profile changed [not included]
/etc/firejail/Discord.profile changed [not included]
/etc/firejail/DiscordCanary.profile changed [not included]
/etc/firejail/FossaMail.profile changed [not included]
/etc/firejail/Fritzing.profile changed [not included]
/etc/firejail/Gitter.profile changed [not included]
/etc/firejail/JDownloader.profile changed [not included]
/etc/firejail/Mathematica.profile changed [not included]
/etc/firejail/Natron.profile changed [not included]
/etc/firejail/QMediathekView.profile changed [not included]
/etc/firejail/QOwnNotes.profile changed [not included]
/etc/firejail/Telegram.profile changed [not included]
/etc/firejail/Thunar.profile changed [not included]
/etc/firejail/Viber.profile changed [not included]
/etc/firejail/VirtualBox.profile changed [not included]
/etc/firejail/XMind.profile changed [not included]
/etc/firejail/Xephyr.profile changed [not included]
/etc/firejail/Xvfb.profile changed [not included]
/etc/firejail/abrowser.profile changed [not included]
/etc/firejail/acat.profile changed [not included]
/etc/firejail/adiff.profile changed [not included]
/etc/firejail/akonadi_control.profile changed [not included]
/etc/firejail/akregator.profile changed [not included]
/etc/firejail/als.profile changed [not included]
/etc/firejail/amarok.profile changed [not included]
/etc/firejail/amule.profile changed [not included]
/etc/firejail/android-studio.profile changed [not included]
/etc/firejail/aosp.profile changed [not included]
/etc/firejail/apack.profile changed [not included]
/etc/firejail/apktool.profile changed [not included]
/etc/firejail/arch-audit.profile changed [not included]
/etc/firejail/archaudit-report.profile changed [not included]
/etc/firejail/ardour4.profile changed [not included]
/etc/firejail/ardour5.profile changed [not included]
/etc/firejail/arduino.profile changed [not included]
/etc/firejail/arepack.profile changed [not included]
/etc/firejail/aria2c.profile changed [not included]
/etc/firejail/ark.profile changed [not included]
/etc/firejail/arm.profile changed [not included]
/etc/firejail/artha.profile changed [not included]
/etc/firejail/asunder.profile changed [not included]
/etc/firejail/atom-beta.profile changed [not included]
/etc/firejail/atom.profile changed [not included]
/etc/firejail/atool.profile changed [not included]
/etc/firejail/atril-previewer.profile changed [not included]
/etc/firejail/atril-thumbnailer.profile changed [not included]
/etc/firejail/atril.profile changed [not included]
/etc/firejail/audacious.profile changed [not included]
/etc/firejail/audacity.profile changed [not included]
/etc/firejail/aunpack.profile changed [not included]
/etc/firejail/authenticator.profile changed [not included]
/etc/firejail/baloo_file.profile changed [not included]
/etc/firejail/baloo_filemetadata_temp_extractor.profile changed [not included]
/etc/firejail/baobab.profile changed [not included]
/etc/firejail/basilisk.profile changed [not included]
/etc/firejail/beaker.profile changed [not included]
/etc/firejail/bibletime.profile changed [not included]
/etc/firejail/bitcoin-qt.profile changed [not included]
/etc/firejail/bitlbee.profile changed [not included]
/etc/firejail/bleachbit.profile changed [not included]
/etc/firejail/blender-2.8.profile changed [not included]
/etc/firejail/blender.profile changed [not included]
/etc/firejail/bless.profile changed [not included]

Bug#971594: RFS: asciidoc/9.0.2-1 [ITA] -- Highly configurable text format for writing documentation

[Paul Wise]

On Sat, 2020-10-03 at 10:11 +0200, Leon Marz wrote:

> Ok, no problem. asciidoc-base is now a metapackage, which depends on 
> asciidoc.

Please also file a bug on nanoc so that you can eventually drop the
asciidoc-base transitional package.

I also suggest removing the suggests/recommends from asciidoc-base
since it is a transitional package containing nothing.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#971644: elogind: accidentally hitting Fn-F12 crashes the system (dirty filesystem)

[Thorsten Glaser]

Package: elogind
Version: 243.7-1+debian1
Severity: critical
Justification: causes serious data loss
X-Debbugs-Cc: t...@mirbsd.de

Yay, I found another behavioural difference between just running Debian
(classic, that is, sysvinit withOUT elogind) and Debian with elogind (to
satisfy certain packages’ dependencies, I certainly do not need any of
its functionality!).

This is in the same manner as #919694 (*why* is that still unfixed‽)
and #949698 (now fixed).

I’m working on an IBM Thinkpad X61, which has a “suspend to disc”
symbol printed in blue on the F12 key, which means Fn-F12 would, if
the operating system handles it, suspend to hard disc.

This key never did anything without elogind installed.

I just hit it by accident. The system immediately(!) became fully
unresponsible (could not even move the mouse pointer), but my xterm
with tail -F /var/log/syslog captured a number of lines. The first
three of it were:

Oct  4 01:09:22 tglase-nb vmunix: [1043273.743227] elogind-daemon[1640]: 
Hibernate key pressed.
Oct  4 01:09:22 tglase-nb vmunix: [1043273.747348] elogind-daemon[1640]: 
Hibernating...
Oct  4 01:09:22 tglase-nb vmunix: [1043273.749104] PM: Image not found (code 
-22)

This is clear evidence that elogind *actively* captured that keypress
and did something not normal (i.e. not present on a standard pre-systemd
system without elogind). Whatever it did apparently failed, but it STILL
proceeded to crash the whole system (with the screen flickering a number
of times and then the system suddenly powering off).

Upon starting it again (losing all my state, unsaved files I was writing,
and all that), I’ve seen the usual messages about problems with a dirty
filesystem, so it’s evident that elogind positively, actively crashed the
system instead of shutting it down cleanly, or, (which would have been the
correct thing to do) just returning and not doing *anything* after that
whatever it tried to do failed.

The other log messages I saw flickering by in xterm are, of course, not
preserved (ext4 “helpfully” inserted a whole block of NUL characters into
my /var/log/syslog file, though).

Now, from evidence to guesswork: from reading the log, I’m guessing it
actually *did* try to suspend to disc, failing to do so (naturally, as
this system is not set up for it, namely, the RAM is much larger than
the swap space, and no equivalent to Windows® 2000’s HIBERFIL.SYS was
set up either, mostly because I do not even *use* hibernation, nor do
I *want* it). But, like I said, that failure was mishandled.

Considering I actually lost (a small amount of) user data, I feel the
severity justified.

I’ve also just looked at the elogind.conf file I was told to change in
one of the two other bugreports I mentioned above. There is some config
regarding hibernation, so I guess, now that I know about the problem,
I could just turn off as a WORKAROUND *ONLY* (I *assume* changing
#HandleHibernateKey=hibernate
to  HandleHibernateKey=ignore
might do the trick) but then I wonder why this is not ignored by default,
and the failure to handle suspend-to-disc failure is still present (and
someone should probably check if systemd similarily suffers).

Anyway, this bugreport should point out something more: People *need*
to install libpam-elogind to satisfy package dependencies, which forces
elogind installation alongside; elogind now runs a dæmon which changes
system behaviour (compared to regular pre-systemd Debian) in unpredictable
ways, much to users’ detriment.

I believe there exist users who would wish for all these features, but
to me, who doesn’t even need them in the first place, a way of satisfying
packages without piling new bugs onto the system is direly needed.

Sorry for any grumpiness here, I’ve just lost some work and quite an
amount of session state and it’s half past one in the bloody night and
I visited the manuls (pallas cats) in the zoo earlier which provide for
appropriate grumpiness; I don’t intend any insult or something towards
any living being (just towards software).


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

Kernel: Linux 5.8.0-2-amd64 (SMP w/2 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages elogind depends on:
ii  dbus 1.12.20-1
ii  debconf  1.5.74
ii  libacl1  2.2.53-8
ii  libc62.31-3
ii  libcap2  1:2.43-1
ii  libelogind0  243.7-1+debian1
ii  libselinux1  3.1-2
ii  libudev1 246.6-1
ii  lsb-base 11.1.0

Versions of packages elogind recommends:
ii  libpam-elogind  243.7-1+debian1
ii  policykit-1 0.105-29

elogind suggests no packages.

-- Configuration Files:

Bug#971643: null pointer dereference with dpkg -V

[John Scott]

> Here's the relevant bit of code with a check to diagnose:
> void varbuf_add_buf(struct varbuf *v, const void *s, size_t size)
> {
>   varbuf_grow(v, size);
> + if(v->buf + v->used == NULL) {
> + puts((size == 0) ? "size is zero" : "size is not zero");
> + }
>   memcpy(v->buf + v->used, s, size);
>   v->used += size;
> }
> This prints "size is zero",

By the way one gets different behavior with if(v->buf + v->used == NULL)
vs. if(v->buf + v->used) even on uninstrumented binaries. With the latter
I get a bunch of lines like
size is not zero
size is not zero
size is not zero
...
and then later it alternates:
size is zero
size is not zero
size is zero
size is not zero
...

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

Bug#971643: null pointer dereference with dpkg -V

[John Scott]

Package: dpkg
Version: 1.20.5
Severity: normal
Tags: upstream
X-Debbugs-Cc: 

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

I cannot reproduce this on a Debian binary package. Hardening flags like
FORTIFY_SOURCE may keep this from being an issue. I found this fooling
around with ASan:
$ ./dpkg --admindir='/var/lib/dpkg' -V apt
varbuf.c:99:3: runtime error: null pointer passed as argument 1, which is 
declared to never be null

Here's the relevant bit of code with a check to diagnose:
void varbuf_add_buf(struct varbuf *v, const void *s, size_t size)
{
varbuf_grow(v, size);
+   if(v->buf + v->used == NULL) {
+   puts((size == 0) ? "size is zero" : "size is not zero");
+   }
memcpy(v->buf + v->used, s, size);
v->used += size;
}

This prints "size is zero", so maybe that's why this seems harmless:
memcpy() may not do anything and the same may go for adding 'size'.

- -- Package-specific info:
System tainted due to merged-usr-via-symlinks.

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

Kernel: Linux 5.8.0-2-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_WARN, TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 dpkg depends on:
ii  libbz2-1.0   1.0.8-4
ii  libc62.31-3
ii  liblzma5 5.2.4-1+b1
ii  libselinux1  3.1-2
ii  tar  1.30+dfsg-7
ii  zlib1g   1:1.2.11.dfsg-2

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt2.1.10
pn  debsig-verify  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQT287WtmxUhmhucNnhyvHFIwKstpwUCX3kADwAKCRByvHFIwKst
pwchAQDgoFTpjnnkcHbb6/KKL84JrmXebZR9YAKxmEkZ10Pq6gEAhqyXkMG3AVeq
I0LeSKIgP2NMNPAYXG/AsXynzvc5+wM=
=iKS8
-END PGP SIGNATURE-

Bug#971641: Reassign Bug#971641

[Wm Salt Hale]

reassign 971641 dpkg

thanks




I think this bug should have been submitted to dpkg, not
dpkg-parsechangelog. Also, please ignore the system information, it was not
filed from the computer where I reproduced the bug.

~ Salt

Bug#971070: fakeroot 1.25.1-1 breaks mmdebstrap

[Johannes Schauer]

Control: retitle -1 fakeroot 1.25.1-1 breaks fakechroot
Control: affects -1 fakechroot mmdebstrap
Control: tags -1 + patch

On Sun, 27 Sep 2020 10:30:54 +0200 Johannes 'josch' Schauer  
wrote:
> your recent upload of fakeroot broke my package mmdebstrap in a way that
> I do not yet understand. See for example this CI test which uses
> fakeroot via fakechroot:
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/m/mmdebstrap/7190912/log.gz
> 
> I get an even different error when running mmdebstrap locally with the
> new fakeroot version on my system:
> 
> $ mmdebstrap --variant=apt --mode=fakechroot unstable /dev/null
> fakechroot: nested operation is not supported
> E: need working fakechroot binary
> 
> If I downgrade fakeroot like this:
> 
> $ sudo apt install fakeroot=1.24-1 libfakeroot=1.24-1
> 
> then everything works fine again.
> 
> Maybe you can shed some light on the situation about what might've
> changed between 1.24-1 and 1.25.1-1 that leads to these problems?

I bisected the upstream commits and figured out that the problem was introduced
by commit 9b26ceaaba9796bc9e18f375be91da16a4aae04d. Upon closer inspection, I
noticed, that one renaming from LIB to FAKEROOT_LIB was omitted. The problem is
fixed by this patch:

--- a/scripts/fakeroot.in
+++ b/scripts/fakeroot.in
@@ -162,7 +162,7 @@ if test -n "$@LDLIBPATHVAR@"; then
 fi
 # ...and preloaded libs
 if test -n "$@LDPRELOADVAR@"; then
-  LIB="$FAKEROOT_LIB:$@LDPRELOADVAR@"
+  FAKEROOT_LIB="$FAKEROOT_LIB:$@LDPRELOADVAR@"
 fi

 export FAKEROOT_FD_BASE

Without this patch, the value of LD_PRELOAD will be ignored. This in turn
breaks other tools that rely on LD_PRELOAD like fakechroot. Without this patch:

$ fakechroot fakeroot sh -c 'echo $LD_PRELOAD'
libfakeroot-sysv.so

With this patch:

$ fakechroot fakeroot sh -c 'echo $LD_PRELOAD'
libfakeroot-sysv.so:libfakechroot.so

Thanks!

cheers, josch

signature.asc
Description: signature

Bug#906124: grub-efi-amd64: Also in grub-efi-amd64

[Vladislav Yarmak]

On Sat, 26 Sep 2020 22:33:42 + Victorien Berlot
 wrote:
> Hello,
> 
> Has this bug been fixed ?

Nope, but this bug was ported to Centos 8 and probably other distros.
TBH, looks like widespread bootchain sabotage to me.

BTW, NSA released technical report about secureboot recently:
https://media.defense.gov/2020/Sep/15/2002497594/-1/-1/0/CTR-UEFI-SECURE-BOOT-CUSTOMIZATION-20200915.PDF/CTR-UEFI-SECURE-BOOT-CUSTOMIZATION-20200915.PDF

Interesting fact, they skip initramdrive verification as well, and
modern distros make it's verification next to impossible.

-- 
Best Regards,
Vladislav Yarmak

Bug#971642: logidee-tools: Fails to build w/ latest TeX Live checkout

[Hilmar Preusse]

Package: logidee-tools
Version: 1.2.18
Severity: important
Tags: patch

Dear Maintainer,

   * What led up to the situation?

Recently we uploaded a new snapshot of the TeX Live texmf tree into Debian.
For our texlive-lang part a regression is reported: your package does not
build any more.

https://qa.debian.org/excuses.php?package=texlive-lang

Excuse for texlive-lang

Migration status for texlive-lang (2020.20200804-1 to 2020.20200925-1): 
BLOCKED: Rejected/violates migration policy/introduces a regression
Issues preventing migration:
autopkgtest for logidee-tools/1.2.18: amd64: Regression ♻ (reference ♻), 
arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻)
Additional info:
Piuparts tested OK - 
https://piuparts.debian.org/sid/source/t/texlive-lang.html
6 days old (needed 5 days)

The error message in the build log gives the idea that a LaTeX package is not
loaded either by the TeX code or the used LaTeX class file:


ABD: EveryShipout initializing macros

! LaTeX Error: Command \fnum@table undefined.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...  
  

I'm able to reproduce the issue here in a Debian unstable installation and
I could fix it by loading the longtable LaTeX package in the cls file.

Consider to upload a fixed package if you like the solution.

Hilmar

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 5.8.0-2-686-pae (SMP w/2 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages logidee-tools depends on:
ii  ghostscript9.53.2~dfsg-1
pn  imagemagick
ii  perl   5.30.3-4
ii  psutils1.17.dfsg-4
pn  texlive-fonts-recommended  
pn  texlive-lang-french
pn  texlive-lang-german
pn  texlive-latex-extra
pn  texlive-latex-recommended  
pn  texlive-pictures   
pn  texlive-pstricks   
ii  xsltproc   1.1.34-4

Versions of packages logidee-tools recommends:
pn  libxml2-utils  

logidee-tools suggests no packages.

-- 
sigmentation fault


signature.asc
Description: PGP signature

Bug#700060: ITP: ITP: growlight -- Disk manipulation and system preparation tool -- Disk manipulation and system preparation tool

[Nick Black]

as noted in bug #969408, pkern has graciously sponsored an
upload into the NEW queue, and growlight 1.2.13 will hopefully
find favor with the FTP Masters.

if so, this will successfully close a seven-year-old bug!

-- 
nick black -=- https://www.nick-black.com
to make an apple pie from scratch,
you need first invent a universe.

Bug#971604: qtbase-opensource-src FTCBFS: fails finding mysql

[Lisandro Damián Nicanor Pérez Meyer]

tag 971604 pending
thanks

Hi!

On Sat, 3 Oct 2020 at 11:02, Lisandro Damián Nicanor Pérez Meyer
 wrote:
>
> Hi!
>
> On Fri, 2 Oct 2020 at 17:24, Helmut Grohne  wrote:
> >
> > Source: qtbase-opensource-src
> > Version: 5.14.2+dfsg-6
> > Tags: patch upstream
> > User: debian-cr...@lists.debian.org
> > Usertags: ftcbfs
> >
> > We did have a few stabs at making qtbase-opensource-src cross buildable
> > already. At some point, it was running into an Exec format error when
> > running mysql_config and we concluded that this should be fixed on the
> > mariadb side. That's not gonna happen, because doing so would break
> > cross building mariadb. What needs to happens is that the world stops
> > using mysql_config. As bad as this sounds, the solution is quite simple,
> > because the building blocks are already included: pkg-config and
> > mysqlclient.pc. Please consider applying the attached one-line patch.
> [just for this part]
>
> I'm testing the patch to see if a normal buildstill works (you haven't
> at leats mentioned that). I would guess yes... but...

It built fine, so I merged it in the experimental branch.
Helmut: we plan to push a new Qt version "soon", so this particular
fix will be in there.

For the rest of the questions I still need to seat and check them,
although I think calling the build arch's qmake should be just fine.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Bug#971641: dpkg-parsechangelog: displays maintainer based on most recent uploader, rather than maintainer at time of change

[Wm Salt Hale]

Package: dpkg-parsechangelog
Version: 1.19.7
Severity: normal

Dear Maintainer,

When using dpkg-parsechangelog with the `--show-field maintainer` flag, I
noticed that the maintainer was showing the wrong individual.

Upon further inspection, it appears that this field is set based on the most
recent change, rather than using the maintainer that submitted the change.

This can be problematic, especially in cases of "Non-maintainer upload". An
example of this can be seen by issuing the following commands:

```
curl -s "https://metadata.ftp-master.debian.org/changelogs//main/libn/libnet-
dns-perl/libnet-dns-perl_1.19-1_changelog" | dpkg-parsechangelog --show-field
maintainer -v 0.68-1.2 -l -
```

I suspect that a complete fix will require adding a new field which references
the uploader.

~ Salt



-- System Information:
Debian Release: bullseye/sid
  APT prefers focal-updates
  APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), 
(100, 'focal-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.4.0-7642-generic (SMP w/4 CPU cores)
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 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#971638: Acknowledgement (live-boot: multiple stages cannot be specified to kernel command parameter break=)

[Wang Shanker]

This patch can also fix #971639

Bug#971639: live-boot: break=mountroot will make the boot process fail

[Wang Shanker]

Package: live-boot
Version: 1:20190614
Severity: important
Tags: upstream patch

When break=mountroot is specified in the kernel parameter, the
overiding maybe_break will pull in the functions defined in
/scripts/functions, overiding not only panic, but mount_* as well,
resulting those mount_* functions overriden by the stubs. 

The following patch in #971638 can also fix this issue.

From 1dde5d3680e0f7c475b9d58cb8337fa99515bdaa Mon Sep 17 00:00:00 2001
From: Miao Wang 
Date: Sun, 4 Oct 2020 04:57:40 +0800
Subject: [PATCH] Call orignial maybe_break in our overriden verison

Signed-off-by: Miao Wang 
---
components/9990-initramfs-tools.sh | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)

diff --git a/components/9990-initramfs-tools.sh 
b/components/9990-initramfs-tools.sh
index b251754..0954904 100755
--- a/components/9990-initramfs-tools.sh
+++ b/components/9990-initramfs-tools.sh
@@ -16,13 +16,12 @@ log_wait_msg ()

# Override maybe_break from scripts/functions
maybe_break()
-{
-   if [ "${break}" = "$1" ]; then
-   # Call original panic
-   . /scripts/functions
-   panic "Spawning shell within the initramfs"
-   fi
-}
+(
+   # Call original maybe_break
+   # which will call panic defined there
+   . /scripts/functions
+   maybe_break "$@"
+)

# Override panic from scripts/functions
panic()
--
2.28.0

-- Package-specific info:

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

Kernel: Linux 4.19.0-10-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages live-boot depends on:
ii  live-boot-initramfs-tools [live-boot-backend]  1:20190614

Versions of packages live-boot recommends:
pn  live-boot-doc  
ii  live-tools 1:20171207
pn  rsync  
pn  uuid-runtime   

Versions of packages live-boot suggests:
pn  cryptsetup  
pn  curlftpfs   
pn  httpfs2 
pn  wget

-- no debconf information

Bug#971638: live-boot: multiple stages cannot be specified to kernel command parameter break=

[Wang Shanker]

Package: live-boot
Version: 1:20190614
Severity: important
Tags: patch upstream

Since Stretch, initramfs-tools has provided support for specifying
multiple stages for the parameter break=, which was introduced in
the commit b215c18c of initramfs-tools (#795832). However, the function
`maybe_break` gets overriden in live-boot and multiple stages cannot be
specified. This can be reproduced by creating a live-boot image and use
qemu to boot it:

```
debootstrap --variant=minbase --merged-usr buster rootfs
chroot rootfs/ apt-get install --no-install-recommends linux-image-amd64 
live-boot busybox live-tools
chroot rootfs/ bash -c '/usr/sbin/busybox --list-full | while read cmd; do [ ! 
-e "$cmd" ] && ln -s /sbin/busybox "$cmd"; done'
mksquashfs rootfs/ livetest.squashfs -noI -noD -noF -noX -noappend -e boot
ln -s rootfs/vmlinuz rootfs/initrd.img ./
python3 -m http.server 8000 &
qemu-system-x86_64 -cpu kvm64 -machine pc,accel=kvm -smp 
cpus=1,cores=1,sockets=1 -m 2G  -chardev stdio,mux=on,id=char0 -netdev 
user,id=net0 -device e1000e,netdev=net0,id=net0 -monitor chardev:char0 -serial 
chardev:char0 -kernel vmlinuz -initrd initrd.img -append 
'fetch=http://xx.xx.xx.xx:8000/livetest.squashfs boot=live toram console=ttyS0 
break=mount,mountroot,bottom'
```

In the above senario, the boot process only stops at ``mount" stage, but
not at ``mountroot" and ``bottom".

The following patch can fix this bug by directly calling the original
`maybe_break` function provided by initramfs-tools.

From 1dde5d3680e0f7c475b9d58cb8337fa99515bdaa Mon Sep 17 00:00:00 2001
From: Miao Wang 
Date: Sun, 4 Oct 2020 04:57:40 +0800
Subject: [PATCH] Call orignial maybe_break in our overriden verison

Signed-off-by: Miao Wang 
---
components/9990-initramfs-tools.sh | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)

diff --git a/components/9990-initramfs-tools.sh 
b/components/9990-initramfs-tools.sh
index b251754..0954904 100755
--- a/components/9990-initramfs-tools.sh
+++ b/components/9990-initramfs-tools.sh
@@ -16,13 +16,12 @@ log_wait_msg ()

# Override maybe_break from scripts/functions
maybe_break()
-{
-   if [ "${break}" = "$1" ]; then
-   # Call original panic
-   . /scripts/functions
-   panic "Spawning shell within the initramfs"
-   fi
-}
+(
+   # Call original maybe_break
+   # which will call panic defined there
+   . /scripts/functions
+   maybe_break "$@"
+)

# Override panic from scripts/functions
panic()
-- 
2.28.0


-- Package-specific info:

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

Kernel: Linux 4.19.0-10-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages live-boot depends on:
ii  live-boot-initramfs-tools [live-boot-backend]  1:20190614

Versions of packages live-boot recommends:
pn  live-boot-doc  
ii  live-tools 1:20171207
pn  rsync  
pn  uuid-runtime   

Versions of packages live-boot suggests:
pn  cryptsetup  
pn  curlftpfs   
pn  httpfs2 
pn  wget

-- no debconf information

Bug#971637: prometheus-alertmanager: generate-ui.sh throws "ERROR: invalid option"

[Daniel Lo Nigro]

Package: prometheus-alertmanager
Version: 0.21.0+ds-2
Severity: normal
X-Debbugs-Cc: li...@d.sb

Dear Maintainer,

When I run /usr/share/prometheus/alertmanager/generate-ui.sh to install the web 
UI, the following error occurs:

Optimising source code...
ERROR: invalid option --output=/tmp/tmp.zMO98JwUjl/script.js

Changing line 26 from:

--mangle --output=$TMPDIR/script.js

to:

--mangle --output $TMPDIR/script.js

seems to fix the issue (that is, removing the `=` after `--output`).

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

Kernel: Linux 5.5.0-2-cloud-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 prometheus-alertmanager depends on:
ii  init-system-helpers  1.58
ii  libc62.31-3
ii  systemd-sysv 246.4-1

prometheus-alertmanager recommends no packages.

prometheus-alertmanager suggests no packages.

-- Configuration Files:
/etc/prometheus/alertmanager.yml changed [not included]

-- no debconf information

Bug#971636: undefined symbol: ZEND_HASH_GET_APPLY_COUNT

[Jörg Frings-Fürst]

Package: php-lua
Version: 2.0.5+1.1.0-3
Severity: grave


Hello,

after install php-lua I get:

> php -v
PHP Warning:  PHP Startup: Unable to load dynamic library 'lua.so' (tried: 
/usr/lib/php/20180731/lua.so (/usr/lib/php/20180731/lua.so: undefined symbol: 
ZEND_HASH_GET_APPLY_COUNT), /usr/lib/php/20180731/lua.so.so 
(/usr/lib/php/20180731/lua.so.so: cannot open shared object file: No such file 
or directory)) in Unknown on line 0
PHP 7.3.19-1~deb10u1 (cli) (built: Jul  5 2020 06:46:45) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.19, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.3.19-1~deb10u1, Copyright (c) 1999-2018, by Zend 
Technologies
with Xdebug v2.7.0RC2, Copyright (c) 2002-2019, by Derick Rethans

After remove php-lua it looks good:

> php -v
PHP 7.3.19-1~deb10u1 (cli) (built: Jul  5 2020 06:46:45) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.19, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.3.19-1~deb10u1, Copyright (c) 1999-2018, by Zend 
Technologies
with Xdebug v2.7.0RC2, Copyright (c) 2002-2019, by Derick Rethans

CU
Jörg

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

Kernel: Linux 4.19.0-11-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE:en_US:de_LU:de_CH:de_BE:de_AT (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages php-lua depends on:
ii  libapache2-mod-php7.3 [phpapi-20180731]  7.3.19-1~deb10u1
ii  libc62.28-10
ii  liblua5.2-0  5.2.4-1.1+b2
ii  php-common   2:69
ii  php7.3-cgi [phpapi-20180731] 7.3.19-1~deb10u1
ii  php7.3-cli [phpapi-20180731] 7.3.19-1~deb10u1
ii  php7.3-fpm [phpapi-20180731] 7.3.19-1~deb10u1
ii  php7.3-phpdbg [phpapi-20180731]  7.3.19-1~deb10u1
ii  ucf  3.0038+nmu1

php-lua recommends no packages.

php-lua suggests no packages.

-- no debconf information

Bug#971635: gnome-shell-extension-autohidetopbar: Not hiding on wayland window in gnome 3.38

[EdiD]

Package: gnome-shell-extension-autohidetopbar
Version: 20200921-1
Severity: normal

Top bar does not autohide on wayland window after upgrading from gnome
3.36 to 3.38
Autohiding is working as expected with X window


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing'), (110, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages gnome-shell-extension-autohidetopbar depends on:
ii  gnome-shell  3.38.0-2

Versions of packages gnome-shell-extension-autohidetopbar recommends:
ii  gnome-tweaks  3.34.0-4

gnome-shell-extension-autohidetopbar suggests no packages.

-- no debconf information

Bug#908617: (no subject)

[Jean-Philippe MENGUAL]

Hi,

It seems this bug is now fixed with the latest release of manpages-fr. 
Could you tell us if the bug is still here? Otherwise I will close it.


Regards

--
Jean-Philippe MENGUAL
Debian Developer non uploading
Community team member
Accessibility team member
debian-l10n-french team member
President of Debian France non-profit organization

Bug#971606: installation-reports cubieboard 5

[Geert Stappers]

Control: tag -1 moreinfo

On Sat, Oct 03, 2020 at 12:17:51AM +0300, Валериан Пережигин wrote:
> Package: installation-reports
> 
> Boot method: hd-media/sd-card-images + usb (fat32) with
> 
> debian-cd debian-10.6.0-armhf-xfce-CD-1.iso.
> 
> I was using uart (pl2303).
> Image version: 
> https://mirror.yandex.ru/debian-cd/10.6.0/armhf/bt-cd/debian-10.6.0-armhf-xfce-CD-1.iso.torrent
> Date: 2020-10-01 20:12 MSK
> 
> Machine: cubietech cubietrick plus (cubieboard 5)
> Processor: soc A83t (2GHz ?)
> Memory: 2GiB (DDR3 at 672MHz)
> 
> Comments/Problems:
> 
> No sdcard demonstrated, only usb and sata.
> No dp or hdmi.
> Installation to sata (manually prepared dos partitioning, just select 
> filesystems) sucsessed.
> Installation of u-boot climed sucsess yet failed (system was not bootable).
> 
> By main pc:
> 1. copyed boot partition (from sata) to sdcard.
> 2. installed by dd u-boot (from u-boot-sunxi_2020.10~rc5+dfsg-1_armhf.deb) to 
> sdcard.

Acknowledge


> 3. insertied sdcard to cb5.
> 
> System worked.

"System worked" as:   The installer came alive and showed behaviour as
seen at other installs ???


> But no video, no network, no sdcard.
> Uart work fine.
> Usb came up after long delay (with some errors).
> 
> Kernel update yet again claim no errors, but bootloader is stil to be 
> installed.
> 
> I regret sdcard not showed up.

Please rerun the installer, find a shell,  do  `lsblk`
and pretty please report back.



Regards
Geert Stappers
-- 
Silence is hard to parse

Bug#970261: RM: mrd6 -- ROM; No longer maintained

[Sean Whitton]

control: tag -1 + moreinfo

Hello,

On Sun 13 Sep 2020 at 10:41pm +01, Thomas Preud'homme wrote:

> Please remove mrd6 from the unstable distribution as it is no longer
> maintained since 2013. Quoting its README file [1]:
>
> "[note from the author, 2013: mrd6 is unsupported software. Since
>  2005 native multicast forwarding support has been added to Linux
>  and pim6sd can be used to manage it. mrd6's codebase is kept
>  around for historical reasons, it should still work in current
>  kernels and still allows you to do funky things with routing.
>  Feel free to fork. -hugo]"
>
> [1] https://github.com/hugosantos/mrd6/blob/master/README
>
> It currently has a popcon of 13.

Is there any evidence that it doesn't work?  Otherwise, I suggest just
orphaning it.

-- 
Sean Whitton

Bug#964693: Bullseye patch

[Stéphane Lesimple]

Hello,

The fix to fix qpxtool 0.8.0 compilation under Bullseye is trivial, it's just 
missing an #include.

The patch is attached to this mail.

Best regards,

Stéphane.


qpxtool-bullseye-fix.patch
Description: Binary data

Bug#971633: [Pkg-rust-maintainers] Bug#971633: debcargo: Debcargo should provide a man page

[Geert Stappers]

Control: severity -1 normal
Thanks

On Sat, Oct 03, 2020 at 10:49:43AM -0700, Diane Trout wrote:
> Package: debcargo
> Severity: wishlist
> 
> 
> Debian policy encourages all packages to provide a manpage.
> 
> §12.1 "If no manual page is available, this is considered as a bug and should
> be reported to the Debian Bug Tracking System (the maintainer of the package 
> is
> allowed to write this bug report themselves, if they so desire). Do not close
> the bug report until a proper man page is available"
> 
> It would be nice to have some included instructions about how to use debcargo.


It is normal to have instructions how to use a program.



My offer in this:

Write the usage text of debcargo, I'll convert it to manual page.



Regards
Geert Stappers

P.S.
If the usage text already exists, please say so.


signature.asc
Description: PGP signature

Bug#969118: RM: liblightify -- ROM; RoM

[Sean Whitton]

control: tag -1 + moreinfo

Hello,

On Thu 27 Aug 2020 at 10:03pm +02, Tobias Frost wrote:

> OSRAM discontinues Lightify soon and I have not really time anymore
> for (upstream) development, so lets drop it from Debian.

Hmm, the cloud services are turning off, but might people not want to
use this library to control their existing light bulbs rather than
having to throw them away?

-- 
Sean Whitton

Bug#969173: RM: openvas openvas-libraries openvas-cli openvas-manager -- ROM; replaced by gvm

[Sean Whitton]

control: tag -1 + moreinfo

Hello,

On Fri 28 Aug 2020 at 05:14pm +02, Raphaël Hertzog wrote:

> GVM is replacing OpenVAS and a bunch of source packages have been
> renamed or are obsolete.
>
> Please remove the following source packages from unstable:
> * openvas(replaced by gvm)
> * openvas-libraries  (replaced by gvm-libs)
> * openvas-cli(obsolete)
> * openvas-manager(replaced by gvmd)

We need one bug per source package for the sake of our scripts, please.

-- 
Sean Whitton

Bug#969095: RM: mysql-5.7 -- ROM; superseded by mysql-8.0

[Sean Whitton]

control: tag -1 + moreinfo

Hello,

On Thu 27 Aug 2020 at 05:48pm +01, Robie Basak wrote:

> Binary movements:
>
> libmysqld-dev is gone in src:mysql-8.0 - this feature is no longer
> supported upstream. The other binary packages have direct replacements:
>
> libmysqlclient20 -> libmysqlclient21
> s/5.7/8.0/
>
> There's also a new binary package mysql-router.

Looks like there is still a rdep on pytest-services.

-- 
Sean Whitton

Bug#969082: RM: austin [armhf mipsel] -- RoM; ANAIS

[Sean Whitton]

control: tag -1 + moreinfo

Hello,

On Thu 27 Aug 2020 at 09:49am +01, Gabriele wrote:

> May I kindly ask you to remove the austin binaries for architectures
> armhf and mipsel for the time being, in order to fix the issue
>
> Bug#968309: src:austin: fails to migrate to testing for too long:
> FTBFS on armhf and mipsel
>
> These binaries will not be requested again in future revisions
> until I can manage to fix the actual underlying issue with Austin.
> Unfortunately, I don't see a quicker way of dealing with this matter
> at the moment, as I don't have the time and resources to debug on the
> mentioned architectures.

Have you asked upstream about this?

Typically it is better to confirm that the bug is not a trivial fix
before resorting to removal.

-- 
Sean Whitton

Bug#968971: gitlab: Can't create new project: undefined method `set_attribute_was'

[Antoine Le Gonidec]

Here I am running 13.2.8-1+fto10+2 on top of a Debian Buster, following the recommended 
"FastTrack" installation method.

I get a similar error related to a missing "set_attribute_was" method when 
trying to add a new push mirror to an existing repository.

The only mentions I found of this method are in the following packages:
- ruby-acts-as-taggable-on: 
/usr/lib/ruby/vendor_ruby/acts_as_taggable_on/taggable/core.rb
- ruby-attr-encrypted: 
/usr/lib/ruby/vendor_ruby/attr_encrypted/adapters/active_record.rb

Both are installed from Buster backports:
- ruby-acts-as-taggable-on: 6.5.0-2~bpo10+1
- ruby-attr-encrypted: 3.1.0-2~bpo10+1

The method "set_attribute_was" used to be provided by ruby-activemodel in its 
5.* version (Buster and official Buster backports), but is not part of the 6.* version 
(FastTrack-provided backports).

If I remove the calls to "set_attribute_was" from the two listed .rb files and 
restart the gitlab service, I no longer get the crash on addition of a new push mirror. I 
attached the edited source files to this e-mail for testing purposes, but keep in mind 
that I am not a Ruby developer, I only removed some part of the scripts without worrying 
about the consequences. If you use these edited files without a careful review, things 
are expected to break in unexpected ways ;)


gitlab-set_attribute_was-crash-fixed-source-files.tar.xz
Description: application/xz


OpenPGP_0x4E34F6017289428A.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature

Bug#965219: Recipe for reproduction

[Paul Gevers]

Hi

Quotes from IRC for documentation purposes

[19:47:41] -*- elbrus is looking into bug #965219
[19:47:44] [zwiebelbot] Debian#965219: dbconfig-common: Write file error
(wrong owner) - https://bugs.debian.org/965219
[19:48:18]  does anybody know why root can't "exec > $file"
anymore in sid/bullseye?
[19:48:52]  (if file is owned by a different user and having
strict permissions)
[19:49:03]  it works in buster
[19:51:10]  elbrus: /proc/sys/fs/protected_regular. For
directories like /tmp
[19:52:06]  2 on my system
[19:52:34]  0 on the buster system I'm testing on
[19:53:04]  ansgar: can you point me at (or in the direction of)
some documentation about it?
[19:53:32]  elbrus: linux-doc,
Documentation/admin-guide/sysctl/fs.rst.gz
[19:53:41]  awesome, thanks
[19:53:48]  and I assume the default changed?
[19:54:05]  elbrus: It's clearly an unsafe operation as user
www-data could replace the file with a symlink to something else.
[19:54:14]  And then root would overwrite an unrelated file.
[19:54:26]  elbrus: Yes. It's a new feature.
[19:54:43]  that explains, I'll need to find a work around

Paul
PS: man proc.5 also has the info



signature.asc
Description: OpenPGP digital signature

Bug#971634: RFS: btrfsmaintenance/0.5-1 -- automate btrfs maintenance tasks on mountpoints or directories

[Nicholas D Steeves]

Package: sponsorship-requests
Severity: normal

Dear mentors and Sven,

I am looking for a sponsor for my package "btrfsmaintenance":

 * Package name: btrfsmaintenance
   Version : 0.5-1
   Upstream Author : David Sterba 
 * URL : https://github.com/kdave/btrfsmaintenance
 * License : GPL-2
 * Vcs : https://salsa.debian.org/sten-guest/btrfsmaintenance
   Section : admin

It builds those binary packages:

  btrfsmaintenance - automate btrfs maintenance tasks on mountpoints or 
directories

To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/btrfsmaintenance/

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/b/btrfsmaintenance/btrfsmaintenance_0.5-1.dsc

Changes since the last upload:

 btrfsmaintenance (0.5-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #970732)
 - /etc/default/btrfsmaintenance now optionally supports more granular
   systemd time and date specification.
 - balance, scrub, and trim are finally serialised as mutually exclusive
   operations.
 - Default filters for btrfs balance are now "5 10" for data (from "1 5 10
   20 30 40 50"), and "5" for metadata (from "1 5 10 20 30"); this means
   that less data is rewritten, and that less free space is recovered;
   this change mitigates some of the longstanding negative effects on
   system responsiveness during a balance operation because the work
   completes more quickly.
   * Drop leading white space from NEWS.Debian, and rename the file as "NEWS".
   * README.Debian: Note that btrfsmaintenance is not yet aware of a system's
 power state (on AC, battery, UPS), plus minor edits for polish.
   * README.Debian: Add Qu Wenruo's position against balancing, with
 citation.
   * Switch to debhelper-compat 13.
   * Override dh_installdeb to add missing executable bit to BASH scripts.
   * Set Rules-Requires-Root: no.
   * Add 0002-Add-doc-key-to-btrfsmaintenance-refresh.service.patch to address
 lintian complaint systemd-service-file-missing-documentation-key.
   * Update description to address new blk-mq default scheduler.
 (Closes: #970731)
   * Declare Standards-Version: 4.5.0. (No additional changes needed)

Regards,
--
  Nicholas D Steeves

Bug#971633: debcargo: Debcargo should provide a man page

[Diane Trout]

Package: debcargo
Version: 2.2.10-1
Severity: wishlist

Dear Maintainer,

I was trying to figure out how to package a rust package and the Debian wiki
suggested debcargo was the tool to help prepare a pacakge so I installed it.

I then discovered it didn't have any documentation.

Debian policy encourages all packages to provide a manpage.


§12.1 "If no manual page is available, this is considered as a bug and should
be reported to the Debian Bug Tracking System (the maintainer of the package is
allowed to write this bug report themselves, if they so desire). Do not close
the bug report until a proper man page is available"

It would be nice to have some included instructions about how to use debcargo.

Thanks
Diane Trout



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

Kernel: Linux 5.8.0-1-amd64 (SMP w/4 CPU threads)
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)
LSM: AppArmor: enabled

Versions of packages debcargo depends on:
ii  libc62.30-4
ii  libcurl3-gnutls  7.72.0-1
ii  libgcc-s1 [libgcc1]  10.1.0-1
ii  libgcc1  1:10.1.0-1
ii  libgit2-27   0.27.7+dfsg.1-0.2
ii  libssh2-11.8.0-2.1
ii  libssl1.11.1.1g-1
ii  quilt0.66-2.1
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages debcargo recommends:
ii  cargo  0.43.1-3

debcargo suggests no packages.

-- no debconf information

Bug#971630: severe memory issue in gnutls

[Björn JACKE]

Package: imagemagick-6.q16
Version: 8:6.9.10.23+dfsg-2.1+deb10u1
Severity: important

using "convert" to convert to pdf (and possible also other formats) is not 
allowed due to policy restriction:

convert test.jpeg  test.pdf
convert-im6.q16: attempt to perform an operation not allowed by the security 
policy `PDF' @ error/constitute.c/IsCoderAuthorized/408.

Bug#965219: Recipe for reproduction

[Paul Gevers]

Control: tags -1 confirmed
Control: severity -1 serious

Hi,

On 10-09-2020 21:07, Paul Gevers wrote:
> So, thanks for the report and the reproducer. I'll try to look into it soon.

While looking at the code, I swore this worked in the past. And so I
tested the following in testing:

paul@mulciber /tmp $ sudo su
root@mulciber:/tmp# touch bla
root@mulciber:/tmp# chmod go-r bla
root@mulciber:/tmp# chown paul: bla
root@mulciber:/tmp# ls -al bla
-rw--- 1 paul paul 0 okt  3 19:21 bla
root@mulciber:/tmp# exec > bla
bash: bla: Permission denied

However, when I do the following on a stable system:
admin@ci-worker05:/tmp$ sudo su
root@ci-worker05:/tmp# touch bla
root@ci-worker05:/tmp# chmod go-r bla
root@ci-worker05:/tmp# chown admin: bla
root@ci-worker05:/tmp# ls -al bla
-rw--- 1 admin admin 0 Oct  3 17:29 bla
root@ci-worker05:/tmp# exec > bla
root@ci-worker05:/tmp# echo hello
root@ci-worker05:/tmp# exit
admin@ci-worker05:/tmp$ cat /tmp/bla
hello

So, this is a regression from buster. I'll need to figure out where this
comes from and/or how to fix this. Suggestions welcome.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#971560: libsane-common 1.0.25-4.1+deb9u1 Stretch security update missing lots of files

[Sylvain Beucler]

Hi,

The package is in this state since Aug 17, I think we can afford to wait
a few more days for testing.
So yes, please do test on Tuesday.

Cheers!
Sylvain

On 03/10/2020 00:41, Ivan Baldo wrote:
> Hello.
> The soonest I could try to check, is this Tuesday 6th 19:00 -0300, sorry.
> Let me know if that's useful or too late.
> Thanks!
> 
> El vie., 2 de oct. de 2020 a la(s) 10:22, Sylvain Beucler
> (b...@beuc.net) escribió:
>>
>> Hi,
>>
>> On 02/10/2020 13:51, Ivan Baldo wrote:
>>> El vie., 2 de oct. de 2020 a la(s) 06:48, Sylvain Beucler
>>> (b...@beuc.net) escribió:

 Hi,

> El jue., 1 de oct. de 2020 a la(s) 19:32, Sylvain Beucler
> (b...@beuc.net) escribió:
>> This could be due to a bug when building the 'all' and 'amd64' packages
>> separately.

 I can reproduce the 2 debdiff-s with 'debuild -A' and 'debuild -B'
 respectively.

 I'm currently backporting fixes from 1.0.27-1~experimental3 to fix the
 issue, and updating our procedures to test this case in the future.
>>>
>>> Great, thanks a lot!!!
>>
>> I prepared a new package at:
>> https://www.beuc.net/tmp/debian-lts/sane-backends/
>> that I plan to upload as a regression fix.
>>
>> (Note: sane-dll is now consistently removed, as it previously evaded
>> deletion only in amd64, see #971592.)
>>
>> Can you test it?
>>
>> Cheers!
>> Sylvain
> 
> 
> 

Bug#968001: tightvnc-java: Invalid module description, or, may java module be mixed with other JARs in /usr/share/java?

[Sven Geuer]

Hello Guiseppe,

I am currently adopting the package and have a working unreleased
version of tightvnc-jave available, which was built applying openjdk-
11.

As I don't possess any specific java knowledge I cannot judge whether
this will fix the issue you reported. I will send you the deb file
attached to a separate email and would like to ask you to test whether
it fixes this bug for you. If it doesn't, I am afraid there is little
what can be done, as upstream is dead.

Regards,
Sven


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

Bug#971402: vboot-utils: FTBFS when fixfilepath is enabled from dpkg-buildflags

[Vagrant Cascadian]

On 2020-09-29, Vagrant Cascadian wrote:
> On 2020-09-29, Vagrant Cascadian wrote:
>> When the dpkg-buildflags "fixfilepath" is enabled, vboot-utils FTBFS, as
>> clang does not support the -ffile-prefix-map argument:
>>
>>   clang: clang: error: error: unknown argument: 
>> '-ffile-prefix-map=/<>=.'unknown argument: 
>> '-ffile-prefix-map=/<>=.'
>
> This is actually supported in clang-10, and appears to build fine with
> clang-10.
>
> New patch attached which switches to clang-10.

And it has come to my attention that the default clang will likely end
up being clang 11 for bullseye, so maybe testing with clang-11 instead,
or waiting till the clang default is upgraded in bullseye.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#971408: simde: FTBFS when dpkg-buildflags passes -ffile-prefix-map

[Vagrant Cascadian]

On 2020-09-29, Vagrant Cascadian wrote:
> When run with DEB_BUILD_OPTIONS=reproducible=+fixfilepath, simde FTBFS:
>
>   clang: error: unknown argument: '-ffile-prefix-map=/<>=.'
>
> This is because clang 10 is the first version to support
> -ffile-prefix-map, and simde is building with the default clang version
> 9.
>
> The attached patch updates to clang-10 to fix this issue.

Though clang 11 might become the default for bullseye, in which case
this would be a needless change; I haven't tested if simde builds fine
with clang 11.


> Alternately, you could stick with the default gcc, setting in
^ clang :)
> debian/rules:
>
>   # Remove when switching to clang 10 or newer.
>   export DEB_BUILD_MAINT_OPTIONS=reproducible=-fixfilepath+fixdebugpath

Oops, that should have been:

   # Remove when switching to clang 10 or newer.
   export DEB_BUILD_MAINT_OPTIONS=reproducible=-fixfilepath,+fixdebugpath

Though from a reproducible builds perspective, building with a version
of clang that supports -ffile-prefix-map is still preferable to
disabling the feature.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#971632: ITP: r-bioc-noiseq -- Exploratory analysis and differential expression for RNA-seq

[Steffen Moeller]

Package: wnpp
Severity: wishlist

Subject: ITP: r-bioc-noiseq -- Exploratory analysis and differential expression 
for RNA-seq
Package: wnpp
Owner: Steffen Moeller 
Severity: wishlist

* Package name: r-bioc-noiseq
  Version : 2.31.0
  Upstream Author : Sonia Tarazona
* URL : https://bioconductor.org/packages/NOISeq/
* License : Artistic-2.0
  Programming Lang: GNU R
  Description : Exploratory analysis and differential expression for RNA-seq
   data
 Analysis of RNA-seq expression data or other similar kind
 of data. Exploratory plots to evualuate saturation, count
 distribution, expression per chromosome, type of detected
 features, features length, etc. Differential expression between
 two experimental conditions with no parametric assumptions.

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

Bug#971631: udev: /bin/setfacl -m g:scanner:rw ' failed when USB scanner plugged in

[Chris Hofstaedtler]

Control: reassign -1 sane-backends 

Hello Joe,

* Joe Rowan  [201003 15:43]:
> Not really sure which package is responsible for this, but I'll try udev.

sane-backends provides the scanner rules for udev, so I'm
reassigning your bug report. I hope the sane-backends maintainers
can help you.

Best,
Chris

Bug#971617: rakudo: failed upgrade: Missing or wrong version of dependency 'gen/moar/stage2/MASTNodes.nqp'

[Dominique Dumont]

On Sat, 03 Oct 2020 09:17:00 +0200 Marc Glisse  
wrote:
>   rakudo-helper.pl: Reinstalling all perl6 modules ...
> (1/3) reinstall: perl6-zef
> Unhandled exception: Missing or wrong version of dependency 'gen/moar/
stage2/MASTNodes.nqp' (from 'gen/moar/Pod.nqp')

I've reproduced this issue.

nqp-data is missing *.nqp files. Looks like nqp's build system no longer 
install these files.

I don't know if this an expected behavior or a bug on nqp side. I've opened 
https://github.com/Raku/nqp/issues/675 to track this issue upstream.

In the meantime, I'm going to tweak debian/rules to install the missing nqp 
files until this issue is sorted out upstream.

All the best

Bug#929707: [debian-mysql] Bug#929707: mariadb-client-10.1: import of "mysqldump --all-databases" fails with "ERROR 1062 (23000): Duplicate entry"

[Matija Nalis]

Yes, I can write a shell test scripts which looks like 
https://salsa.debian.org/mariadb-team/mariadb-10.5/-/blob/master/debian/tests/smoke

and verify that (when run from shell) it fails with non-zero
errorlevel in Stretch mariadb, and passes with 0 on Buster mariadb.

If that is enough? (I don't really have resources ATM to setup build
environment and do full-build checks etc)


On Tue, Sep 29, 2020 at 11:44:12PM +0300, Otto Kekäläinen wrote:
> Thanks!
> 
> Would you like to test with mariadb-10.5 in unstable as well?
> 
> Or perhaps contribute by writing a small autopkgtest extension (the
> debian/tests files in the packaging repository at
> https://salsa.debian.org/mariadb-team/mariadb-10.5) that runs this
> dump and thus ensure forever that this feature will not regress?

-- 
Opinions above are GNU-copylefted.

Bug#941345: Acknowledgement (git-buildpackage: Option --git-arch ignored when constructing the GBP_CHANGES_FILE variable for the postbuild hook)

[Roger Shimizu]

control: tags -1 +patch

I also met this issue, and verified above patch really works in my environment.
So enclose the patch and hope this can be merged into mainline soon.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
From: Heiko Schlittermann 
Date: Sun, 29 Sep 2019 11:56:33 +0200
Subject: [PATCH] No ignore option --git-arch when constructing the GBP_CHANGES_FILE variable for the postbuild hook

Closes: #941345
---
 gbp/scripts/buildpackage.py | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/gbp/scripts/buildpackage.py b/gbp/scripts/buildpackage.py
index 9b3d67f..dc86592 100755
--- a/gbp/scripts/buildpackage.py
+++ b/gbp/scripts/buildpackage.py
@@ -287,7 +287,7 @@ def disable_hooks(options):
 setattr(options, hook, '')
 
 
-def changes_file_suffix(builder, dpkg_args):
+def changes_file_suffix(builder, dpkg_args, arch):
 """
 >>> changes_file_suffix('debuild', ['-A'])
 'all'
@@ -306,15 +306,15 @@ def changes_file_suffix(builder, dpkg_args):
 elif '-A' in args:
 return 'all'
 else:
-return os.getenv('ARCH', None) or du.get_arch()
+return arch or os.getenv('ARCH', None) or du.get_arch()
 
 
-def changes_file_name(source, build_dir, builder, dpkg_args):
+def changes_file_name(source, build_dir, builder, dpkg_args, arch):
 return os.path.abspath("%s/../%s_%s_%s.changes" %
(build_dir,
 source.changelog.name,
 source.changelog.noepoch,
-changes_file_suffix(builder, dpkg_args)))
+changes_file_suffix(builder, dpkg_args, arch)))
 
 
 def check_branch(repo, options):
@@ -514,7 +514,7 @@ def main(argv):
  else source.upstream_version)
 export_dir = os.path.join(output_dir, "%s-%s" % (source.sourcepkg, major))
 build_dir = export_dir if options.export_dir else repo.path
-changes_file = changes_file_name(source, build_dir, options.builder, dpkg_args)
+changes_file = changes_file_name(source, build_dir, options.builder, dpkg_args, options.pbuilder_arch)
 
 # Run preexport hook
 if options.export_dir and options.preexport:

Bug#963746: nfs-common: Random Segmentation Violations of rpc.gssd Daemon

[Kraus, Sebastian]

root@all:~# coredumpctl debug 
   PID: 26824 (rpc.gssd)
   UID: 0 (root)
   GID: 0 (root)
Signal: 11 (SEGV)
 Timestamp: Sat 2020-10-03 10:29:16 CEST (5h 38min ago)
  Command Line: /usr/sbin/rpc.gssd -vvv -rrr -t 3600 -T 10
Executable: /usr/sbin/rpc.gssd
 Control Group: /system.slice/rpc-gssd.service
  Unit: rpc-gssd.service
 Slice: system.slice
   Boot ID: e60fc71ee667413c98017762004c67f2
Machine ID: d3d1247edbd7490591d291e33e196b79
  Hostname: all
   Storage: 
/var/lib/systemd/coredump/core.rpc\x2egssd.0.e60fc71ee667413c98017762004c67f2.26824.160171375600.lz4
   Message: Process 26824 (rpc.gssd) of user 0 dumped core.

Stack trace of thread 4596:
#0  0x563f504ab38e create_auth_rpc_client (rpc.gssd)
#1  0x563f504ab9f8 krb5_use_machine_creds (rpc.gssd)
#2  0x563f504abb92 process_krb5_upcall (rpc.gssd)
#3  0x563f504ac3b3 handle_gssd_upcall (rpc.gssd)
#4  0x7f13dcd4dfa3 start_thread (libpthread.so.0)
#5  0x7f13dcc7e4cf __clone (libc.so.6)

Stack trace of thread 26824:
#0  0x7f13dcc73819 __GI___poll (libc.so.6)
#1  0x7f13dcb59207 send_dg (libresolv.so.2)
#2  0x7f13dcb56c43 __GI___res_context_query (libresolv.so.2)
#3  0x7f13dcb31536 __GI__nss_dns_gethostbyaddr2_r 
(libnss_dns.so.2)
#4  0x7f13dcb31823 _nss_dns_gethostbyaddr_r 
(libnss_dns.so.2)
#5  0x7f13dcc8fee2 __gethostbyaddr_r (libc.so.6)
#6  0x7f13dcc987d5 gni_host_inet_name (libc.so.6)
#7  0x563f504aa455 gssd_get_servername (rpc.gssd)
#8  0x563f504aa82c gssd_read_service_info (rpc.gssd)
#9  0x563f504ab067 gssd_inotify_clnt (rpc.gssd)
#10 0x7f13dcf269ba event_persist_closure (libevent-2.1.so.6)
#11 0x7f13dcf27537 event_process_active (libevent-2.1.so.6)
#12 0x563f504a8eaa main (rpc.gssd)
#13 0x7f13dcba909b __libc_start_main (libc.so.6)
#14 0x563f504a903a _start (rpc.gssd)

GNU gdb (Debian 8.2.1-2+b3) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/sbin/rpc.gssd...Reading symbols from 
/usr/lib/debug/.build-id/97/484761d181f6a900fc8e41e4ff6cf038e00e4c.debug...done.
done.
[New LWP 4596]
[New LWP 26824]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/sbin/rpc.gssd -vvv -rrr -t 3600 -T 10'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x563f504ab38e in create_auth_rpc_client (clp=clp@entry=0x563f50687c30, 
tgtname=tgtname@entry=0x563f5069e67f "h...@client.domain.tu-berlin.de", 
clnt_return=clnt_return@entry=0x7f13dcb2cde8, 
auth_return=auth_return@entry=0x7f13dcb2cd50, uid=uid@entry=0, 
cred=cred@entry=0x0, authtype=0) at gssd_proc.c:352
352 gssd_proc.c: No such file or directory.
[Current thread is 1 (Thread 0x7f13dcb2d700 (LWP 4596))]
(gdb) set pagination off
(gdb) bt full
#0  0x563f504ab38e in create_auth_rpc_client (clp=clp@entry=0x563f50687c30, 
tgtname=tgtname@entry=0x563f5069e67f "h...@client.domain.tu-berlin.de", 
clnt_return=clnt_return@entry=0x7f13dcb2cde8, 
auth_return=auth_return@entry=0x7f13dcb2cd50, uid=uid@entry=0, 
cred=cred@entry=0x0, authtype=0) at gssd_proc.c:352
rpc_clnt = 0x0
sec = {mech = 0x563f504b7590 , qop = 0, svc = 
RPCSEC_GSS_SVC_NONE, cred = 0x7f13d80024d0, req_flags = 2}
auth = 0x0
retval = -1
min_stat = 256
rpc_errmsg = '\000' , 

Bug#971630:

[debianbugs]

retitle: Imagemagick convert can't convert to PDF

Bug#971604: qtbase-opensource-src FTCBFS: fails finding mysql

[Lisandro Damián Nicanor Pérez Meyer]

Hi!

On Fri, 2 Oct 2020 at 17:24, Helmut Grohne  wrote:
>
> Source: qtbase-opensource-src
> Version: 5.14.2+dfsg-6
> Tags: patch upstream
> User: debian-cr...@lists.debian.org
> Usertags: ftcbfs
>
> We did have a few stabs at making qtbase-opensource-src cross buildable
> already. At some point, it was running into an Exec format error when
> running mysql_config and we concluded that this should be fixed on the
> mariadb side. That's not gonna happen, because doing so would break
> cross building mariadb. What needs to happens is that the world stops
> using mysql_config. As bad as this sounds, the solution is quite simple,
> because the building blocks are already included: pkg-config and
> mysqlclient.pc. Please consider applying the attached one-line patch.
[just for this part]

I'm testing the patch to see if a normal buildstill works (you haven't
at leats mentioned that). I would guess yes... but...

Dmitry: if it builds I'll be merging this in some hours.


-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Bug#971401: texlive-binaries: triggers update-alternatives warning for bibtex

[Gabriele Stilli]

Il 03/10/20 11:48, Hilmar Preuße ha scritto:

> The new TL base migrated into testing, so the issue should be gone
> now. Could you retest?
Hello,

after upgrading I tried to reinstall texlive-binaries a first time and
the error was there. Tried a second time and it was gone. Probably on
the first attempt the update-alternatives database was still broken and
needed a repair. Log follows. A third run didn't show the error either.

Thanks again!

Regards,
Gabriele

root@camelot:~# LC_ALL=C apt-get install --reinstall texlive-binaries
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not
upgraded.
Need to get 0 B/10.1 MB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 424725 files and directories currently installed.)
Preparing to unpack .../texlive-binaries_2020.20200327.54578-5_amd64.deb ...
Unpacking texlive-binaries (2020.20200327.54578-5) over
(2020.20200327.54578-5) ...
Setting up texlive-binaries (2020.20200327.54578-5) ...
update-alternatives: warning: forcing reinstallation of alternative
/usr/bin/bibtex.original because link group bibtex is broken
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for install-info (6.7.0.dfsg.2-5) ...
install-info: warning: no info dir entry in
`/usr/share/info/automake-history.info.gz'
Processing triggers for tex-common (6.15) ...
Building format(s) --all.
This may take some time... done.
==  How can you help?  (doc: https://wiki.debian.org/how-can-i-help)
==

-  Show old opportunities as well as new ones: how-can-i-help --old
-
root@camelot:~# LC_ALL=C apt-get install --reinstall texlive-binaries
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not
upgraded.
Need to get 0 B/10.1 MB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 424725 files and directories currently installed.)
Preparing to unpack .../texlive-binaries_2020.20200327.54578-5_amd64.deb ...
Unpacking texlive-binaries (2020.20200327.54578-5) over
(2020.20200327.54578-5) ...
Setting up texlive-binaries (2020.20200327.54578-5) ...
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for install-info (6.7.0.dfsg.2-5) ...
install-info: warning: no info dir entry in
`/usr/share/info/automake-history.info.gz'
Processing triggers for tex-common (6.15) ...
Building format(s) --all.
This may take some time... done.
==  How can you help?  (doc: https://wiki.debian.org/how-can-i-help)
==

-  Show old opportunities as well as new ones: how-can-i-help --old
 -

Bug#971627: 100% cpu on resume of transfer

[Kurt Roeckx]

On Sat, Oct 03, 2020 at 02:08:54PM +0200, Paul Slootman wrote:
> On Sat 03 Oct 2020, Kurt Roeckx wrote:
> > 
> > I was transfering a large file using rsync (3 TB). The connection
> > broke after about 1 TB. I was using the -P option. So I restarted
> > the transfer. But that transfer resulted in 100% CPU usage on the
> > sender side, and limiting the transfer to about 1.5 MB/s.
> > 
> > It also seems that when I restart the transfer, it first reads the
> > 1 TB on the client side, and then reads the 1 TB on the sender
> > side, causing a large delay before restarting the transfer.
> 
> This is normal, as rsync first has to verify that the 1TB on the
> destination is correct and identical to the data on the source.
> 
> If you are certain that the part already transmitted to the destination
> is correct, you can use --append to only send the remaining part of the
> file.

Is the 100% CPU usage also expected?

As one debian mirror admins, I also run an rsync server. I often
see rsync using 100% cpu, but I never knew why. I now assume that
the transfer was broken when they were mirroring the .iso image
from me.


Kurt

Bug#971629: crrcsim: add sceneries and planes to the crrcsim package

[a463b]

Package: crrcsim
Version: 0.9.13

This 'bug report' is a very kind request for adding data files to crrcsim:

[A] The first request is to add the data from 

http://joel.lienard.free.fr/crrcsim/index-en.html

to the crrcsim package in Debian. These sceneries are really spectacular and 
completely transform the experience of crrcsim. 

Mr. Liénard was so kind to attribute the "Creative Commons 
Attribution-ShareAlike 4.0 International License" to his work today to allow 
the inclusion into Linux distributions. The (CC-BY-SA) v4.0 is part of the 
DFSGLicenses.


[B] This report also highly suggests that the scenery

LesBusards

of Mr. Liénard's work becomes the default scenery for crrcsim. 

After comparing the original default scenery and the LesBusards scenery, I hope 
you will agree that LesBusards is as general purpose as the original default 
scenery but far more beautiful and realistic.


[C]) If the license for the additional planes 

https://sourceforge.net/projects/crrcsim/files/crrcsim-addon-models/CRRCsim-addon-models-0.2.0/

of the original crccsim project is the same as for crccsim itself, then it 
would be good to include them into the Debian crrcsim package also.

Sincerely,

Peter

Bug#966311: gnucash: please upgrade to newer upstream version

[Dmitry Smirnov]

On Monday, 27 July 2020 1:24:44 AM AEST Gabriel F. T. Gomes wrote:
> Upstream gnucash released a new stable version, 4.0 [1]. Among the new
> features, the "type-ahead search" would be very welcome.

Thanks for reminder.


> Could you update it in Debian, please? :)

Sure. :)

Packaging for new release is committed and upload is pending.


> If you need help, just let me know.

Yes, I'd appreciate any help please. I'm at the limit of my capacity.


> I could submit a merge request at Salsa if you would like that,

That's one way to do things. Or you could just become co-maintainer and
we can sort out your direct commits between us.


> although I think it would be a little
> weird because gbp will update three different branches.

I prefer to stay away from GBP:

  * https://salsa.debian.org/onlyjob/notes/-/wikis/no-gbp
  * https://salsa.debian.org/onlyjob/notes/-/wikis/bp

-- 
All the best,
 Dmitry Smirnov
 GPG key : 4096R/52B6BBD953968D1B

---

Tyranny is always better organized than freedom.

---

Multiple errors in the New York Times article about Sweden’s corona strategy
-- Emanuel Karlsten, 
https://emanuelkarlsten.se/multiple-errors-in-the-new-york-times-article-about-swedens-corona-strategy/


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

Bug#971549: ITP: golang-github-dgryski-go-metro -- metrohash library in golang

[Roger Shimizu]

This is a new dependency of golang-github-seiflotfy-cuckoofilter.
Already uploaded to NEW, and gits pushed to:
- https://salsa.debian.org/go-team/packages/golang-github-dgryski-go-metro

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#971628: Whipper: Missing dependency on python3-distutils

[Brandon Werner]

Package: whipper
Version: 0.9.0-4

Hello,
I tried to install and use whipper and got a traceback. Installling the 
python3-distutils package solved the issue.

Bug#936268: caldav-tester: Python2 removal in sid/bullseye

[Jonas Smedegaard]

Quoting Petter Reinholdtsen (2020-10-03 12:05:25)
> 
> I am sorry I failed to annouce it on a list where the people interested
> in looking after caldav-tester were present.

Water under the bridge :-)


> I am very happy you decide to take a look at reviving this package.  I 
> hope you succeed in porting it to python 3 and getting feedback from 
> upstream.

Thanks.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#971627: 100% cpu on resume of transfer

[Kurt Roeckx]

Package: rsync
Version: 3.1.3-6

Hi,

I was transfering a large file using rsync (3 TB). The connection
broke after about 1 TB. I was using the -P option. So I restarted
the transfer. But that transfer resulted in 100% CPU usage on the
sender side, and limiting the transfer to about 1.5 MB/s.

It also seems that when I restart the transfer, it first reads the
1 TB on the client side, and then reads the 1 TB on the sender
side, causing a large delay before restarting the transfer.

Both sides have the same version installed.


Kurt

Bug#971626: markdown plugin is missing in buster

[hmartin]

Package: geany-plugins
Version: 1.36+dfsg-1

Believing the last comment in 
https://github.com/geany/geany-plugins/issues/757 , the plugin is 
available and could be included.
However I notice that geany-plugin-markdown isn't included in Debian 
since buster (https://packages.debian.org/stretch/geany-plugin-markdown)


Is it possible to include it again ?

Regards,

Bug#969788: nextcloud-desktop: Upgrade removed part of configuration

[Markus Frosch]

> > from my side it seems like not many people have the problem that the 
> > configuration is lost while doing the upgrade. So I think, it is just a
> > normal 
> > bug you found. Please report it upstream and provide us the url, so that we 
> > can track the upstream status.
> > 
> > hefee

This bug could be related, it sounds like an iteration problem when updating the
folder selection DB from 2.x to 3.x

https://github.com/nextcloud/desktop/pull/2435

Backport: https://github.com/nextcloud/desktop/pull/2436

It should be included in 3.0.2 - so I suggest to update to 3.0.2 and close this
bug for now...

Best Regards
Markus Frosch
-- 
lazyfro...@debian.org
https://lazyfrosch.de

Bug#971625: libcups2-dev: please include a cups.pc for pkg-config

[Helmut Grohne]

Package: libcups2-dev
Version: 2.3.3-3
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:gnome-settings-daemon

gnome-settings-daemon fails to cross build from source, because it
cannot locate cups. It uses meson to do so an meson attempts multiple
methods. First, it looks for a pkg-config file, but that's missing. Then
it tries cups-config, but those tools are often broken during cross
compilation, so it skips this unless specifically instructed. During
native builds, it locates cups using cups-config. Then it tries cmake
snippets, but those are also missing.

Since pkg-config is well-supported, I think cups should adopt it, too.
I'm attaching a patch that adds a basic cups.pc to the package without
integrating it into the upstream build, because this approach was a lot
simpler and it suffices to show that the solution makes
gnome-settings-daemon cross buildable. Integrating it upstream would
make sense anyhow if upstream agrees. The attached cups.pc is quite
minimal though and does not cover the full functionality that
cups-config provides. If going upstream, it would likely gain a little
more contant. Going upstream would also raise the question of how to
handle cups-config --libs --image. I suppose that this would be turned
into adding a separate cupsimage.pc. Likely, a proper solution involves
discussion with upstream.

Please consider applying and/or upstreaming the attached patch.

Helmut
diff --minimal -Nru cups-2.3.3/debian/changelog cups-2.3.3/debian/changelog
--- cups-2.3.3/debian/changelog 2020-09-03 09:27:04.0 +0200
+++ cups-2.3.3/debian/changelog 2020-10-03 11:14:42.0 +0200
@@ -1,3 +1,10 @@
+cups (2.3.3-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Provide a cups.pc file. (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 03 Oct 2020 11:14:42 +0200
+
 cups (2.3.3-3) unstable; urgency=medium
 
   [ Didier Raboud ]
diff --minimal -Nru cups-2.3.3/debian/clean cups-2.3.3/debian/clean
--- cups-2.3.3/debian/clean 1970-01-01 01:00:00.0 +0100
+++ cups-2.3.3/debian/clean 2020-10-03 11:14:42.0 +0200
@@ -0,0 +1 @@
+debian/cups.pc
diff --minimal -Nru cups-2.3.3/debian/cups.pc.in cups-2.3.3/debian/cups.pc.in
--- cups-2.3.3/debian/cups.pc.in1970-01-01 01:00:00.0 +0100
+++ cups-2.3.3/debian/cups.pc.in2020-10-03 11:14:42.0 +0200
@@ -0,0 +1,7 @@
+Name: cups
+Description: cups application integration library
+URL: https://www.cups.org/
+Version: @DEB_VERSION_UPSTREAM@
+Cflags:
+Libs: -lcups
+Libs.private:
diff --minimal -Nru cups-2.3.3/debian/rules cups-2.3.3/debian/rules
--- cups-2.3.3/debian/rules 2020-09-03 09:27:04.0 +0200
+++ cups-2.3.3/debian/rules 2020-10-03 11:14:42.0 +0200
@@ -16,6 +16,7 @@
 export DSOFLAGS = $(shell dpkg-buildflags --get LDFLAGS)
 
 include /usr/share/dpkg/architecture.mk
+include /usr/share/dpkg/pkg-info.mk
 
 %:
dh $@ --without autoreconf
@@ -188,6 +189,9 @@
 ifneq (,$(filter libcups2-dev,$(shell dh_listpackages)))
# debian/libcups2-dev.install entry cannot rename files on-the-fly
cp cups/language-private.h debian/libcups2-dev/usr/include/cups/i18n.h
+   # debian/libcups2-dev.install cannot interpolate before compat 13
+   sed -e 's/@DEB_VERSION_UPSTREAM@/${DEB_VERSION_UPSTREAM}/' < 
debian/cups.pc.in > debian/cups.pc
+   install -D -m 644 debian/cups.pc 
debian/libcups2-dev/usr/lib/${DEB_HOST_GNU_TYPE}/pkgconfig/cups.pc
 endif
 
 ifneq (,$(filter cups-daemon,$(shell dh_listpackages)))

Bug#969788: Fwd: Re: Bug#969788: nextcloud-desktop: Upgrade removed part of configuration

[Markus Frosch]

Control: severity -1 important

Somehow this message didn't reach the BTS...

 Forwarded Message 
Von: Sandro Knauß 
An: Tobias Frost , 969...@bugs.debian.org, Markus Frosch <
lazyfro...@debian.org>, Erwan David 
Betreff: Re: Bug#969788: nextcloud-desktop: Upgrade removed part of 
configuration
Datum: Thu, 24 Sep 2020 21:04:34 +0200

> Control: severity 969576 important
> 
> Hey,
> 
> from my side it seems like not many people have the problem that the 
> configuration is lost while doing the upgrade. So I think, it is just a
> normal 
> bug you found. Please report it upstream and provide us the url, so that we 
> can track the upstream status.
> 
> hefee
> 
> --
> On Donnerstag, 10. September 2020 20:16:48 CEST you wrote:
> > On Thu, 10 Sep 2020 19:27:37 +0200 Tobias Frost  wrote:
> > > I'll see if I can find some logs…
> > 
> > Ok, it seems so that my instance deletes its configuration itself…
> > 
> > But I think that needs a word on my configuration:
> > ~/Documents is synced with my Nextcloud intance
> > I have setup XDG_DATA and XDG_CONFIG to be on
> > ~/Documents/XDG/$hostname/{XDG_DATA XDG_CONFIG}
> > (to be able to share XDG configurations files on complicant apps more easy
> > between PCs)
> > 
> > ~/Documents/XDG/isildor/XDG_CONFIG/Nextcloud is a symlink to
> > ~/.config/Nextcloud (so it is not on the share)
> > 
> > It seems that nextcloud app is deleting that file, (following the symlink)
> > 
> > Of course this could be a read herring, as I naively tried to reconfigure
> > the nextcloud without deleting Documents and I just got conflict everywhere
> > now.
> > 
> > It is possible the the app is following the symlink and thinks, hey , file
> > not on the nextcloud server, delete it… Could be another bug though; (I
> > guess it should not follow symlinks, at least it used to ignore symlinks
> > when syncing to servers)
> > 
> > Next step I'll try a fresh resync…
> 
> -- 
> Mein öffentlicher Schlüssel / My public key: E68031D299A6527C 
> Fingerabdruck / Fingerprint:
> D256 4951 1272 8840 BB5E  99F2 E680 31D2 99A6 527C 
> Runterladen z.B. bei/ Get it e.g. here:
> pool.sks-keyservers.net, ...
> 
> Ich habe meinen Schlüssel 2015 gewechselt / I've switched my GnuPG key 2015.
> Hier ein Dokument, was meinen Wechsel deutlich macht ( mit beiden Schlüsseln 
> unterschrieben)
> Here's a document, that proves I wanted to do this switch ( it is signed by 
> both keys)
> http://sandroknauss.de/files/transition2015.asc

-- 
mar...@lazyfrosch.de
https://lazyfrosch.de

Bug#936268: caldav-tester: Python2 removal in sid/bullseye

[Petter Reinholdtsen]

I am sorry I failed to annouce it on a list where the people interested
in looking after caldav-tester were present.  I am very happy you decide
to take a look at reviving this package.  I hope you succeed in porting
it to python 3 and getting feedback from upstream.

-- 
Happy hacking
Petter Reinholdtsen

Bug#971624: RM: haskell-gi-gtk-hs [armhf] -- ROM; missing build dependency

[Ilias Tsitsimpis]

Package: ftp.debian.org
Severity: normal

The latest version of haskell-gi-gtk FTBFS on armhf (ghc: out of memory,
see ROM #970642).

Please remove haskell-gi-gtk-hs (build-depends on haskell-gi-gtk)
from armhf.

Thanks,

-- 
Ilias

Bug#971401: texlive-binaries: triggers update-alternatives warning for bibtex

[Hilmar Preuße]

Am 30.09.2020 um 00:09 teilte Gabriele Stilli mit:

Hi Gabriele,


while configuring texlive-binaries, the following warning appeared:

update-alternatives: warning: forcing reinstallation of alternative
/usr/bin/bibtex.original because link group bibtex is broken
update-alternatives: warning: not replacing
/usr/share/man/man1/bibtex.1.gz with a link

The warning is reproducible on subsequent reinstallations.

The new TL base migrated into testing, so the issue should be gone now. 
Could you retest?


Hilmar
--
#206401 http://counter.li.org



OpenPGP_signature
Description: OpenPGP digital signature

Bug#966327: ITP: foot -- Fast, lightweight and minimalistic Wayland terminal emulator

[Jonas Smedegaard]

Hi,

Thanks for packaging foot!

I notice that several new releases have been issued upstream since the 
Debian release now pending in NEW queue.  I encourage you release newer 
Debian packages - that is handled gracefully by the NEW queue, and eases 
work for those like me super-eager to use it and building sneak-peak 
local packages from git :-)

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#971623: review and simplify the /devel/wnpp section

[Laura Arjona Reina]

Package: www.debian.org
User: www.debian@packages.debian.org
Usertag: scripts
Severity: normal

Hi, we received the proposal to add listing of orphaned packages by
popularity in this merge request:

https://salsa.debian.org/webmaster-team/webwml/-/merge_requests/553

I find the idea valuable, but the approach (linking to wnpp.debian.net)
is very different from what we already have in /devel/wnpp section (we
build some lists ourselves with the wnpp.pl script [1], using the data
gathered by the 1ftpfiles script from the cron repo [2].

[1]
https://salsa.debian.org/webmaster-team/webwml/-/blob/master/english/devel/wnpp/wnpp.pl
[2]
https://salsa.debian.org/webmaster-team/cron/-/blob/master/parts/1ftpfiles

Having a look at both the resulting listings that we provide in
www.debian.org/devel/wnpp, and the ones provided in wnpp.debian.net, I
think maybe we could review our old approach and remove most of the
listings we were providing, and link to wnpp.debian.net instead.

This of course would require changes in the wml files in /devel/wnpp
section, the Makefiles, and the scripts in the cron repo.

What do you think?
Kind regards,
-- 
Laura Arjona Reina
https://wiki.debian.org/LauraArjona

Bug#971622: Please update gnome-music to 3.36.5

[Amr Ibrahim]

Package: gnome-music

Please update gnome-music to 3.36.5. It's a bug-fix release.

https://gitlab.gnome.org/GNOME/gnome-music/-/blob/gnome-3-36/NEWS

Overview of changes in 3.36.5
=

Bugs fixed:
 scrobbler: Don't crash if gnome-online-accounts is unavailable (#410)
 Selection mode search doesn't work (#405)
 Selecting an album in albums view in selection mode randomly deselects 
other albums (#406)

 Selection mode only works for artists during search (#407)
 mpris misc fixes (!743)

Bug#968157: src:haskell-cborg: testsuite fails due to bus errors on armhf

[Ilias Tsitsimpis]

Control: severity -1 important

haskell-cborg has been removed from armhf (see #968084). Lowering the
severity to allow it to migrate to testing.

-- 
Ilias

Bug#971621: wmmixer : Unable to open mixer device /dev/mixer'.

[rv]

Package: wmmixer
Version: 1.8-1
Severity: important
X-Debbugs-Cc: riveravaldezm...@gmail.com

Dear Maintainer,

   * What led up to the situation?

$ sudo apt-get install wmmixer 
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias   
Leyendo la información de estado... Hecho
Se instalarán los siguientes paquetes adicionales:
  oss-compat
Paquetes sugeridos:
  osspd wmaker | afterstep
Se instalarán los siguientes paquetes NUEVOS:
  oss-compat wmmixer
0 actualizados, 2 nuevos se instalarán, 0 para eliminar y 15 no actualizados.
Se necesita descargar 32,8 kB de archivos.
Se utilizarán 110 kB de espacio de disco adicional después de esta operación.
¿Desea continuar? [S/n]S

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

$ wmmixer

   * What was the outcome of this action?

wmmixer : Unable to open mixer device /dev/mixer'.

   * What outcome did you expect instead?

wmmixer starting, I suppose.

Thanks a lot. Let me know if I can help with something.
Regards!

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

Kernel: Linux 5.8.0-1-amd64 (SMP w/3 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
LANGUAGE=es_AR:es
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages wmmixer depends on:
ii  libc62.30-8
ii  libgcc-s1 [libgcc1]  10.2.0-7
ii  libstdc++6   10.2.0-7
ii  libx11-6 2:1.6.10-3
ii  libxext6 2:1.3.3-1+b2
ii  libxpm4  1:3.5.12-1
ii  oss-compat   7

wmmixer recommends no packages.

Versions of packages wmmixer suggests:
pn  wmaker | afterstep  

-- no debconf information

Bug#900244: NVM error information log entry count increase not an error

[Günter Frenz]

Hi,

I don't know if this is the same bug as described above: since some time
I get the same message via mail always on system-boot but my error
log seems to be empty:

corinnis:~# smartctl -i -l error /dev/nvme0n1
smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.8.0-2-amd64] (local build)
Copyright (C) 2002-19, Bruce Allen, Christian Franke,
www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:   Samsung SSD 970 EVO 500GB
Serial Number:  S466NX0M112847J
Firmware Version:   2B2QEXE7
PCI Vendor/Subsystem ID:0x144d
IEEE OUI Identifier:0x002538
Total NVM Capacity: 500.107.862.016 [500 GB]
Unallocated NVM Capacity:   0
Controller ID:  4
Number of Namespaces:   1
Namespace 1 Size/Capacity:  500.107.862.016 [500 GB]
Namespace 1 Utilization:174.323.851.264 [174 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64:002538 5191b033dd
Local Time is:  Sat Oct  3 10:37:34 2020 CEST

=== START OF SMART DATA SECTION ===
Error Information (NVMe Log 0x01, max 64 entries)
No Errors Logged

best regards

Günter


-- 
---
Günter Frenz
Börschgasse 16a, D-51143 Köln
(h) gu...@guefz.de, gu...@freenet.de
(w) f...@gso-koeln.de
---




pgpvStth1L55W.pgp
Description: Digitale Signatur von OpenPGP

Bug#971508: xsnow: autopkgtest must be marked superficial

[Paul Gevers]

Hi Willem,

> -- Regards Sudip On Thu, Oct 1, 2020 at 1:16 PM Willem Vermin
>  wrote:
>> I was able to run xsnow in Xvfb, along with fvwm or gnome-shell.
>>
>> Clicking buttons only affect what you see on the screen, there is no
>> specific output caused by button clicks.
>>
>> What I could do, is run xsnow in Xvfb and parse the messages from xsnow
>> at startup and end, and check if they are as expected. Would that suffice?
>>
>> Btw,
>> The current test, based on the output of
>> xsnow -h
>> is trivial, but it does ensure that all needed system libraries are in
>> place.

As the bug report of Sudip clearly states, these tests are valuable, we
do appreciate them. Even when marked superficial, they will block
dependencies that break your package, so that's OK. Why we want packages
to be marked superficial if they only do trivial testing is because we
treat packages with autopkgtests special in the judgement for migration.
Now a bit. During the freeze a lot more. This special treatment is based
on the understanding that significant testing has a reasonable chance to
prevent bugs in the package itself from  migrating to testing.

So, for now it's really the maintainer call. If you believe that you can
test the package in such a way that there's a reasonable chance to catch
(some) bugs, than the autopgktest doesn't need a superficial
restriction. We're not asking for full coverage.

Please, just keep your testing limited to superficial testing if it's
not reasonable to do more, but mark it as such.

Plug (although I don't know how to do it exactly): there's reports that
one can also test GUIs via the accessibility bus. The great advantage of
doing that is that one is also testing for accessibility, which is a
great good IMHO. Maybe there's more to check in the responses from that
bus.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#971618: diaspora: aspects membership list is broken

[Pirate Praveen]

Package: diaspora
Version: 0.7.14.0-7
Severity: grave
Control: forwarded -1 https://github.com/diaspora/diaspora/issues/8158

Attaching screenshot of broken aspect selection list. This is possibly 
caused by newer version of jquery in debian (upstream is still using 
jquery 3.4.1 and we are already on 3.5.1 which dropped support for self 
closing html tags).


Though trying with older versions of jquery from 
rubygems.org/rails-assets.org (jquery-ui-rails, rails-assets-jquery) 
did not fix it. Another possibility is mismatch in backbone.js versions.

Bug#971594: RFS: asciidoc/9.0.2-1 [ITA] -- Highly configurable text format for writing documentation

[Leon Marz]

> I would instead suggest either keeping it as it was before, getting
> nanoc fixed before removing asciidoc-base or making asciidoc-base into
> a transitional package depending on asciidoc.

Ok, no problem. asciidoc-base is now a metapackage, which depends on 
asciidoc.

- Leon

Bug#971617: rakudo: failed upgrade: Missing or wrong version of dependency 'gen/moar/stage2/MASTNodes.nqp'

[Marc Glisse]

Package: rakudo
Version: 2020.09+dfsg-1
Severity: important

Dear Maintainer,

on a computer that was up-to-date with testing yesterday, I ran "apt
upgrade" this morning, which tried updating rakudo/nqp/moarvm, but
failed with

Setting up rakudo (2020.09+dfsg-1) ...
  rakudo-helper.pl: Reinstalling all perl6 modules ...
(1/3) reinstall: perl6-zef
Unhandled exception: Missing or wrong version of dependency 
'gen/moar/stage2/MASTNodes.nqp' (from 'gen/moar/Pod.nqp')
   at :1  
(/usr/lib/perl6/lib/Perl6/Pod.moarvm:)
 from src/vm/moar/ModuleLoader.nqp:47  (/usr/share/nqp/lib/ModuleLoader.moarvm:)
 from src/vm/moar/ModuleLoader.nqp:40  
(/usr/share/nqp/lib/ModuleLoader.moarvm:load_module)
 from :1  
(/usr/lib/perl6/lib/Perl6/Actions.moarvm:)
 from src/vm/moar/ModuleLoader.nqp:47  (/usr/share/nqp/lib/ModuleLoader.moarvm:)
 from src/vm/moar/ModuleLoader.nqp:40  
(/usr/share/nqp/lib/ModuleLoader.moarvm:load_module)
 from :1  
(/usr/lib/perl6/lib/Perl6/Grammar.moarvm:)
 from src/vm/moar/ModuleLoader.nqp:47  (/usr/share/nqp/lib/ModuleLoader.moarvm:)
 from src/vm/moar/ModuleLoader.nqp:40  
(/usr/share/nqp/lib/ModuleLoader.moarvm:load_module)
 from :1  
(/usr/lib/perl6/runtime/perl6.moarvm:)
"perl6 /usr/share/perl6/tools/install-dist.p6 
--from=/usr/share/perl6/debian-sources/perl6-zef --to=/tmp/qzgpwdSHG6/build 
--for=vendor" unexpected
ly returned exit value 1 at /usr/share/perl5/IPC/System/Simple.pm line 578.
IPC::System::Simple::_check_exit("perl6 
/usr/share/perl6/tools/install-dist.p6 --from=/usr/shar"..., 1, 
ARRAY(0x55ccaf960dd0)) called at /
usr/share/perl5/IPC/System/Simple.pm line 550
IPC::System::Simple::_process_child_error(256, "perl6 
/usr/share/perl6/tools/install-dist.p6 --from=/usr/shar"..., 
ARRAY(0x55ccaf960dd0)) 
called at /usr/share/perl5/IPC/System/Simple.pm line 190
IPC::System::Simple::run("perl6 /usr/share/perl6/tools/install-dist.p6 
--from=/usr/shar"...) called at (eval 25) line 12
eval {...} called at (eval 25) line 11
Fatal::__ANON__("perl6 /usr/share/perl6/tools/install-dist.p6 
--from=/usr/shar"...) called at /usr/share/perl6/rakudo-helper.pl line 47
main::install("perl6-zef") called at /usr/share/perl6/rakudo-helper.pl 
line 109
main::reinstall_all() called at /usr/share/perl6/rakudo-helper.pl line 
151
 at /usr/share/perl6/rakudo-helper.pl line 47
dpkg: error processing package rakudo (--configure):
 installed rakudo package post-installation script subprocess returned error 
exit status 1

Running "apt install -f" now gives the same error. I hesitated about
filing this with perl6-zef 0.8.5-2 instead of rakudo...

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

Kernel: Linux 5.8.0-2-amd64 (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 not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages rakudo depends on:
ii  libc6  2.31-3
ii  libgraph-perl  1:0.9704-1
ii  libipc-system-simple-perl  1.30-1
ii  libpath-tiny-perl  0.114-1
ii  moarvm 2020.09+dfsg-1
ii  nqp2020.09+dfsg-2

rakudo recommends no packages.

Versions of packages rakudo suggests:
ii  valgrind  1:3.16.1-1

-- no debconf information

Bug#936268: caldav-tester: Python2 removal in sid/bullseye

[Jonas Smedegaard]

Quoting Petter Reinholdtsen:
> I tried to notify other caldav interested people to see if there was 
> any interest in taking over.

I am surprised by the above remark, and the consequential removal 
request by Moritz Mühlenhoff.

The only notification I am aware of is this¹:
> I am unable to spend much time on maintaining the package, so I hope 
> someone with more spare time can help out.  Upstream is not actively 
> making new releases, but have tagged releases in the past on my 
> request. Their focus is writing a tool to test their own caldav 
> server, and they only fetch HEAD in their own development.  Close 
> contact with upstream will thus help to make it easier to package 
> updated versions in Debian.
>
> I do not plan to drop the package, but as long as it seem to be 
> working, I do not plan to spend much time on it either.  I am not 
> actively using it myself, and thus do not regularly have an itch to 
> scratch.

I failed to read above as a request for adoption at the time, and still 
do.

Please formally orphan or file an RFA to most reliably communicate such 
intent.

I assume that the package is now up for adoption, and will act 
accordingly - hopefully I did not get here too late and the package gets 
kicked out before I can finish my examination.


 - Jonas

¹ 
https://alioth-lists.debian.net/pipermail/calendarserver-discuss/2017-April/68.html

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#971616: sh: pager: command not found

[Harald Dunkel]

Package: dpkg
Version: 1.19.7

I am pretty sure this is not supposed to happen:

# aptitude upgrade
:
Setting up smartmontools (7.1-1~bpo10+1) ...
Installing new version of config file /etc/default/smartmontools ...
Installing new version of config file /etc/init.d/smartmontools ...

Configuration file '/etc/smartd.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** smartd.conf (Y/I/N/O/D/Z) [default=N] ? d
sh: pager: command not found
dpkg: error processing package smartmontools (--configure):
 conffile difference visualizer subprocess returned error exit status 127
:


Regards
Harri

Bug#970903: RM: dms/oldstable -- ROM; removing until have time to revamp it

[Sean Whitton]

Hello,

On Wed 23 Sep 2020 at 10:37am +12, Matthew Grant wrote:

> Could you please remove the package from unstable as I honetly don't have the
> time at the moment to revamp the package for modern Debian.
>
> I am about to take it our ot use probably for myself, as I am focusing on 
> Samba
> server development and IPv6 for my current employer.
>
> Some time in the future when I have spare time I may start work on this 
> project
> again, but I am officially putting it on hold for now.

I'm removing because it's RC-buggy; otherwise, I think orphaning the
package would have been more appropriate.

-- 
Sean Whitton

Bug#971615: golang-github-russellhaering-goxmldsig: CVE-2020-15216

[Salvatore Bonaccorso]

Source: golang-github-russellhaering-goxmldsig
Version: 0.0~git20180430.7acd5e4-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for 
golang-github-russellhaering-goxmldsig.

CVE-2020-15216[0]:
| In goxmldsig (XML Digital Signatures implemented in pure Go) before
| version 1.1.0, with a carefully crafted XML file, an attacker can
| completely bypass signature validation and pass off an altered file as
| a signed one. A patch is available, all users of goxmldsig should
| upgrade to at least revision f6188febf0c29d7ffe26a0436212b19cb9615e64
| or version 1.1.0


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2020-15216
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15216
[1] 
https://github.com/russellhaering/goxmldsig/security/advisories/GHSA-q547-gmf8-8jr7
[2] 
https://github.com/russellhaering/goxmldsig/commit/f6188febf0c29d7ffe26a0436212b19cb9615e64

Regards,
Salvatore

Bug#968345: RM: golang-github-mendersoftware-scopestack-dev -- ROM; deprecated and unused

[Sean Whitton]

control: tag -1 - moreinfo

On Sat 22 Aug 2020 at 08:27am -07, Sean Whitton wrote:

> On Thu 13 Aug 2020 at 01:08PM +02, lluis.cam...@northern.tech wrote:
>
>> This dependency is also deprecated after removing
>> golang-github-mendersoftware-log (see #960398)
>>
>> Unused both in testing and unstable, so please remove:
>>
>> golang-github-mendersoftware-scopestack-dev
>
> Could the maintainer confirm this, please?

Done in #968343.

-- 
Sean Whitton

Bug#971614: /usr/bin/nextcloud: General protection fault with libQT5Core after resuming when hibernate

[alain]

Package: nextcloud-desktop
Version: 2.5.1-3+deb10u1
Severity: important
File: /usr/bin/nextcloud

Dear Maintainer,

I resumed my system after hibernate.
Nextcloud seemed to do not work (no activities with the newtwork) but the icon 
was green in the Xfce4 panel.
Il can display the UI. When I wanted to see the activity of an account,
after a while, it crasched.

Log after crashing : 
kernel: [ 9155.629572] traps: nextcloud[1219] general protection fault 
ip:7fe3a06e4ba7 sp:7ffd47ecb948 error:0 in 
libQt5Core.so.5.11.3[7fe3a06ae000+2a4000]

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

Kernel: Linux 5.8.0-0.bpo.2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_UNSIGNED_MODULE
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 nextcloud-desktop depends on:
ii  libc6 2.28-10
ii  libgcc1   1:8.3.0-6
ii  libnextcloudsync0 2.5.1-3+deb10u1
ii  libqt5concurrent5 5.11.3+dfsg1-1+deb10u4
ii  libqt5core5a  5.11.3+dfsg1-1+deb10u4
ii  libqt5dbus5   5.11.3+dfsg1-1+deb10u4
ii  libqt5gui55.11.3+dfsg1-1+deb10u4
ii  libqt5keychain1   0.9.1-2
ii  libqt5network55.11.3+dfsg1-1+deb10u4
ii  libqt5positioning55.11.3+dfsg-2
ii  libqt5printsupport5   5.11.3+dfsg1-1+deb10u4
ii  libqt5qml55.11.3-4
ii  libqt5quick5  5.11.3-4
ii  libqt5sql5-sqlite 5.11.3+dfsg1-1+deb10u4
ii  libqt5webchannel5 5.11.3-2
ii  libqt5webenginecore5  5.11.3+dfsg-2+deb10u1
ii  libqt5webenginewidgets5   5.11.3+dfsg-2+deb10u1
ii  libqt5webkit5 5.212.0~alpha2-21
ii  libqt5widgets55.11.3+dfsg1-1+deb10u4
ii  libqt5xml55.11.3+dfsg1-1+deb10u4
ii  libsqlite3-0  3.27.2-3
ii  libssl1.1 1.1.1d-0+deb10u3
ii  libstdc++68.3.0-6
ii  nextcloud-desktop-common  2.5.1-3+deb10u1
ii  nextcloud-desktop-l10n2.5.1-3+deb10u1
ii  zlib1g1:1.2.11.dfsg-1

Versions of packages nextcloud-desktop recommends:
ii  nextcloud-desktop-doc  2.5.1-3+deb10u1

nextcloud-desktop suggests no packages.

-- no debconf information

Bug#970460: [Bug libc/23960] [2.28 Regression]: New getdents{64} implementation breaks qemu-user

[John Paul Adrian Glaubitz]

Hi!

On 10/3/20 1:12 AM, Thorsten Glaser wrote:
> could you work around the problem by starting an i386 VM on
> your amd64 system, and then running the qemu-user buildds on
> that? The return values from the syscalls will natively be
> correct 32 bit there…

We already tried that if I remember, this doesn't help and the issue
remains. Apparently i386 is special in this regard by using 64-bit
extended values [1].

Adrian

> [1] https://bugzilla.kernel.org/show_bug.cgi?id=205957

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#969490: RM: caldav-tester -- RoQA; Depends on Python 2, dead upstream

[Jonas Smedegaard]

Please wait a bit - I would like to try revive this package.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#969672: gnutls28: please upgrade to guile-3.0 soon, if feasible

[Rob Browning]

Andreas Metzler  writes:

> I would love to, but guile-3.0 >= 3.0.4-1+b1 seems to be broken. See
> 969640.

Assuming I did it right (guile-3.0-dev was installed along with all
the other build deps, and guile-2.2-dev wasn't), a "fakeroot
debian/rules binary" just built without trouble here using the current
3.6.15-4 package.

I wonder if the problem has been resolved, or maybe it's intermittent,
arch dependent, or something else.  And was the failure local, or on the
buildds?

I can double-check in a sid sbuild chroot later.  (When it succeeded, I
was just using the system I had handy, which is somewhere between
bullseye and sid (x86_64).)

-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#963924: libdc1394-22 -- RoQA; Superseeded by libdc1394

[Sean Whitton]

control: tag -1 + moreinfo

Hello,

On Thu 24 Sep 2020 at 08:28am +02, Gianfranco Costamagna wrote:

> looks like the new libdc1394 took over the libdc1394-22-dev as transitional 
> packages, and rebuilds have been performed
> for reverse-dependencies to move to the new version.
>
> Can you please just remove the old one from the archive?

Hmm, are you sure everything is up to date?

Checking reverse dependencies...
# Broken Depends:
opencv: libopencv-videoio3.2
libopencv-videoio4.1

Dependency problem found.

-- 
Sean Whitton

Bug#960761: RM:node-babel-preset-react -- ROM; obsolete, no reverse dependencies

[Sean Whitton]

control: tag -1 + moreinfo

Hello,

On Sat 16 May 2020 at 05:23pm +0530, Pirate Praveen wrote:

> Package: ftp.debian.org
> Severity: normal
> Control: block -1 by 960433
>
> As part of removing babel version 6 (replaced by babel 7)[1] from the
> archive, please remove this package. Its only reverse dependency
> (node-babel-preset-airbnb) is also marked for removal.

Looks like this is a binary package, not a source package?  Typically
you'd upload a version of the source package which does not build it and
then it'd be removed (automatically or manually).

-- 
Sean Whitton

Bug#971609: r-cran-sna: Not build in Debian, unsatisfiable build-deps

[Andreas Tille]

Control: block -1 by 951510
Control: block -1 by 951511

On Fri, Oct 02, 2020 at 03:13:33PM -0700, Steve Langasek wrote:
> So it would be good if those would get uploaded to the archive, given there
> is another package that build-depends on them.
The question

   "Shall we re-submit, or is that not enough?"

in [1] was never answered and so nothing happened from our side.  I have
just re-uploaded - lets see what might happen.

Kind regards

  Andreas.

[1] 
https://alioth-lists.debian.net/pipermail/r-pkg-team/2020-February/010262.html

-- 
http://fam-tille.de

Bug#969975: RM: openjfx tuxguitar libjogl2-java [armel armhf i386 mipsel] -- RoQA; NBS

[Sean Whitton]

On Wed 09 Sep 2020 at 05:53pm +02, Gianfranco Costamagna wrote:

> Package: ftp.debian.org
> Severity: normal
>
> Hello, ftpmasters,
>
> as explained in #962915, the removal of libswt-gtk-4-java on 32bit (armel 
> armhf i386 mipsel), made some packages unbuildable there.
>
> I think we should remove them too, since 32bit are not supported anymore.
>
> the list of libswt-gtk-4-java reverse-dependencies is:
> - openjfx
> - libjogl2-java
> - tuxguitar
>
> please remove them, as well as their dependencies.
> (I would like to provide a full list, but my dak rm is not that good)

Could we have separate RM bugs please?  Our scripts assume that so this
is currently much more effortful to process.

-- 
Sean Whitton