Processed: forcibly merging 977876 973506

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 977876 973506
Bug #977876 {Done: Matthias Klumpp } [packagekit] 
packagekit-offline-update.service not enabled, not offline updates applied
Bug #973506 [packagekit] packagekit: offline system update don't work after 
upgrading from 1.1.13-2+b1 to 1.2.1-1
Severity set to 'serious' from 'important'
Marked Bug as done
The source packagekit and version 1.2.2-2 do not appear to match any binary 
packages
Marked as fixed in versions packagekit/1.2.2-2.
Merged 973506 977876
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
973506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973506
977876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#977901: chromium: Inconsistent SEGV

[Boyd Stephen Smith Jr.]

On Tuesday, December 22, 2020 10:47:31 PM CST Boyd Stephen Smith Jr. wrote:
> All my extensions were pulled down during the Google Sync and ran fine on 87
> for roughly an hour -- that's twice as long as my longest browser session
> for version 87 on the old profile.
> 
> I still convinced this is a bug -- nothing in my profile should cause a
> SEGV, ref_count violation, or corrupted double-linked list.  But, there's
> at least a workaround, that I'm going to take advantage of, to create a
> new, blank profile and either sync or manually import (or likely a
> combination of both) all your settings into the new profile.

So, it seems one of the _settings_ of one of my extensions is causing the 
problem.  Restored my _settings_ (same list of extensions), and got a crash in 
10 minutes.

*That* is annoying, but not a chromium bug.  Feel free to close this at your 
leisure.

I'll have to play around with disabling extensions to see which one(s) cause a 
crash within 30 minutes.  Super annoying since I do use every one of them 
literally every day. :(
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net   ((_/)o o(\_))
Twitter: @DaTwinkDaddy   `-'(. .)`-'
http://iguanasuicide.net/\_/


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

Bug#977901: chromium: Inconsistent SEGV

[Boyd Stephen Smith Jr.]

On Tuesday, December 22, 2020 5:26:04 PM CST Boyd Stephen Smith Jr. wrote:
> On Tue, 22 Dec 2020 23:43:23 +0100 Michel Le Bihan  
wrote:
> > I was not able to reproduce those crashes.
> 
> That's unfortunate.  I'm up to 50 just today.  I'm probably going to have to
> downgrade to 83 at least until there's another update.

Downgrading was a mixed bag (browser was stable, but audio/video stopped 
working (!)) .  So, I tried again with 87.

Rather than just disabling my extensions, I tried from a brand-new profile and 
an empty cache.  So far, I'm not able to reproduce the crashing on the new 
profile.

Unfortunately, I have about a half-dozen extensions that have at least some 
configuration that isn't synchronized anywhere else, so I need to go back to 
83 and the old profile, dump/export/backup all their settings to a file (or 
take notes), then go back to 87 and the new profile and restore/import/apply 
all those settings in the new profile.

All my extensions were pulled down during the Google Sync and ran fine on 87 
for roughly an hour -- that's twice as long as my longest browser session for 
version 87 on the old profile.

I still convinced this is a bug -- nothing in my profile should cause a SEGV, 
ref_count violation, or corrupted double-linked list.  But, there's at least a 
workaround, that I'm going to take advantage of, to create a new, blank 
profile and either sync or manually import (or likely a combination of both) 
all your settings into the new profile.

It's not going to be a kind experience for people upgrading from buster to 
bullseye, especially since the crashes make it hard to export settings from 
your old profile.
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net   ((_/)o o(\_))
Twitter: @DaTwinkDaddy   `-'(. .)`-'
http://iguanasuicide.net/\_/


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

Bug#957037: biboumi: ftbfs with GCC-10

[Vasudev Kamath]

Michel Le Bihan  writes:

> Le mardi 22 décembre 2020 à 17:35 +0530, Vasudev Kamath a écrit :
>> Jonas Smedegaard  writes:
>> 
>> > Quoting Michel Le Bihan (2020-12-20 17:15:29)
>> > > Le dimanche 20 décembre 2020 à 16:50 +0100, Jonas Smedegaard a
>> > > écrit :
>> > > > Quoting Michel Le Bihan (2020-12-20 16:06:27)
>> > > > > A quick summary of the differences between both repos:
>> > > > 
>> > > > Thanks, that is no doubt helpful!
>> > > > 
>> > > > [ beware: commenting without actually having looked at the
>> > > > code! ]
>> > > Please look at it when you will have time.
>> > 
>> > Most likely no: Instead, please wait for Vasudev to look at it.
>> 
>> I was looking at biboumi repository and did not see any merge
>> requests
>> on it. Jonas do we need to enable something in repo to allow merge
>> requests?.
>> 
> Yes. You need to enable merge requests in the repository settings. They
> are currently disabled.

Done, it took me a while to navigate around the settings. Please raise
MR so I can review.

Cheers,
Vasudev

Bug#976731: marked as done (firefox: FTBFS on arm64 (explicit specialization in non-namespace scope ‘class js::wasm::BaseRegAlloc’))

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2020 12:34:27 +0900
with message-id <20201223033427.gpy6we6mysc2v...@glandium.org>
and subject line Re: Bug#976731: firefox: FTBFS on arm64 (explicit 
specialization in non-namespace scope ‘class js::wasm::BaseRegAlloc’)
has caused the Debian Bug report #976731,
regarding firefox: FTBFS on arm64 (explicit specialization in non-namespace 
scope ‘class js::wasm::BaseRegAlloc’)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
976731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firefox
Version: 83.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Log: 
https://buildd.debian.org/status/fetch.php?pkg=firefox=arm64=83.0-1=1606251110=0

Excerpt:
> In file included from Unified_cpp_js_src_wasm0.cpp:20:
> /<>/js/src/wasm/WasmBaselineCompile.cpp:661:13: error: explicit 
> specialization in non-namespace scope ‘class js::wasm::BaseRegAlloc’
>   661 |   template <>
>   | ^
> /<>/js/src/wasm/WasmBaselineCompile.cpp:662:8: error: 
> template-id ‘hasFPU’ in declaration of primary 
> template
>   662 |   bool hasFPU() {
>   |^~~~
> /<>/js/src/wasm/WasmBaselineCompile.cpp:747:17: error: too many 
> template-parameter-lists
>   747 |   FloatRegister allocFPU() {
>   | ^~~~
> /<>/js/src/wasm/WasmBaselineCompile.cpp:752:13: error: explicit 
> specialization in non-namespace scope ‘class js::wasm::BaseRegAlloc’
>   752 |   template <>
>   | ^
> /<>/js/src/wasm/WasmBaselineCompile.cpp:753:17: error: expected 
> ‘;’ at end of member declaration
>   753 |   FloatRegister allocFPU() {
>   | ^~~~
>   | ;
> /<>/js/src/wasm/WasmBaselineCompile.cpp:753:17: error: 
> ‘js::jit::FloatRegister js::wasm::BaseRegAlloc::allocFPU’ conflicts with a 
> previous declaration
> /<>/js/src/wasm/WasmBaselineCompile.cpp:738:8: note: previous 
> declaration ‘void js::wasm::BaseRegAlloc::allocFPU(js::jit::FloatRegister)’
>   738 |   void allocFPU(FloatRegister r) {
>   |^~~~
> /<>/js/src/wasm/WasmBaselineCompile.cpp:753:25: error: expected 
> unqualified-id before ‘<’ token
>   753 |   FloatRegister allocFPU() {
>   | ^
> /<>/js/src/wasm/WasmBaselineCompile.cpp: In member function 
> ‘js::wasm::RegF32 js::wasm::BaseRegAlloc::needF32()’:
> /<>/js/src/wasm/WasmBaselineCompile.cpp:937:27: error: invalid 
> use of non-static member function ‘void 
> js::wasm::BaseRegAlloc::allocFPU(js::jit::FloatRegister)’
>   937 | return RegF32(allocFPU());
>   |   ^
> /<>/js/src/wasm/WasmBaselineCompile.cpp:738:8: note: declared 
> here
>   738 |   void allocFPU(FloatRegister r) {
>   |^~~~
> /<>/js/src/wasm/WasmBaselineCompile.cpp:937:18: error: expected 
> primary-expression before ‘(’ token
>   937 | return RegF32(allocFPU());
>   |  ^
> /<>/js/src/wasm/WasmBaselineCompile.cpp:937:27: error: invalid 
> use of non-static member function ‘void 
> js::wasm::BaseRegAlloc::allocFPU(js::jit::FloatRegister)’
>   937 | return RegF32(allocFPU());
>   |   ^
> /<>/js/src/wasm/WasmBaselineCompile.cpp:738:8: note: declared 
> here
>   738 |   void allocFPU(FloatRegister r) {
>   |^~~~
> /<>/js/src/wasm/WasmBaselineCompile.cpp:937:46: error: expected 
> primary-expression before ‘)’ token
>   937 | return RegF32(allocFPU());
>   |  ^
> /<>/js/src/wasm/WasmBaselineCompile.cpp: In member function 
> ‘js::wasm::RegF64 js::wasm::BaseRegAlloc::needF64()’:
> /<>/js/src/wasm/WasmBaselineCompile.cpp:951:27: error: invalid 
> use of non-static member function ‘void 
> js::wasm::BaseRegAlloc::allocFPU(js::jit::FloatRegister)’
>   951 | return RegF64(allocFPU());
>   |   ^~~~
> /<>/js/src/wasm/WasmBaselineCompile.cpp:738:8: note: declared 
> here
>   738 |   void allocFPU(FloatRegister r) {
>   |^~~~
> /<>/js/src/wasm/WasmBaselineCompile.cpp:951:18: error: expected 
> primary-expression before ‘(’ token
>   951 | return RegF64(allocFPU());
>   |  ^
> /<>/js/src/wasm/WasmBaselineCompile.cpp:951:27: error: invalid 
> use of non-static member function ‘void 
> js::wasm::BaseRegAlloc::allocFPU(js::jit::FloatRegister)’
>   951 | return 

Bug#975455: devtodo: failing autopkgtests with grep 3.6

[Carlos Henrique Lima Melara]

Hi, Adrian.

On Sun, Dec 20, 2020 at 06:35:57PM +0200, Adrian Bunk wrote:
> On Sun, Nov 22, 2020 at 03:20:04PM -0300, Carlos Henrique Lima Melara wrote:
> >...
> > Thanks to let me know. I did see this problem yesterday but didn't have
> > time to fix.
> > 
> > I'll be fixing it today and hopefully will be in unstable this week.
> 
> If there's anything where I could help, please let me know.

I've fixed the bug and talked to a DD that usually sponsor my packages,
but he is busy this month, so he didn't have the chance to look at the
new release yet.

I'd like to know if it would be possible for you to sponsor the new
release of devtodo which is in the debian mentors repo. I've asked
my sponsor and he said it would be nice because he is overwhelmed
lately.

Anyway, thanks for taking the time to look at this bug.

Cheers,
Carlos Melara (Charles)

Bug#977901: chromium: Inconsistent SEGV

[David Purton]

I can confirm that this bug is affecting me since upgrading to
87.0.4280.88-0.2 in Testing today.

David

-- 
David Purton  
:email: dcpur...@marshwiggle.net  
:phone: 0413 626 862

Bug#973677: libkscreenlocker5: No login dialog is shown, user cannot unlock session

[Norbert Preining]

tags 973677 + unreproducible moreinfo
severity 973677 normal
thanks

On Tue, 03 Nov 2020, Mikko Korhonen wrote:
> but happens every time and at any unlock, not just on dehibernation and with 
> a 
> single monitor: only the cursor is shown on a black screen and there is no 
> way to login.
> As a workaround killing the process helps as the new instance shows the login 
> screen.

It seems from other reports that this stems from a mix of versions (5.17
and 5.19 or even 5.20).

I cannot reproduce this on a current up to date unstable system with
plasma 5.20.4 completely updated.

Can you please reconfirm whether this is still an issue with current
Plasma from unstable.

Thanks

Norbert

--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 977927 grave
Bug #977927 [mitmproxy] DistributionNotFound: 'hyperframe>=6.0' due to missing 
dependencies
Severity set to 'grave' from 'important'
> merge 977926 977927
Bug #977926 [mitmproxy] Missing required dependencies
Bug #977927 [mitmproxy] DistributionNotFound: 'hyperframe>=6.0' due to missing 
dependencies
Merged 977926 977927
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
977926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977926
977927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> merge 977926 977927
Bug #977926 [mitmproxy] Missing required dependencies
Unable to merge bugs because:
severity of #977927 is 'important' not 'grave'
Failed to merge 977926: Did not alter merged bugs.

>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
977926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977926
977927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#977926: Missing required dependencies

[Faidon Liambotis]

Package: mitmproxy
Version: 5.3.0-1
Severity: grave

Installing mitmproxy in a clean sid chroot, and running it (with no arguments)
results into a large backtrace that ends with...
  pkg_resources.DistributionNotFound: The 'hyperframe>=6.0' distribution was 
not found and is required by mitmproxy

After installing the package python3-hyperframe, the error becomes:
  pkg_resources.DistributionNotFound: The 'h2>=4.0' distribution was not found 
and is required by mitmproxy
...in turn fixed by installing the package python3-h2.

It looks like at least those two dependencies are missing, preventing
the package from working out of the box in any configuration. Both of
these were in the Depends for the 4.0.4-5 version (buster's).

I did not check whether other features require more dependencies, as I'm
not too familiar with all of mitmproxy's operation modes.

Regards,
Faidon

Bug#977901: chromium: Inconsistent SEGV

[Boyd Stephen Smith Jr.]

On Tue, 22 Dec 2020 23:43:23 +0100 Michel Le Bihan  wrote:
> Installing `chromium-dbgsym` should be enough. Please run Chromium with
> the `--debug` flag like: `chromium --debug`.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963711#10

Chromium crashes on startup if I use the "-g" or "--debug" options.  After I 
issue a "run" at the "(gdb)" prompt, there's some time (a few seconds), but I 
never get a GUI window and then it crashes.  I do get a usable back trace for 
the crash on startup, which I added to that bug.

> I was not able to reproduce those crashes.

That's unfortunate.  I'm up to 50 just today.  I'm probably going to have to 
downgrade to 83 at least until there's another update.
-- 
Boyd Stephen Smith Jr.   ,= ,-_-. =.
b...@iguanasuicide.net   ((_/)o o(\_))
Twitter: @DaTwinkDaddy   `-'(. .)`-'
http://iguanasuicide.net/\_/


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

Bug#943462: [polkit-kde-agent-1] Fails to start with elogind

[Norbert Preining]

Hi Alex,

On Fri, 25 Oct 2019, Alex Volkov wrote:
> Version: 4:5.14.5-1
> Severity: serious

This is for a very old version of Plasma. Could you please try the
current 5.20.4 from unstable.

We can surely not debug this for stable.

Thanks

Norbert

--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#942078: [high quality bug] baloo crash, can't recover; forced reindex does not fix; unusable via dolphin C-f

[Norbert Preining]

Hi Nicholas,

On Wed, 09 Oct 2019, Nicholas D Steeves wrote:
> Version: 5.54.0-1
> Severity: serious
> Justification: poor experience will cause user to give up on baloo; worse 
> than GNOME

Can you reproduce this with current frameworks 5.77 in unstable?

Does it always crash at the same file (jack_capture_90.mp3) or always in
different files?

Thanks

Norbert

--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#972070: marked as done (bluez-obexd: Failure to browse files, Failed to execute program org.bluez.obex: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 23:00:11 +
with message-id 
and subject line Bug#972070: fixed in bluez 5.55-2
has caused the Debian Bug report #972070,
regarding bluez-obexd: Failure to browse files, Failed to execute program 
org.bluez.obex: No such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
972070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972070
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bluez-obexd
Version: 5.55-1
Severity: grave
X-Debbugs-Cc: borissh1983+b...@gmail.com

Dear Maintainer,

After upgrading to 5.55-1 (from 5.50), I no longer able to browse files on 
connected bluetooth device.

I had tried to browse files via plasma's bluetooth deamon (bluedevil?) and was 
greted with a message that obexd service is not running.

I had expected that I would be able to browse files over bluetooth (as it was 
before in 5.50).

logs indicate that the obex service is no longer running and can not be started.

In ~/.xsession-errors I had found : 

kdeinit5: Got EXEC_NEW '/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_obexftp.so' 
from launcher.
kdeinit5: preparing to launch 
'/usr/lib/x86_64-linux-gnu/qt5/plugins/kio_obexftp.so'
bluedevil.kio_obexftp: Create session error "" ""
bluedevil.kio_obexftp: Create session error "" ""
kf5.kio.widgets: KRun(0x55cb874b1150) ERROR 163 "Obexd service is not running."

I had found in syslog the next messages (after attempting to send files, which 
also no longer work):

Activating service name='org.bluez.obex' requested by ':1.45' (uid=1000 
pid=3034 comm="/usr/bin/bluedevil-sendfile -u /org/bluez/hci0/dev")
Activated service 'org.bluez.obex' failed: Failed to execute program 
org.bluez.obex: No such file or directory

I had also found the next messages in ~/.xsession-errors when trying to send : 

bluedevil.sendfile: Device "/org/bluez/hci0/dev_AA_BB_CC_DD_EE_FF"
bluedevil.sendfile: Files ()
org.kde.bluez: PendingCall Error: "Failed to execute program org.bluez.obex: No 
such file or directory"

Manual attempt to call send file (/usr/bin/bluedevil-sendfile -u 
/org/bluez/hci0/dev) result in : 

bluedevil.sendfile: Device "/org/bluez/hci0/dev"
bluedevil.sendfile: Files ()
org.kde.bluez: PendingCall Error: "Failed to execute program org.bluez.obex: No 
such file or directory"
bluedevil.sendfile: Manager initialized
bluedevil.sendfile: Error creating session "ObexManager not operational!"

Attempt to start the service obex resultes in an error : 

systemctl start --user obex
Failed to start obex.service: Unit dbus.socket not found.

sudo systemctl start obex
Failed to start obex.service: Unit obex.service not found.

dbus status : 

sudo systemctl status dbus
  dbus.service - D-Bus System Message Bus
 Loaded: loaded (/lib/systemd/system/dbus.service; static)
 Active: active (running)
TriggeredBy: dbus.socket
   Docs: man:dbus-daemon(1)
   Main PID: 847 (dbus-daemon)
  Tasks: 1 (limit: 18752)
 Memory: 7.1M
 CGroup: /system.slice/dbus.service
 └─847 /usr/bin/dbus-daemon --system --address=systemd: --nofork 
--nopidfile --systemd-activation --syslog-only

dbus-daemon[847]: [system] Activating via systemd: service 
name='org.freedesktop.UPower' unit='upower.service' requested by ':1.28' 
(uid=111 pid=1464 comm="/usr/bin/sddm-greeter --socket /tmp/sddm-:0-mWqkXh")
dbus-daemon[847]: [system] Successfully activated service 
'org.freedesktop.UPower'
dbus-daemon[847]: [system] Activating via systemd: service 
name='org.freedesktop.PackageKit' unit='packagekit.service' requested by 
':1.54' (uid=1000 pid=2053 
comm="/usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier")
dbus-daemon[847]: [system] Successfully activated service 
'org.freedesktop.PackageKit'
dbus-daemon[847]: [system] Activating service 
name='org.kde.powerdevil.discretegpuhelper' requested by ':1.53' (uid=1000 
pid=2074 comm="/usr/lib/x86_64-linux-gnu/libexec/org_kde_powerdev") (using 
servicehelper)
dbus-daemon[847]: [system] Successfully activated service 
'org.kde.powerdevil.discretegpuhelper'
dbus-daemon[847]: [system] Activating via systemd: service 
name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 
pid=848 comm="/usr/sbin/NetworkManager --no-daemon ")
dbus-daemon[847]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
dbus-daemon[847]: [system] Activating via systemd: service 
name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' 
requested by ':1.9' (uid=0 pid=848 comm="/usr/sbin/NetworkManager 

Bug#976887: marked as done (texlive-base: Should not migrate to testing for now.)

[Debian Bug Tracking System]

Your message dated Wed, 23 Dec 2020 07:54:19 +0900
with message-id 
and subject line Re: Bug#976887: texlive-base: Should not migrate to testing 
for now.
has caused the Debian Bug report #976887,
regarding texlive-base: Should not migrate to testing for now.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
976887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-base
Version: 2020.20201203-2
Severity: serious

Dear Maintainer,

The new texlive-base has an impact on docbook based documentations,
see

https://bugs.debian.org/976475
https://bugs.debian.org/976508
https://bugs.debian.org/976519
https://bugs.debian.org/976535
https://bugs.debian.org/976538
https://bugs.debian.org/976544
https://bugs.debian.org/976547
https://bugs.debian.org/976554
https://bugs.debian.org/976556
https://bugs.debian.org/976574
https://bugs.debian.org/976586

Prevent it from migration to testing for now until the issue is sorted
out.

Hilmar
-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource.

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

lrwxrwxrwx 1 root root 31 Dec  4 20:07 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Dec  2 00:27 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Dec  4 20:07 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Dec  4 20:07 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 3342 Dec  7 08:36 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Nov 10  2008 mktex.cnf
-rw-r--r-- 1 root root 475 Dec  2 00:27 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

Kernel: Linux 5.9.0-4-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 texlive-base depends on:
ii  debconf [debconf-2.0]  1.5.74
ii  libpaper-utils 1.1.28+b1
ii  sensible-utils 0.0.12+nmu1
ii  tex-common 6.15
ii  texlive-binaries   2020.20200327.54578-5
ii  ucf3.0043
ii  xdg-utils  1.1.3-2

Versions of packages texlive-base recommends:
pn  lmodern  

Versions of packages texlive-base suggests:
ii  ghostscript [postscript-viewer]  9.53.3~dfsg-5
ii  gv [postscript-viewer]   1:3.7.4-2
ii  perl-tk  

Bug#977901: chromium: Inconsistent SEGV

[Michel Le Bihan]

Hello,

Installing `chromium-dbgsym` should be enough. Please run Chromium with
the `--debug` flag like: `chromium --debug`. You can mix it with your
other flags like `chromium --debug --incognito`. In the GDB shell,
please enter `run`. Chromium should start then. You can then use
Chromium, but it will be very slow. Once a crash occurs, please enter
`bt` in the shell and attach the backtrace to this bug.

I was not able to reproduce those crashes.

Michel Le Bihan

Bug#977918: vm: Package vm prevents clean emacs27 start

[Dirk Eddelbuettel]

Package: vm
Version: 8.2.0b-6
Severity: serious

Using the (awesome !!) newer emacs 27.1, I am having issues with package
vm. One issue is that on startup, a message 'Package cl is deprecated' is
shown.  Startup appears to finish in interactive, but does not in daemon 
mode
which is how I used to use emacs. So the message prevents daemon mode from
working.

Moreover, some googling reveals that 'cl' is indeed deprecated and vm 
ideally
should move on from it.  An upgrade would be great, but it is not clear how
active upstream still is.

A fix / update to vm would be awesome. It's been my goto mail client since
forever.

And of course in a minimal container with just emacs27 and vm the issue does
not reproduce. While I have a lot of general programming stuff in .emacs,
there is not that much relative to vm so I am a little ... stumped.

Dirk

-- 
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#977921: boost1.74: context asm files not built on mipsel

[Adrian Bunk]

Source: boost1.74
Version: 1.74.0-3
Severity: serious
Tags: ftbfs
Control: affects -1 src:nix libboost-coroutine1.74.0 libboost-fiber1.74.0

https://buildd.debian.org/status/fetch.php?pkg=nix=mipsel=2.3.7%2Bdfsg1-1%2Bb1=1608526707=0

...
/usr/bin/ld: src/libutil/serialise.o: in function 
`boost::context::fiber::resume() &&':
/usr/include/boost/context/fiber_fcontext.hpp:288: undefined reference to 
`jump_fcontext'
...


The root cause is:

https://buildd.debian.org/status/fetch.php?pkg=boost1.74=mipsel=1.74.0-3%2Bb1=1607629749=0

...
dpkg-shlibdeps: warning: symbol make_fcontext used by 
debian/libboost-fiber1.74.0/usr/lib/mipsel-linux-gnu/libboost_fiber.so.1.74.0 
found in none of the libraries
dpkg-shlibdeps: warning: symbol jump_fcontext used by 
debian/libboost-fiber1.74.0/usr/lib/mipsel-linux-gnu/libboost_fiber.so.1.74.0 
found in none of the libraries
dpkg-shlibdeps: warning: symbol ontop_fcontext used by 
debian/libboost-fiber1.74.0/usr/lib/mipsel-linux-gnu/libboost_fiber.so.1.74.0 
found in none of the libraries
...
dpkg-shlibdeps: warning: symbol jump_fcontext used by 
debian/libboost-coroutine1.74.0/usr/lib/mipsel-linux-gnu/libboost_coroutine.so.1.74.0
 found in none of the libraries
dpkg-shlibdeps: warning: symbol make_fcontext used by 
debian/libboost-coroutine1.74.0/usr/lib/mipsel-linux-gnu/libboost_coroutine.so.1.74.0
 found in none of the libraries
...


libs/context/src/asm/*_mips32_o32_elf_gas.S were built for mipsel
in 1.71, but are no longer included in 1.74.

Processed: boost1.74: context asm files not built on mipsel

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:nix libboost-coroutine1.74.0 libboost-fiber1.74.0
Bug #977921 [src:boost1.74] boost1.74: context asm files not built on mipsel
Added indication that 977921 affects src:nix, libboost-coroutine1.74.0, and 
libboost-fiber1.74.0

-- 
977921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#977920: python3-distutils and python3-lib2to3 depend on unavailable version of python3:any

[Aurelien Jarno]

Source: python3-stdlib-extensions
Version: 3.9.1-1
Severity: serious

| # apt-get install python3-distutils
| Reading package lists... Done
| Building dependency tree   
| Reading state information... Done
| Some packages could not be installed. This may mean that you have
| requested an impossible situation or if you are using the unstable
| distribution that some required packages have not yet been created
| or been moved out of Incoming.
| The following information may help to resolve the situation:
| 
| The following packages have unmet dependencies:
|  python3-distutils : Depends: python3:any (>= 3.9.1-0~)
|  Depends: python3-lib2to3 (= 3.9.1-1) but it is not going 
to be installed
| E: Unable to correct problems, you have held broken packages.

python3:any is still at version 3.9.0-4.

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 977901 grave
Bug #977901 [chromium] chromium: Inconsistent SEGV
Severity set to 'grave' from 'normal'
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
977901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#977502: marked as done (podman,golang-github-containers-common: both ship /usr/share/man/man5/containers-mounts.conf.5.gz)

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 22:03:56 +
with message-id 
and subject line Bug#977502: fixed in libpod 2.1.1+dfsg1-3
has caused the Debian Bug report #977502,
regarding podman,golang-github-containers-common: both ship 
/usr/share/man/man5/containers-mounts.conf.5.gz
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: podman,golang-github-containers-common
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 2.1.1+dfsg1-2
Control: found -1 0.28.1+ds1-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Preparing to unpack .../golang-github-containers-common_0.28.1+ds1-1_all.deb 
...
  Unpacking golang-github-containers-common (0.28.1+ds1-1) over (0.26.3+ds1-2) 
...
  dpkg: error processing archive 
/var/cache/apt/archives/golang-github-containers-common_0.28.1+ds1-1_all.deb 
(--unpack):
   trying to overwrite '/usr/share/man/man5/containers-mounts.conf.5.gz', which 
is also in package podman 2.1.1+dfsg1-2
  Errors were encountered while processing:
   /var/cache/apt/archives/golang-github-containers-common_0.28.1+ds1-1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  usr/share/man/man5/containers-mounts.conf.5.gz

This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


podman=2.1.1+dfsg1-2_golang-github-containers-common=0.28.1+ds1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libpod
Source-Version: 2.1.1+dfsg1-3
Done: Reinhard Tartler 

We believe that the bug you reported is fixed in the latest version of
libpod, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated libpod package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 22 Dec 2020 13:00:57 -0500
Source: libpod
Architecture: source
Version: 2.1.1+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Reinhard Tartler 
Closes: 977502 977717
Changes:
 libpod (2.1.1+dfsg1-3) unstable; urgency=medium
 .
   [ Dmitry Smirnov ]
   * Tightened versioned dependency on "containernetworking-plugins".
 .
   [ Reinhard Tartler ]
   * debian/copyright: various cleanups
   * Fix handling of Ambient/Inheritable caps for non root user, Closes: #977717
   * Rely on upstream's build scripts to install manpages
   * Remove conflicting manpage container-mounts(5), Closes: #977502
Checksums-Sha1:
 2eba41876b9db2df8510354e570daf5c06400ece 5513 libpod_2.1.1+dfsg1-3.dsc
 2996d5dada1a510a36ab5b8fefa06ece6931fa6b 15524 
libpod_2.1.1+dfsg1-3.debian.tar.xz
Checksums-Sha256:
 f81336e296aa60096ca8c3121b1c1e4dad02e983bf410c9d26ba7855041e5e2b 5513 
libpod_2.1.1+dfsg1-3.dsc
 

Bug#977502: marked as pending in libpod

[Reinhard Tartler]

Control: tag -1 pending

Hello,

Bug #977502 in libpod reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/libpod/-/commit/bafa6d42d5dfc209c6e864494fe0fc8d16d0494d


Rely on upstream's build scripts to install manpages (Closes: #977502)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/977502

Processed: Bug#977502 marked as pending in libpod

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #977502 [podman,golang-github-containers-common] 
podman,golang-github-containers-common: both ship 
/usr/share/man/man5/containers-mounts.conf.5.gz
Added tag(s) pending.

-- 
977502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Bug#977502 marked as pending in libpod

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #977502 [podman,golang-github-containers-common] 
podman,golang-github-containers-common: both ship 
/usr/share/man/man5/containers-mounts.conf.5.gz
Ignoring request to alter tags of bug #977502 to the same tags previously set

-- 
977502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#977502: marked as pending in libpod

[Reinhard Tartler]

Control: tag -1 pending

Hello,

Bug #977502 in libpod reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/libpod/-/commit/7377dad97a3c3352ad41c9d45c8faedacfa8ef20


Remove conflicting manpage container-mounts(5), Closes: #977502


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/977502

Bug#977919: vm: Mail quoting no longer works in emacs27

[Dirk Eddelbuettel]

Package: vm
Version: 8.2.0b-6
Severity: serious

As per the previous bug report emacs27 and vm are having some issues. Another
wart is that mail replies no longer work. Hitting 'F' for a quoted reply
inserts the full email including headers _unquoted_ and _unindented_ with an
error message 

  Symbol's value as variable is void: mail-yank-hooks

As replying to mail is part of the core functionality, this renders the
package very much incomplete so severity has been set to 'serious'.

Thanks for looking into this.

Dirk

--
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#977103: marked as done (chromium: FTBFS on armhf: error: write to reserved register 'R7')

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 22:45:59 +0100
with message-id 
and subject line Re: Bug#977103: chromium: FTBFS on armhf: error: write to 
reserved register 'R7'
has caused the Debian Bug report #977103,
regarding chromium: FTBFS on armhf: error: write to reserved register 'R7'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: chromium
Version: 83.0.4103.116-3.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

chromium fails to build on armhf:
| FAILED: obj/v8/v8_base_without_compiler/cpu-arm.o 
| clang++ -MMD -MF obj/v8/v8_base_without_compiler/cpu-arm.o.d -DUSE_UDEV 
-DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_GNU_SOURCE 
-DCR_CLANG_REVISION=\"n346557-4e0d9925-2\" -D__STDC_CONSTANT_MACROS 
-D__STDC_FORMAT_MACROS -D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND 
-DDYNAMIC_ANNOTATIONS_ENABLED=0 -DV8_TYPED_ARRAY_MAX_SIZE_IN_HEAP=64 
-DENABLE_MINOR_MC -DV8_INTL_SUPPORT -DV8_USE_EXTERNAL_STARTUP_DATA 
-DV8_CONCURRENT_MARKING -DV8_ARRAY_BUFFER_EXTENSION 
-DV8_ENABLE_LAZY_SOURCE_POSITIONS -DV8_EMBEDDED_BUILTINS -DV8_SHARED_RO_HEAP 
-DV8_WIN64_UNWINDING_INFO -DV8_ENABLE_REGEXP_INTERPRETER_THREADED_DISPATCH 
-DV8_SNAPSHOT_COMPRESSION -DV8_DEPRECATION_WARNINGS -DV8_TARGET_ARCH_ARM 
-DCAN_USE_ARMV7_INSTRUCTIONS -DCAN_USE_VFP3_INSTRUCTIONS -DV8_HAVE_TARGET_OS 
-DV8_TARGET_OS_LINUX -DDISABLE_UNTRUSTED_CODE_MITIGATIONS 
-DV8_DEPRECATION_WARNINGS -DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_40 
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_40 -DUSING_SYSTEM_ICU=1 
-DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_STATIC -DUCHAR_TYPE=uint16_t 
-DU_IMPORT=U_EXPORT -DV8_DEPRECATION_WARNINGS -DUSE_SYSTEM_ZLIB=1 -I../.. -Igen 
-I../../v8 -Igen/v8 -Igen/shim_headers/icui18n_shim 
-Igen/shim_headers/icuuc_shim -Igen/shim_headers/libevent_shim 
-Igen/shim_headers/zlib_shim -I../../v8/include -fno-strict-aliasing 
--param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pthread 
-fcolor-diagnostics -fmerge-all-constants 
-fcrash-diagnostics-dir=../../tools/clang/crashreports -Xclang -mllvm -Xclang 
-instcombine-lower-dbg-declare=0 --target=arm-linux-gnueabihf -march=armv7-a 
-mfloat-abi=hard -mtune=generic-armv7-a -Wno-builtin-macro-redefined 
-D__DATE__= -D__TIME__= -D__TIMESTAMP__= -Xclang -fdebug-compilation-dir 
-Xclang . -no-canonical-prefixes -mfpu=vfpv3-d16 -mthumb -Wall -Wextra 
-Wimplicit-fallthrough -Wunreachable-code -Wthread-safety -Wextra-semi 
-Wno-missing-field-initializers -Wno-unused-parameter -Wno-c++11-narrowing 
-Wno-unneeded-internal-declaration -Wno-undefined-var-template 
-Wno-ignored-pragma-optimize -Wno-pointer-to-int-cast -fno-omit-frame-pointer 
-g0 -Wheader-hygiene -Wstring-conversion -Wtautological-overlap-compare 
-Wmissing-field-initializers -Wunreachable-code -fno-ident -fdata-sections 
-ffunction-sections -fvisibility=default -Wexit-time-destructors 
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include 
-std=c++14 -fno-exceptions -fno-rtti -Wdate-time -D_FORTIFY_SOURCE=2 -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-conversion -Wno-unused-function 
-Wno-unused-variable -Wno-unused-private-field -Wno-deprecated-declarations  
-fno-delete-null-pointer-checks -c ../../v8/src/codegen/arm/cpu-arm.cc -o 
obj/v8/v8_base_without_compiler/cpu-arm.o
| ../../v8/src/codegen/arm/cpu-arm.cc:45:16: error: write to reserved register 
'R7'
|   asm volatile("svc 0\n"
|^
| 1 error generated.
| [32359/39645] CXX obj/v8/v8_base_without_compiler/wasm-serialization.o
| [32360/39645] CXX obj/v8/v8_base_without_compiler/interface-descriptors-arm.o
| [32361/39645] CXX obj/v8/v8_base_without_compiler/assembler-arm.o
| ninja: build stopped: subcommand failed.

See
https://buildd.debian.org/status/fetch.php?pkg=chromium=armhf=83.0.4103.116-3.1%2Bb2=1607626873=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 87.0.4280.88-0.2

Re: Sebastian Ramacher
> | ../../v8/src/codegen/arm/cpu-arm.cc:45:16: error: write to reserved 
> register 'R7'
> |   asm volatile("svc 0\n"
> |^
> | 1 error generated.

The latest upload (thanks Michel!) built fine on armhf.

Christoph--- End Message ---

Bug#977918: vm: Package vm prevents clean emacs27 start

[Dirk Eddelbuettel]

Package: vm
Version: 8.2.0b-6
Severity: serious

Using the (awesome !!) newer emacs 27.1, I am having issues with package
vm. One issue is that on startup, a message 'Package cl is deprecated' is
shown.  Startup appears to finish in interactive, but does not in daemon mode
which is how I used to use emacs. So the message prevents daemon mode from
working.

Moreover, some googling reveals that 'cl' is indeed deprecated and vm ideally
should move on from it.  An upgrade would be great, but it is not clear how
active upstream still is.

A fix / update to vm would be awesome. It's been my goto mail client since
forever.

Dirk

--
https://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#969372: INFO: Bug#969372: uwsgi-emperor: SysV init script does nothing

[Rens Houben]

Okay, this is quick-and-dirty because I didn't have a great deal of time and 
I'm not /that/ great with systemd service files to begin with.

---
[Unit]
Description=uWSGI Emperor
After=syslog.target

[Service]
ExecStart=/usr/bin/uwsgi --ini /etc/uwsgi-emperor/emperor.ini
RuntimeDirectory=uwsgi
Restart=always
KillSignal=SIGQUIT
Type=notify
StandardError=syslog
NotifyAccess=all

[Install]
WantedBy=multi-user.target

There's serious room for improvement there -- the usual way for 
running the Emperor is in Tyrant mode and setting it to retain 
setuid/setguid capabilities before switching down to a 
non-privileged user; I think it would be possible to assign 
it those capabilities in the service file and start it unprivileged 
otherwise, but I'm not good enough to bash that out safely.

Hope this helps, and thanks for the excellent job you guys do,

--Rens.

Bug#977876: marked as done (packagekit-offline-update.service not enabled, not offline updates applied)

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 21:35:31 +
with message-id 
and subject line Bug#977876: fixed in packagekit 1.2.2-2
has caused the Debian Bug report #977876,
regarding packagekit-offline-update.service not enabled, not offline updates 
applied
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977876
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: packagekit
Version: 1.2.1-1
Severity: serious

Hello,

It seems that packagekit-offline-update.service is not enabled meaning
that the offline update functionality is broken. This is annoying as
GNOME is using this functionality meaning that it's possible the the
system of our users are not updated.

The contrib/PackageKit.spec.in file explicitly creates a symlink to 
system-update.target.wants:

mkdir -p $RPM_BUILD_ROOT/usr/lib/systemd/system/system-update.target.wants
ln -sf /usr/lib/systemd/system/packagekit-offline-update.service \

$RPM_BUILD_ROOT/usr/lib/systemd/system/system-update.target.wants/packagekit-offline-update.service

That symlink should also be created IMVHO (fwupd is also doing that)

Could you please make sure that this is done?

Kind regards,
Laurent Bigonville


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

Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
--- End Message ---
--- Begin Message ---
Source: packagekit
Source-Version: 1.2.2-2
Done: Matthias Klumpp 

We believe that the bug you reported is fixed in the latest version of
packagekit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated packagekit package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 22 Dec 2020 22:14:10 +0100
Source: packagekit
Architecture: source
Version: 1.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klumpp 
Changed-By: Matthias Klumpp 
Closes: 977876
Changes:
 packagekit (1.2.2-2) unstable; urgency=medium
 .
   [ Laurent Bigonville ]
   * debian/control: Build-Dependis against libplymouth-dev (>= 0.9.5) and
 Breaks against previous version of the plymouth package
   * debian/packagekit.links: Ensure that the packagekit-offline-update service
 is started in the system-update.target.wants target (Closes: #977876)
Checksums-Sha1:
 b5adc4c16a0c9a19a8b720ee8bffc06480c41e8e 3008 packagekit_1.2.2-2.dsc
 283a9b30ea4f78419bd159a7ffc6a7590fe3f2f1 2745144 packagekit_1.2.2.orig.tar.xz
 f2ca71acb846876a18e703cd411cf13a42f4b3aa 23816 packagekit_1.2.2-2.debian.tar.xz
 ecdc2f6508098337234bac4f2b67035eae0e1a45 16888 
packagekit_1.2.2-2_source.buildinfo
Checksums-Sha256:
 32b7de3099e07817dd03e43e0cda645c283357d570fcebcd3a33a5d608d39443 3008 
packagekit_1.2.2-2.dsc
 9e533bc1a445c210da388a77bef17bd4c2df0fde498e628f0f0a1601f6f19045 2745144 
packagekit_1.2.2.orig.tar.xz
 b63eed9ec96a7a0847a1f70c7e3bea2bbca9435f1438bf0c6774a1f1253b8509 23816 
packagekit_1.2.2-2.debian.tar.xz
 4046770ca748991311b787146196a6aa6d319e0641ff3e916e5432ac6d10c6dc 16888 
packagekit_1.2.2-2_source.buildinfo
Files:
 3754f5479be522acf50ca8b3c4f0a71a 3008 admin optional packagekit_1.2.2-2.dsc
 2bfa2687bcc4e189bb90e2228c11e558 2745144 admin optional 
packagekit_1.2.2.orig.tar.xz
 03634a9b61c2c123389efd0a934f9d15 23816 admin optional 
packagekit_1.2.2-2.debian.tar.xz
 1d03c21a464db54bb0e2e818ac4d41f4 16888 admin optional 
packagekit_1.2.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEE0zo/DKFrCsxRpgc4SUyKX79N7OsFAl/iYsQPHG1ha0BkZWJp
YW4ub3JnAAoJEElMil+/Tezrd74P/01C5A6pyTGwQCqbhdrsPe7PDPTGw9/FLgZr
m8WRzTlIncx//iK7DpkQIYjqov7ADC975OnVZsW+3b4iNSIQTMmQ7adndLDvKttt

Bug#957082: marked as done (cfengine3: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 22:21:25 +0100
with message-id <60cbae9d-5aca-53f6-ed8a-598a00f17...@debian.org>
and subject line Re: cfengine3: ftbfs with GCC-10
has caused the Debian Bug report #957082,
regarding cfengine3: ftbfs with GCC-10
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
957082: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957082
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cfengine3
Version: 3.12.1-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/cfengine3_3.12.1-2_unstable_gcc10.log
The last lines of the build log are at the end of this report.

To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-10/porting_to.html

[...]
libtool: link: gcc -pthread -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -g -Wall 
-Wno-pointer-sign -Werror=implicit-function-declaration -Wunused-parameter -O2 
-DNDEBUG -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-z 
-Wl,relro -Wl,-z -Wl,now -o .libs/alloc_test alloc_test.o  
../../libpromises/.libs/libpromises.so ./.libs/libtest.a -llmdb -lpcre -lssl 
-lcrypto -lacl -lxml2 -ldl -lrt -lm -pthread -Wl,-rpath -Wl,/usr/lib/cfengine3
libtool: link: gcc -pthread -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -g -Wall 
-Wno-pointer-sign -Werror=implicit-function-declaration -Wunused-parameter -O2 
-DNDEBUG -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-z -Wl,relro -Wl,-z -Wl,now -Wl,-z 
-Wl,relro -Wl,-z -Wl,now -o .libs/string_writer_test string_writer_test.o  
../../libpromises/.libs/libpromises.so ./.libs/libtest.a -llmdb -lpcre -lssl 
-lcrypto -lacl -lxml2 -ldl -lrt -lm -pthread -Wl,-rpath -Wl,/usr/lib/cfengine3
/bin/bash ../../libtool  --tag=CC   --mode=link gcc  -pthread -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -g -Wall -Wno-pointer-sign 
-Werror=implicit-function-declaration -Wunused-parameter -O2 -DNDEBUG -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,-z,relro -Wl,-z,now -o 
file_writer_test file_writer_test.o gcov-stub.o 
../../libpromises/libpromises.la libtest.la -llmdb -lpcre   -lssl -lcrypto  
  -lacl -lxml2   -ldl -lrt -lm  
/bin/bash ../../libtool  --tag=CC   --mode=link gcc  -pthread -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -g -Wall -Wno-pointer-sign 
-Werror=implicit-function-declaration -Wunused-parameter -O2 -DNDEBUG -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,-z,relro -Wl,-z,now -o 
xml_writer_test xml_writer_test.o xml_writer.o cleanup.o libtest.la libstr.la 
-llmdb -lpcre   -lssl -lcrypto-lacl -lxml2   -ldl -lrt -lm  
/bin/bash ../../libtool  --tag=CC   --mode=link gcc  -pthread -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -g -Wall -Wno-pointer-sign 
-Werror=implicit-function-declaration -Wunused-parameter -O2 -DNDEBUG -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -Wl,-z,relro -Wl,-z,now -o 
sequence_test sequence_test.o ../../libpromises/libpromises.la libtest.la 
-llmdb -lpcre   -lssl -lcrypto-lacl -lxml2   -ldl -lrt -lm  
/bin/bash ../../libtool  --tag=CC   --mode=link gcc  

Bug#958880: marked as done (mplayer: package neglected)

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 22:22:07 +0100
with message-id <3246ee46-4227-3992-e7fb-e52001514...@debian.org>
and subject line Re: mplayer: package neglected
has caused the Debian Bug report #958880,
regarding mplayer: package neglected
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
958880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mplayer
Version: 2:1.3.0-8
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

MPlayer upstream saw no new release for 3 years between 2016 and 2019
and MPlayer in Debian did not yet upgrade to latest release since a year,
which means effectively MPlayer in Debian is 4 years old.

MPlayer is already arguably surpassed by MPV for its playout features,
and ffmpeg arguably surpasses its mencoder transcoding features.
Possibly some users have a specific desire to use MPlayer, but at least
some of our users keep using MPlayer simply because they are unaware of
the existence of MPV, and when pointed out they agree it works better
for them.

Let's not do our users a disservice by shipping an inferior media player.

Please lower or close this bugreport *only* if a) you have compared with
new releases of mpv and ffmpeg that mplayer/mencoder really is still
needed in Debian *AND* your plan to _maintain_ MPlayer in Debian for the
long term (not if you want to help fix a single bug).

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl6lRS4ACgkQLHwxRsGg
ASGmRw//VDB3AcKdXO96RJmfM8hKMFHLFQNE1RkXlLnJ8QBqCBpfVLS54UK0079J
gVPp7/aDnXm1M8Esp1ir+dVNvurPyLvsMFQMBDoXVLJgQOXG+o+x4MKVOKsPfh6s
WnTFeegwV0QJIBJ28E/cDvVB2zNW43ZZGJHIRAkobic1oqG5WD+rWBJtgrndW+0b
G7lmN62gWcnePtY5sXFwgzgB9CHVjp3Bkbyk3WVkclrnIcnRFFa5xMJT7441umGf
9tvXwSzVDO4xrHN6SjeSUN/4/k8oNpG47s2x5x7tJ/yTt0DQa3uIMBC2avZuaF+9
ttcmdTjKF8/gs5CLa9tqKUM2sHqknbWC+Q1UTZZuXqAKvdCXdW8ymRYcFSS/HqYU
AmGxkYjWQqXGBHikBbNO8uvtkkqcPwmSNXWlce5XsI6v4jdUUMQ8I2M7f5uwLey2
zWm50ampIgd5QvJmR6nWJ3zCOMQOnzaajRxGE606xSMhnlZ6J0SAe79q40hyO05J
iVvzlyvW4amBaG7As+YeJbp80twRpMGln+SQcAZ8Y+VicBRyaPithAFvUyfgbdLP
LGtEa6tPh0O6/uQICdYxS89hV457TM3QZhbTIcWRbRZhJg9DTWEJXzOKqW8jUgxo
YdNdySDPq/cye8Oxu39w2pTWKbKIP3vijVmq8d/T6tGw78hO/NE=
=SuT/
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 2:1.4+ds1-1

Hi,

On Sun, 26 Apr 2020 10:24:17 +0200 Jonas Smedegaard  wrote:
> Source: mplayer
> Version: 2:1.3.0-8
> Severity: grave
> Justification: renders package unusable
>
> MPlayer upstream saw no new release for 3 years between 2016 and 2019
> and MPlayer in Debian did not yet upgrade to latest release since a year,
> which means effectively MPlayer in Debian is 4 years old.

A new version was uploaded.

Paul





OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---

Bug#943462: [polkit-kde-agent-1] Fails to start with elogind

[Paul Gevers]

Hi all,

On Fri, 25 Oct 2019 07:04:40 +0500 Alex Volkov 
wrote:
> I'm using elogind 239.3+20190131-1+debian1 and the agent fails to start
> at the kde launch with the following diagnostics:

Any progress on this? The bullseye freeze is approaching.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Bug#942078: [high quality bug] baloo crash, can't recover; forced reindex does not fix; unusable via dolphin C-f

[Paul Gevers]

Hi all,

On Wed, 09 Oct 2019 18:53:25 -0400 Nicholas D Steeves
 wrote:
> Recently baloo has been crashing whenever I log in.  Today I decided it
> was a persistent and serious enough problem that a serious bug was
> warranted.  I've attached the backtrace produced by drkonqi.  Here is
> some additional info that I hope will help quickly resolve this bug.

Any progress on this? The bullseye freeze is approaching. baloo-kf5 is a
key package so isn't autoremoved. Hence it's on the Release Team's radar.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: r-cran-arsenal: autopkgtest failure on several architectures

[Debian Bug Tracking System]

Processing control commands:

> block 975859 by -1
Bug #975859 {Done: Paul Gevers } [src:r-cran-haplo.stats] 
src:r-cran-haplo.stats: fails to migrate to testing for too long: Depends on 
non-migrating package
975859 was not blocked by any bugs.
975859 was not blocking any bugs.
Added blocking bug(s) of 975859: 977915

-- 
975859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975859
977915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#976891: fastboot exits with "fake placeholder until fastboot builds" message

[Hans-Christoph Steiner]

Thanks for jumping in Roger!  I reviewed it with cdesai, and we thought 
those libraries were not used on the "host" version, only when built as 
part of Android OS.  I do think libfec would be useful if someone wants 
to package adbd for Debian.  The Google Android Tools builds do not 
include adbd for the host, only for the Android OS.


Right now, the only blocker I know about is the assembler code in 
android-platform-art, which Michel and I are working on now.

Bug#977915: r-cran-arsenal: autopkgtest failure on several architectures

[Adrian Bunk]

Source: r-cran-arsenal
Version: 3.5.0-2
Severity: serious
Control: block 975859 by -1

https://tracker.debian.org/pkg/r-cran-arsenal

Issues preventing migration:
autopkgtest for r-cran-arsenal/3.5.0-2: amd64: Pass, arm64: Regression ♻ , 
armhf: Pass, i386: Regression ♻ , ppc64el: Regression ♻

Processed: tagging 956762

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 956762 + pending
Bug #956762 [autokey-gtk] autokey-gtk: Depends on deprecated libappindicator
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
956762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 974207

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 974207 + upstream
Bug #974207 [src:psi-plus] psi-plus: FTBFS with Qt 5.15
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
974207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 956772

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 956772 + pending
Bug #956772 [src:hime] hime: Depends on deprecated libappindicator
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
956772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956772
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 956782

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 956782 + pending
Bug #956782 [src:zeal] zeal: Build-Depends (unnecessarily?) on deprecated 
libappindicator
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
956782: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956782
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 956774

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 956774 + pending
Bug #956774 [src:kylin-burner] kylin-burner: Depends on deprecated 
libappindicator
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
956774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#934242: crystalhd: unusable without (available and properly working) firmware

[Paul Gevers]

affects 934242 src:kylin-video
user release.debian@packages.debian.org
usertag 934242 bullseye-will-remove

Hi,

On 21-12-2020 23:32, Jonas Smedegaard wrote:
> Yes, there are still packages depending on it: Someone needs to work 
> actively with those still believing the library is more than snakeoil - 
> because our mechanisms auto-pressuring packages to to stay alert and in 
> line or else get kicked from testing works only on edge packages - 
> packages "well connected" in Debian are not affected.
> 
> (while the allegory is funny, I really don't mean to imply that the 
> mechanisms were _intented_ to treat packages unequally, only that in 
> effect it does)

So, let's inform the kylin-video team that we're about to remove
crystalhd from bullseye.

@kylin-video team, please drop your Build-Depends on libcrystalhd-dev
and your Depends on libcrystalhd3. If this doesn't happen in a week or
two, kylin-video will be removed from bullseye too.

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed (with 5 errors): Re: crystalhd: unusable without (available and properly working) firmware

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 934242 src:kylin-video
Bug #934242 [src:crystalhd] crystalhd: unusable without (available and properly 
working) firmware
Added indication that 934242 affects src:kylin-video
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was elb...@debian.org).
> usertag 934242 bullseye-will-remove
There were no usertags set.
Usertags are now: bullseye-will-remove.
> Hi,
Unknown command or malformed arguments to command.
> On 21-12-2020 23:32, Jonas Smedegaard wrote:
Unknown command or malformed arguments to command.
> > Yes, there are still packages depending on it: Someone needs to work
Unknown command or malformed arguments to command.
> > actively with those still believing the library is more than snakeoil -
Unknown command or malformed arguments to command.
> > because our mechanisms auto-pressuring packages to to stay alert and in
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.

Please contact me if you need assistance.
-- 
934242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 956778

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 956778 + pending
Bug #956778 [src:parcellite] parcellite: Depends on deprecated libappindicator
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
956778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956778
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#956766: gcin: Build-Depends (unnecessarily?) on deprecated libappindicator

[Adrian Bunk]

On Wed, Apr 15, 2020 at 09:23:06AM +0100, Simon McVittie wrote:
> Source: gcin
> Version: 2.8.8+dfsg1-1
> Tags: sid bullseye
> Severity: important
> Control: block 895037 by -1
> User: pkg-ayatana-de...@lists.alioth.debian.org
> Usertags: ayatana-appindicator
> 
> This package Build-Depends on libappindicator3-dev, which is
> deprecated and unmaintained. The supported replacement appears to be
> libayatana-appindicator3-dev.
> 
> It doesn't seem to have a runtime dependency on libappindicator, so perhaps
> the build-dependency is unused?
>...

It seems to be an undeclared runtime dependency, see #921005.

> smcv

cu
Adrian

Bug#976846: marked as done (python3-stdlib-extensions build depends on non-default python3 version)

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 20:18:36 +
with message-id 
and subject line Bug#976846: fixed in python3-stdlib-extensions 3.9.1-1
has caused the Debian Bug report #976846,
regarding python3-stdlib-extensions build depends on non-default python3 version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
976846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python3-stdlib-extensions
Version: 3.8.6-1
Severity: serious

Versions other then 3.9 should not be build depended on in bullseye.
--- End Message ---
--- Begin Message ---
Source: python3-stdlib-extensions
Source-Version: 3.9.1-1
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
python3-stdlib-extensions, which is due to be installed in the Debian FTP 
archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 976...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3-stdlib-extensions 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 22 Dec 2020 19:55:15 +0100
Source: python3-stdlib-extensions
Architecture: source
Version: 3.9.1-1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Closes: 976846
Changes:
 python3-stdlib-extensions (3.9.1-1) unstable; urgency=medium
 .
   * Update 3.9 extensions and modules to the 3.9.1 release.
   * Update 3.8 extensions and modules to the 3.8.7 release.
   * Stop building the extensions for 3.8. Closes: #976846.
   * python3-lib2to3, python3-distutils: Add the :any qualifier to the
 python3 dependencies. See: #964330.
   * Bump standards versions.
Checksums-Sha1:
 b281e971a2651f5506b43c802031ccb6c73a81d6 2450 
python3-stdlib-extensions_3.9.1-1.dsc
 e124b2bdef265e6c97ecadd9cc33caf7cf707d60 1096448 
python3-stdlib-extensions_3.9.1.orig.tar.xz
 964bbd4e35bbb1ad68a98841878e461edbcd05e7 18496 
python3-stdlib-extensions_3.9.1-1.debian.tar.xz
 cdcb1fd3d434e29c74b8338ecc234822fd555649 8272 
python3-stdlib-extensions_3.9.1-1_source.buildinfo
Checksums-Sha256:
 a6cd74043a8100a17b1e1d356796af46799b78879c16b9a1c26d03dd643ccaaa 2450 
python3-stdlib-extensions_3.9.1-1.dsc
 48223c1ec0f8a36161c2edfb60dae6c35763341489a789a142c70bb56363e6db 1096448 
python3-stdlib-extensions_3.9.1.orig.tar.xz
 25ac09c73f89bcddba1fd9d408f1d358a0478d0050b5affec5fa31e5c3ed1c3d 18496 
python3-stdlib-extensions_3.9.1-1.debian.tar.xz
 56daccf81a49fa7f2f01f119e7559fdd4d51ce03c5ceb5ecd4eaf1bff0223a18 8272 
python3-stdlib-extensions_3.9.1-1_source.buildinfo
Files:
 5195d6edcb8fa799abc1ecd2ed3421d6 2450 python optional 
python3-stdlib-extensions_3.9.1-1.dsc
 6b0d6089fb33b998dac64c5ca5743c5b 1096448 python optional 
python3-stdlib-extensions_3.9.1.orig.tar.xz
 9ee22bafa49285c62d4d1b2fe1cdbe4c 18496 python optional 
python3-stdlib-extensions_3.9.1-1.debian.tar.xz
 a93fa65ee7c5c2b4d39d3fdfb545cf79 8272 python optional 
python3-stdlib-extensions_3.9.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl/iTZcQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9X5iD/4+6C+ILFvAcwe4ln53wJsVQV3AsiiswxkD
xKlRM9vIANkkPOmdoPcWGIghmuhpqMKk1HdCW8OoETNxpENmmovf3/sJAULBAPNl
66mKw2heJ3QEmCPu8xrqkqTxYIhEtGoaG8qmH7ox0+4NrHVcw6+A7qoajrnXBkOT
atGcRzya95tI5IGcH+cSt68GoYNxfAbhvNNMCg4bpnJKl1pYNAPB+ytk5+LHyl4K
uu1qu6S37RUoXFNqRt7EGkJrr64KgT4n41guPK/h98ccGw8sJcKN+NugSCqd//YU
m6C72RP5lY+fSB+pUqivtRwX/g3W3r/ZIQh9G1vUmDYqD3PNtAWFrabQyM3gBNEd
I5stTU7ygVH51D2V/tXpS0jK7f0EG9gfVp4F1EChDOVl6vTgfrAdpCnKKbUyF8E6
BjzfMDjPbVJeHLLBoxyNfSn62MdvbbAIc4tK0uTH7j9qL50MSxoQ0AboOfVWDKxS
Th0M32jkqedbxh4FbmJ2eCSVgD6B83sEEOaPZIqWgp4b4Y4lOQJ6mEJnKHQWPAyF
wqI5xfD9WXye5HLUPfQEWdhd3q5ozE871ECOFBtXEUAPul4hRQVP/J10QXBd2nlr
n4uMRYXLi3EEkwymTDZj4lYjFXtggtXrGIP9eipRe7Yci8g6ca2UGbm7BwJpuvoc
/6JOUuGnFg==
=ym/D
-END PGP SIGNATURE End Message ---

Processed: tagging 972767

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 972767 + patch
Bug #972767 [src:frr] frr ftbfs with python3.9
Added tag(s) patch.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
972767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 921005 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 921005 serious
Bug #921005 [gcin] Missing manual dependency for package gcin on 
libappindicator3-1
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
921005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Workaround for the BTS not yet properly handling bookworm

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 954812 important
Bug #954812 [src:pythonmagick] pythonmagick: autopkgtest regression: cannot 
import name '_PythonMagick'
Severity set to 'important' from 'serious'
> severity 975926 important
Bug #975926 [enigmail] enigmail should not be shipped in bookworm
Severity set to 'important' from 'serious'
> severity 976686 important
Bug #976686 [src:glom] glom: mixing incompatible libpython and libboost_python
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
954812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954812
975926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975926
976686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: block 974546 with 974856

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 974546 with 974856
Bug #974546 [src:klatexformula] klatexformula FTBFS: error: invalid use of 
incomplete type ‘class QPainterPath’
974546 was not blocked by any bugs.
974546 was not blocking any bugs.
Added blocking bug(s) of 974546: 974856
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
974546: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974546
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 975823

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 975823 + upstream
Bug #975823 [src:rally-openstack] rally-openstack: FTBFS: AttributeError: 
module 'kubernetes.client.api_client' has no attribute 'models'
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
975823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: retitle 975822 to pyramid-jinja2: Missing build dependency on python3-webtest

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 975822 pyramid-jinja2: Missing build dependency on python3-webtest
Bug #975822 [src:pyramid-jinja2] pyramid-jinja2: FTBFS: dh_auto_test: error: 
pybuild --test -i python{version} -p "3.8 3.9" returned exit code 13
Changed Bug title to 'pyramid-jinja2: Missing build dependency on 
python3-webtest' from 'pyramid-jinja2: FTBFS: dh_auto_test: error: pybuild 
--test -i python{version} -p "3.8 3.9" returned exit code 13'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
975822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975822
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 975817 is forwarded to https://github.com/oVirt/mom/commit/655d6b36f9f80ced1e411bc8504110a261939808

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 975817 
> https://github.com/oVirt/mom/commit/655d6b36f9f80ced1e411bc8504110a261939808
Bug #975817 [src:mom] mom: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 
returned exit code 2
Set Bug forwarded-to-address to 
'https://github.com/oVirt/mom/commit/655d6b36f9f80ced1e411bc8504110a261939808'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
975817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 975810

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 975810 + upstream
Bug #975810 [src:fonts-pecita] fonts-pecita: FTBFS: Error: Validation error
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
975810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 975801

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 975801 + upstream
Bug #975801 [src:python-aioxmpp] python-aioxmpp: FTBFS: TypeError: 'Lock' 
object is not iterable
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
975801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Fixed in 10.5.0

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 975790 fixed-upstream
Bug #975790 [src:ironic-inspector] ironic-inspector: FTBFS: 
sqlalchemy.exc.ArgumentError: column object 'temp_started_at' already assigned 
to table 'nodes'
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
975790: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975790
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Move where the problem is

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 975747 android-libbacktrace 1:10.0.0+r36-1~stage1
Bug #975747 [src:android-platform-build] android-platform-build: FTBFS: ld: 
/usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined reference to 
`unwindstack::RemoteMaps::GetMapsFile[abi:cxx11]() const'
Bug reassigned from package 'src:android-platform-build' to 
'android-libbacktrace'.
No longer marked as found in versions android-platform-build/1:8.1.0+r23-5.
Ignoring request to alter fixed versions of bug #975747 to the same values 
previously set
Bug #975747 [android-libbacktrace] android-platform-build: FTBFS: ld: 
/usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined reference to 
`unwindstack::RemoteMaps::GetMapsFile[abi:cxx11]() const'
Marked as found in versions android-platform-system-core/1:10.0.0+r36-1~stage1.
> affects 975747 src:android-platform-build
Bug #975747 [android-libbacktrace] android-platform-build: FTBFS: ld: 
/usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined reference to 
`unwindstack::RemoteMaps::GetMapsFile[abi:cxx11]() const'
Added indication that 975747 affects src:android-platform-build
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
975747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 975753

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 975753 + fixed
Bug #975753 {Done: Sylvestre Ledru } 
[src:rust-universal-hash] rust-universal-hash: FTBFS: build-dependency not 
installable: librust-generic-array-0.12+default-dev
Added tag(s) fixed.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
975753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#977912: fdroidserver: autopkgtest regression in testing: symbol lookup error

[Paul Gevers]

Source: fdroidserver
Version: 1.1.10-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent change in testing the autopkgtest of your package started
to fail. I copied some of the output at the bottom of this report. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

https://ci.debian.net/data/autopkgtest/testing/amd64/f/fdroidserver/8897248/log.gz

autopkgtest [00:12:33]: test command1: echo Depends; export LANG=C.UTF-8
ANDROID_HOME=/usr/lib/android-sdk TRAVIS_OS_NAME=osx;
fdroid=/usr/bin/fdroid ./tests/run-tests
autopkgtest [00:12:33]: test command1: [---
Depends
Using ANDROID_HOME=/usr/lib/android-sdk
Setting Workspace to /tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src
+ echo_header 'run commit hooks'
+ cd /tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src
==
run commit hooks
+ test -x ./hooks/pre-commit
+ echo_header 'test python getsig replacement'
==
test python getsig replacement
+ cd /tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/tests/getsig
+ ./make.sh
+ cd /tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/tests
+ for testcase in $WORKSPACE/tests/*.TestCase
+ '['
/tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/tests/build.TestCase
==
/tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/tests/install.TestCase
']'
+ /tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/tests/build.TestCase
DEBUG:root:Forcing build-tools FAKE_VERSION_FOR_TESTING in
/tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/.testfiles/test_force_gradle_build_tools9injac2r/source-files/com.kunzisoft.testcase/build.gradle
DEBUG:root:Forcing build-tools FAKE_VERSION_FOR_TESTING in
/tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/.testfiles/test_force_gradle_build_tools9injac2r/source-files/at.bitfire.davdroid/build.gradle
DEBUG:root:Forcing build-tools FAKE_VERSION_FOR_TESTING in
/tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/.testfiles/test_force_gradle_build_tools9injac2r/source-files/com.nextcloud.client/build.gradle
DEBUG:root:Forcing build-tools FAKE_VERSION_FOR_TESTING in
/tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/.testfiles/test_force_gradle_build_tools9injac2r/source-files/eu.siacs.conversations/build.gradle
DEBUG:root:Forcing build-tools FAKE_VERSION_FOR_TESTING in
/tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/.testfiles/test_force_gradle_build_tools9injac2r/source-files/firebase-suspect/build.gradle
DEBUG:root:Forcing build-tools FAKE_VERSION_FOR_TESTING in
/tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/.testfiles/test_force_gradle_build_tools9injac2r/source-files/firebase-suspect/app/build.gradle
DEBUG:root:Forcing build-tools FAKE_VERSION_FOR_TESTING in
/tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/.testfiles/test_force_gradle_build_tools9injac2r/source-files/firebase-whitelisted/build.gradle
DEBUG:root:Forcing build-tools FAKE_VERSION_FOR_TESTING in
/tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/.testfiles/test_force_gradle_build_tools9injac2r/source-files/firebase-whitelisted/app/build.gradle
DEBUG:root:Forcing build-tools FAKE_VERSION_FOR_TESTING in
/tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/.testfiles/test_force_gradle_build_tools9injac2r/source-files/osmandapp/osmand/build.gradle
DEBUG:root:Forcing build-tools FAKE_VERSION_FOR_TESTING in
/tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/.testfiles/test_force_gradle_build_tools9injac2r/source-files/open-keychain/open-keychain/build.gradle
DEBUG:root:Forcing build-tools FAKE_VERSION_FOR_TESTING in
/tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/.testfiles/test_force_gradle_build_tools9injac2r/source-files/open-keychain/open-keychain/OpenKeychain/build.gradle
DEBUG:root:Forcing build-tools FAKE_VERSION_FOR_TESTING in
/tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/.testfiles/test_force_gradle_build_tools9injac2r/source-files/fdroid/fdroidclient/build.gradle
DEBUG:root:Forcing build-tools FAKE_VERSION_FOR_TESTING in
/tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/.testfiles/test_force_gradle_build_tools9injac2r/source-files/Zillode/syncthing-silk/build.gradle
./usr/lib/android-sdk/build-tools/debian/aapt: symbol lookup error:
/usr/lib/x86_64-linux-gnu/android/libbacktrace.so.0: undefined symbol:
_ZN11unwindstack12ElfInterfaceD2Ev
E
==
ERROR: test_get_apk_metadata (__main__.BuildTest)
--
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.ms584tuq/downtmp/build.loi/src/tests/build.TestCase",
line 82, in test_get_apk_metadata
 

Processed: bug 975789 is forwarded to https://github.com/go-acme/lego/pull/1176

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 975789 https://github.com/go-acme/lego/pull/1176
Bug #975789 [src:golang-github-xenolf-lego] golang-github-xenolf-lego: FTBFS: 
src/github.com/go-acme/lego/providers/dns/inwx/inwx.go:85:6: assignment 
mismatch: 1 variable but d.client.Account.Login returns 2 values
Set Bug forwarded-to-address to 'https://github.com/go-acme/lego/pull/1176'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
975789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: retitle 975787 to golang-github-howeyc-fsnotify: Frequent FTBFS due to flaky test

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 975787 golang-github-howeyc-fsnotify: Frequent FTBFS due to flaky test
Bug #975787 [src:golang-github-howeyc-fsnotify] golang-github-howeyc-fsnotify: 
FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 
github.com/howeyc/fsnotify returned exit code 1
Changed Bug title to 'golang-github-howeyc-fsnotify: Frequent FTBFS due to 
flaky test' from 'golang-github-howeyc-fsnotify: FTBFS: dh_auto_test: error: cd 
obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/howeyc/fsnotify 
returned exit code 1'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
975787: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#977911: debian-archive-keyring: bullseye archive signing key

[Adam D. Barratt]

Source: debian-archive-keyring
Version: 2019.1
Severity: serious
X-Debbugs-Cc: ftpmas...@debian.org, debian-rele...@lists.debian.org

Hi,

We need a new archive signing key for bullseye, so that we can include
it in the release.

Regards,

Adam

Bug#977910: debian-archive-keyring: bullseye SRM key

[Adam D. Barratt]

Source: debian-archive-keyring
Version: 2019.1
Severity: serious
X-Debbugs-Cc: debian-rele...@lists.debian.org

Hi,

We need an SRM key for bullseye, so that we can include it in the
release.

Regards,

Adam

Bug#939527: marked as done (vcdimager contains one file with different license)

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 18:38:29 +
with message-id 
and subject line Bug#939527: fixed in vcdimager 2.0.1+dfsg-4
has caused the Debian Bug report #939527,
regarding vcdimager contains one file with different license
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
939527: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939527
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: vcdimager https://tracker.debian.org/pkg/vcdimager
Version: 0.7.24
Debian copyright notion.
https://metadata.ftp-master.debian.org/changelogs//main/v/vcdimager/vcdimager_2.0.1+dfsg-3_copyright

The file changed on 17-03-2011 from gpl 2 or later to gpl 2
https://cvs.savannah.gnu.org/viewvc/vcdimager/vcdimager/lib/sector.c?view=markup

Already send a message to (not visible at the moment)
https://lists.gnu.org/mailman/listinfo/bug-vcdimager/
also
https://directory.fsf.org/wiki/User_talk:Rockyb
more info
https://directory.fsf.org/wiki/vcdimager


-
This free account was provided by VFEmail.net - report spam to ab...@vfemail.net

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  
--- End Message ---
--- Begin Message ---
Source: vcdimager
Source-Version: 2.0.1+dfsg-4
Done: Baptiste Beauplat 

We believe that the bug you reported is fixed in the latest version of
vcdimager, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 939...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Baptiste Beauplat  (supplier of updated vcdimager package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 20 Dec 2020 22:21:55 +0100
Source: vcdimager
Architecture: source
Version: 2.0.1+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Baptiste Beauplat 
Closes: 939527
Changes:
 vcdimager (2.0.1+dfsg-4) unstable; urgency=medium
 .
   * QA upload.
   * Host packaging on Salsa:
 - Add Salsa CI pipeline
 - Use DEP14 repository layout:
   + Add gbp.conf
   + Remove uupdate from d/watch
 - Add Vcs-* fields
   * Bump d/watch version to 4:
 - Use @@ variables
 - Split url and matching-pattern
   * Bump Standard-Version to 4.5.1
   * Bump debhelper to 13:
 - Switch from debhelper to debhelper-compat in d/control
 - Remove d/compat
   * Convert copyright to DEP5:
 - Document GPL-2.0-only license for ./lib/sector.c (Closes: #939527)
 - Document repack due to non-free documentation
   * Remove trailing newlines in changelog
   * Add DEP12 upstream metadata
   * Add missing Build-Depends-Package to d/symbols
   * Reformat patches with `gbp pq` (headers + rename with numbers)
   * Add patch to fix some spelling mistake in the code
   * Fix manpage description:
 - Add --enable-maintainer-mode configure flag to build manpages from source
 - Add help2man as Build-Depends
 - Add patch to use the correct description info for help2man
 - Backup and restore original manpages on clean
Checksums-Sha1:
 a78ca5771db5ee95b4369ba0a5ac68dd672f61fa 2108 vcdimager_2.0.1+dfsg-4.dsc
 e9fb62d37c4e5b2b38a2ef20b2bdd59d36f8bdc0 10896 
vcdimager_2.0.1+dfsg-4.debian.tar.xz
 e219860becaa13aa91fa30df6b4eec087e14710e 7562 
vcdimager_2.0.1+dfsg-4_amd64.buildinfo
Checksums-Sha256:
 11b7dad434a8e9f40babb98dd47eff2f604ca6c5e1ce349702fd9212d0ad9c4d 2108 
vcdimager_2.0.1+dfsg-4.dsc
 48144c2f356a4b463003be4feda10fd19b7d34200da854eb165f7bbc089d4666 10896 
vcdimager_2.0.1+dfsg-4.debian.tar.xz
 c62bf032f8b49b9fd6dbf047edfaecf5ee7deeed0e48998643e439dbed20eccf 7562 
vcdimager_2.0.1+dfsg-4_amd64.buildinfo
Files:
 c62a20e7c8d190675e64df90ba7cb902 2108 otherosfs optional 
vcdimager_2.0.1+dfsg-4.dsc
 a0461e1d3d8d581b2ad16e1595a7ee55 10896 otherosfs optional 
vcdimager_2.0.1+dfsg-4.debian.tar.xz
 57bf29f8d97df5529521404c70c5927f 7562 otherosfs optional 
vcdimager_2.0.1+dfsg-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#976886: movim: diff for NMU version 0.17.1-1.1

[Robin Gustafsson]

Control: tags 976886 + patch
Control: tags 976886 + pending

Dear maintainer,

I've prepared an NMU for movim (versioned as 0.17.1-1.1). The diff
is attached to this message.

I require a sponsor to have it uploaded.

Regards.

diff -Nru movim-0.17.1/debian/autoload.php movim-0.17.1/debian/autoload.php
--- movim-0.17.1/debian/autoload.php2020-03-09 19:45:26.0 +
+++ movim-0.17.1/debian/autoload.php2020-12-22 14:00:10.0 +
@@ -2,7 +2,7 @@
 
 require_once('Composer/Autoload/ClassLoader.php');
 include_once('/usr/share/php/HTMLPurifier.composer.php');
-include_once('/usr/share/php/Illuminate/Support/helpers.php');
+include_once('/usr/share/php/Illuminate/Database/autoload.php');
 include_once('/usr/share/php/GuzzleHttp/Psr7/functions_include.php');
 include_once('/usr/share/php/React/Promise/functions_include.php');
 include_once('/usr/share/php/React/Promise/Stream/functions_include.php');
diff -Nru movim-0.17.1/debian/changelog movim-0.17.1/debian/changelog
--- movim-0.17.1/debian/changelog   2020-03-30 15:10:58.0 +
+++ movim-0.17.1/debian/changelog   2020-12-22 14:00:13.0 +
@@ -1,3 +1,10 @@
+movim (0.17.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use php-illuminate-database 6 (Closes: #976886)
+
+ -- Robin Gustafsson   Tue, 22 Dec 2020 15:00:13 +0100
+
 movim (0.17.1-1) unstable; urgency=medium
 
   * New upstream version.
diff -Nru movim-0.17.1/debian/patches/composer-versions.diff 
movim-0.17.1/debian/patches/composer-versions.diff
--- movim-0.17.1/debian/patches/composer-versions.diff  2020-03-09 
22:23:38.0 +
+++ movim-0.17.1/debian/patches/composer-versions.diff  2020-12-22 
14:00:10.0 +
@@ -25,9 +25,8 @@
  "defuse/php-encryption": "^2.2.1",
  
 -"robmorgan/phinx": "^0.11.4",
--"illuminate/database": "^6.0",
 +"robmorgan/phinx": "^0.9",
-+"illuminate/database": "^5.8",
+ "illuminate/database": "^6.0",
  "doctrine/dbal": "^2.10",
  
  "cboden/ratchet": "^0.4.2",

Bug#976891: fastboot exits with "fake placeholder until fastboot builds" message

[Roger Shimizu]

I'm trying to restore fastboot back to build for 1:10.0.0+r36-1~stage1.3
however, seems there're a few new dependencies.

one is android-libfec inside src:android-platform-system-extras
I already uploaded to NEW queue.

another two is:
- https://android.googlesource.com/platform/external/avb
- https://android.googlesource.com/platform/system/vold

Hope we can still catch up with bullseye...

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

Bug#977906: marked as done (libcollada-parser1d: missing Breaks+Replaces: libcollada-parser-dev (<< 1.12.13-2))

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 18:04:21 +
with message-id 
and subject line Bug#977906: fixed in ros-collada-urdf 1.12.13-3
has caused the Debian Bug report #977906,
regarding libcollada-parser1d: missing Breaks+Replaces: libcollada-parser-dev 
(<< 1.12.13-2)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977906
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcollada-parser1d
Version: 1.12.13-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../libcollada-parser1d_1.12.13-2_amd64.deb ...
  Unpacking libcollada-parser1d:amd64 (1.12.13-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libcollada-parser1d_1.12.13-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/collada_parser/package.xml', which is also 
in package libcollada-parser-dev 1.12.6-5
  Errors were encountered while processing:
   /var/cache/apt/archives/libcollada-parser1d_1.12.13-2_amd64.deb


cheers,

Andreas


libcollada-parser-dev=1.12.6-5_libcollada-parser1d=1.12.13-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ros-collada-urdf
Source-Version: 1.12.13-3
Done: Jochen Sprickerhof 

We believe that the bug you reported is fixed in the latest version of
ros-collada-urdf, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated ros-collada-urdf 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 22 Dec 2020 18:51:02 +0100
Source: ros-collada-urdf
Architecture: source
Version: 1.12.13-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Closes: 977906
Changes:
 ros-collada-urdf (1.12.13-3) unstable; urgency=medium
 .
   * Add Breaks+Replaces for old libcollada-parser-dev.
 Thanks to Andreas Beckmann (Closes: #977906)
Checksums-Sha1:
 f147fe71b59f29c9f2a1ad5d8d13d14833853e9d 2598 ros-collada-urdf_1.12.13-3.dsc
 0a18c29732ab6e47f51e89fb8dc74c712ccacdfb 3824 
ros-collada-urdf_1.12.13-3.debian.tar.xz
 0e52252339d9a8132684dd2b88566f70be4ada81 9244 
ros-collada-urdf_1.12.13-3_source.buildinfo
Checksums-Sha256:
 962096477a27e85af71fd6257dffcec587d07ec4f7667dc48d7226a05efa053b 2598 
ros-collada-urdf_1.12.13-3.dsc
 e8027f121c7ba73ee80006d6936e174130cc3f0db4c41a1fa56256851f1ab40d 3824 
ros-collada-urdf_1.12.13-3.debian.tar.xz
 ba89c644a97c91bc691b065c47128778d46ea9d637d3ab409e06876d56f44a3f 9244 
ros-collada-urdf_1.12.13-3_source.buildinfo
Files:
 8d02a131961318fa64c3992c7aed2623 2598 libs optional 
ros-collada-urdf_1.12.13-3.dsc
 0826f437365ac51f72f908a9eaf767e7 3824 libs optional 
ros-collada-urdf_1.12.13-3.debian.tar.xz
 0d30b834719562d75e397e6d846a21ca 9244 libs optional 
ros-collada-urdf_1.12.13-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl/iMhAACgkQW//cwljm
lDPS3RAAke9/iXNz80I4b90RIwysThVG68kbz47pqqibpX3yY31ezYWSFck4dLjl
3hVZy7lT98y/shoyTogB/mw3/zjFgo//x1FrflhuccLjrZpQARDn4AazJumvmfbD
0Q0tU9zXSDe8FkXlGU0WPE3nykzzOO8kOFTWuvDu1/QXl5PAKEi0hioA9mpWSbkH
5CfH9HbfbNXm33cEH2RyCHwfHPnde6AqNMVUDiPMAfcV6ArRqi/ZTN4iObzsFDm0
YMSHZGik7AfrfqCiAss/vSIpc12ruKCrwgnepmNDLyLHTPaaIEx4c4KIbFr8gRze
E91SpAwZqaVkl2iDd94rJi4i8xtMgRoVsc4Ok/fxZkx5N7sZunXKOVAY0FiT9029
Rj4KUg28F/AXC9JoA+fY5SQYOH6nWTU3eoL6fBqKoLMDeE4NYmr9tEjC2/yOPsnr
Usu6M0JncZyrsohoy/g4tZhc7fWY4Q22yNBbOCsJkEVt4QmQx1u1LEfXFhvBlh2u

Bug#977905: marked as done (librosbag-storage4d: missing Breaks+Replaces: librosbag-storage-dev (<< 1.15.9+ds1-5))

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 18:04:26 +
with message-id 
and subject line Bug#977905: fixed in ros-ros-comm 1.15.9+ds1-6
has caused the Debian Bug report #977905,
regarding librosbag-storage4d: missing Breaks+Replaces: librosbag-storage-dev 
(<< 1.15.9+ds1-5)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librosbag-storage4d
Version: 1.15.9+ds1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../librosbag-storage4d_1.15.9+ds1-5_amd64.deb ...
  Unpacking librosbag-storage4d:amd64 (1.15.9+ds1-5) ...
  dpkg: error processing archive 
/var/cache/apt/archives/librosbag-storage4d_1.15.9+ds1-5_amd64.deb (--unpack):
   trying to overwrite '/usr/share/rosbag_storage/encryptor_plugins.xml', which 
is also in package librosbag-storage-dev:amd64 1.14.3+ds1-5+deb10u2
  Errors were encountered while processing:
   /var/cache/apt/archives/librosbag-storage4d_1.15.9+ds1-5_amd64.deb


cheers,

Andreas


librosbag-storage-dev=1.14.3+ds1-5+deb10u2_librosbag-storage4d=1.15.9+ds1-5.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ros-ros-comm
Source-Version: 1.15.9+ds1-6
Done: Jochen Sprickerhof 

We believe that the bug you reported is fixed in the latest version of
ros-ros-comm, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated ros-ros-comm 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 22 Dec 2020 18:44:09 +0100
Source: ros-ros-comm
Architecture: source
Version: 1.15.9+ds1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Closes: 977905
Changes:
 ros-ros-comm (1.15.9+ds1-6) unstable; urgency=medium
 .
   * Add Breaks+Replaces for old librosbag-storage-dev.
 Thanks to Andreas Beckmann (Closes: #977905)
Checksums-Sha1:
 98a9b020066f2c019092cbcafa1c226002b306e4 4943 ros-ros-comm_1.15.9+ds1-6.dsc
 a489d7890a1cf2b6340b1451b9f9876b9967881e 18040 
ros-ros-comm_1.15.9+ds1-6.debian.tar.xz
 ece1109dcd3b05cf02ab6910486e99c2374d11d8 9874 
ros-ros-comm_1.15.9+ds1-6_source.buildinfo
Checksums-Sha256:
 03c20e0e4060b79c2e0fa925183cfc787dd22869893bb03d7dfe4bdac25e85f0 4943 
ros-ros-comm_1.15.9+ds1-6.dsc
 b8012b48f0596a4e2286f44f3ab8bd6346593dd304a3cc7ad3dcde9d1eb46252 18040 
ros-ros-comm_1.15.9+ds1-6.debian.tar.xz
 9a405b73852ae59955b0de0f10309777df7939f9a8136c8459e277c781aab19b 9874 
ros-ros-comm_1.15.9+ds1-6_source.buildinfo
Files:
 908351a06589ae1e5840a78ea61069ff 4943 libs optional 
ros-ros-comm_1.15.9+ds1-6.dsc
 bf31796f8e00180267c90b576b0efc45 18040 libs optional 
ros-ros-comm_1.15.9+ds1-6.debian.tar.xz
 5920ec5e33e0285c848059c344981c78 9874 libs optional 
ros-ros-comm_1.15.9+ds1-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl/iMIMACgkQW//cwljm
lDO+IRAAjuiM46s6SFDQklH5i4UvcS+UA5+hWE/nTCbDaNct0oNmJ+waxRTZpbgD
NTmGrGw8QJ9VdypQ/WrUG7NHrgkSZnrzmbvPSioIBZLtzpmwH83pgSWlbFp/7Jjc
MePL+4eWuDE05aREZAvX8nsaHaTMfpV0omqDByQ7ZcW0fPgukKtC3DbJO1SPkg59
xK64ldCvwT/Dg2QvdtbNrZXg1Xm1eoloFUDjuOs/Ks2EFWDXxmrOZnJo7J1YHmjX
/0vR/mhkhsxsoKfU+hdetHfc4K95N884r8Ho2gxlYOeNyfX7txZ1QBDW7iekyZhZ
FDae7gT168+Dqj+dDs3T41j13a9AlTQ2oCNEbAH6N9Tge4Ac/cvfcGWlEF32hXNy
mATwCXgWpxD38Gh6Pdzpb4Kixy2FOLcJMCXgsWeuDlJY9EYaUipwCMAWJjFd5VjV

Bug#959905: marked as done (ydotool: FTBFS: relocation R_X86_64_PC32 against symbol `_ZTISt13runtime_error@@GLIBCXX_3.4' can not be used when making a shared object; recompile with -fPIC)

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 18:04:37 +
with message-id 
and subject line Bug#959905: fixed in ydotool 0.1.8-3
has caused the Debian Bug report #959905,
regarding ydotool: FTBFS: relocation R_X86_64_PC32 against symbol 
`_ZTISt13runtime_error@@GLIBCXX_3.4' can not be used when making a shared 
object; recompile with -fPIC
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
959905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ydotool
Version: 0.1.8-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source

While rebuilding on buildd, ydotool failed to build:
https://buildd.debian.org/status/fetch.php?pkg=ydotool=amd64=0.1.8-2%2Bb1=1588761426=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ydotool
Source-Version: 0.1.8-3
Done: Alexandre Viau 

We believe that the bug you reported is fixed in the latest version of
ydotool, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 959...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexandre Viau  (supplier of updated ydotool package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 22 Dec 2020 12:53:31 -0500
Source: ydotool
Architecture: source
Version: 0.1.8-3
Distribution: unstable
Urgency: medium
Maintainer: Alexandre Viau 
Changed-By: Alexandre Viau 
Closes: 959905
Changes:
 ydotool (0.1.8-3) unstable; urgency=medium
 .
   * d/control: Rules-Requires-Root: no.
   * depend on livevdevplus >= 0.1.1-2. (Closes: #959905)
   * d/rules: -DCMAKE_POSITION_INDEPENDENT_CODE=ON.
Checksums-Sha1:
 993e437d7a2cdb3e0e42083bddde402b7f161105 1962 ydotool_0.1.8-3.dsc
 af579448ccdc815b5652771fe87a512151b049ce 2768 ydotool_0.1.8-3.debian.tar.xz
 2fa86198f60f3a5419e4ba19ae152cce18bdf850 7975 ydotool_0.1.8-3_source.buildinfo
Checksums-Sha256:
 58713a008bcbfe4bfe1e9403074be3fadc69429abd5a7766815c806e59e41f48 1962 
ydotool_0.1.8-3.dsc
 4912af797bff6f4151766d73789552a4c21d9d22ce021b55cfe0ad89de03b870 2768 
ydotool_0.1.8-3.debian.tar.xz
 a25a64d3fe932916c4181faa5370d64ec2bdcc58a2c35a5da559704d1efbbc31 7975 
ydotool_0.1.8-3_source.buildinfo
Files:
 c5594fe7d3616ba3e66e34648f4f554d 1962 utils optional ydotool_0.1.8-3.dsc
 01383bafc12ccfe4e5849daa5ba08249 2768 utils optional 
ydotool_0.1.8-3.debian.tar.xz
 ba4710bb822aeecb97bb4d14f0333e5f 7975 utils optional 
ydotool_0.1.8-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEB0B3ii38SjnAyLyMjysRPGU1xacFAl/iMrEACgkQjysRPGU1
xae7Aw/5AeyleekeIBSWLq9GpNu9qv8SkKgGAKIHMEpvyyH9tDaVrdTNO0PdTWjD
aMe9DaPTIup8Mj6+I3/Z/FwH7o2dXrSoGECS6oRkaDahDNuK91UBLm1W1TkzHHwl
9k9A6N7MJmcjBcCnYau94RMevcUKU7DeeeFXP7ah1XriWoigHXE2+MWTKLMyExWx
s/BV/mYcdx4PWudgwd4372bf1tw5IbDZgzsM9/rfzvhNKiExwu9QBwudzVlz7bGC
XhNXoPEN/Qa30hHTYqE+pw5q7R29mYEw/tKdCiOjI5794Ya63kWFuFTCAo6Cs3/i
iFL3asQj/oJI2NHMJgGE9JZtHMqyeNdUwMmqUr4eYHEinlV2/AVIVgQPz5B84HuB
6Bh3V0b81Q6mxokvOIwsXr6ySzeiGwKqTXAVw+jQPuBhc45O0ABs5eC5pnLDHtq3
EoPIM/d72XIb9DzDL64rksyw2BUVw5zOhhuzbUbwPDi0mfU250B3zVXjbyWihAsR
BjU++Uh/kfAnki502L6ygWkmQFKo225/km27DZVr3wFAnmwpWwqQrHKob2oyd0pz
++b2XnqPr6VzQhik35kY1OhBhLv3qU5HjfgjqtpZYo9sixKTO+9mYNORGylMfa4R
+eaytTfRuTyzJ/qA+G4bMlv0wGZ7IbauCf/4L0kFwLIAFWKFdfE=
=UQtr
-END PGP SIGNATURE End Message ---

Bug#977908: mk-configure: Fails with 'Settings for gcc-10.2.1 is not available'

[Robert Luberda]

Package: mk-configure
Version: 0.35.0-1
Severity: serious
Justification: causes FTBFS of libmaa


It looks like mk-configure fails to recognize gcc-10.2.1 (which migrated
to testing almost a week ago), what causes my libmaa package to FTBFS, see:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libmaa.html

   dh "binary" --buildsystem=mkcmake
   dh_update_autotools_config -O--buildsystem=mkcmake
   dh_autoreconf -O--buildsystem=mkcmake
   dh_auto_configure -O--buildsystem=mkcmake
   dh_auto_build -O--buildsystem=mkcmake
mkcmake PREFIX=/usr MANDIR=/usr/share/man INFODIR=/usr/share/info 
SYSCONFDIR=/etc STRIPFLAG= LIBDIR=/usr/lib/x86_64-linux-gnu 
LIBEXECDIR=/usr/lib/x86_64-linux-gnu
==
all ===> doc
==
all ===> maa
checking C compiler type... gcc 10.2.1
bmake[2]: "/usr/share/mk-configure/mk/mkc_imp.platform.sys.mk" line 112: 
'Settings for gcc-10.2.1 is not available, run "mkc_compiler_settings" utility'
*** Error code 1
dh_auto_build: error: mkcmake PREFIX=/usr MANDIR=/usr/share/man 
INFODIR=/usr/share/info SYSCONFDIR=/etc STRIPFLAG= 
LIBDIR=/usr/lib/x86_64-linux-gnu LIBEXECDIR=/usr/lib/x86_64-linux-gnu returned 
exit code 1
make: *** [debian/rules:12: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



Regards,
Robert

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


Versions of packages mk-configure depends on:
ii  bmake  20200710-5

Versions of packages mk-configure recommends:
ii  pkg-config  0.29.2-1

mk-configure suggests no packages.

-- no debconf information

Bug#977890: libcinnamon-menu-3-0: Upgrade 4.6.1-1->4.8.2-2 causes segfault when launching any application

[Julio C. Ortega]

Package: gir1.2-cmenu-3.0
Followup-For: Bug #977890

Dear Maintainer,

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

   * What led up to the situation?

Upgraded libcinnamon-menu-3-0 and gir1.2-cmenu-3.0 4.6.1-1->4.8.2-2 and
cinnamon-l10n from 4.6.2-1->4.8.2-2

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

Launching any application from menus, panel or link leds to segfault, this 
doesn't happen if the application is explicitly launched from the cinnamon 
quick launch prompt (alt+f2)

   * What was the outcome of this action?

Cinnamon crash and prompt to restart in safe mode

   * What outcome did you expect instead?

Normal application Launch


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

Kernel: Linux 5.9.0-4-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=es_CO.UTF-8, LC_CTYPE=es_CO.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 gir1.2-cmenu-3.0 depends on:
ii  libcinnamon-menu-3-0  4.6.1-1

gir1.2-cmenu-3.0 recommends no packages.

gir1.2-cmenu-3.0 suggests no packages.

-- no debconf information

Bug#977906: libcollada-parser1d: missing Breaks+Replaces: libcollada-parser-dev (<< 1.12.13-2)

[Andreas Beckmann]

Package: libcollada-parser1d
Version: 1.12.13-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../libcollada-parser1d_1.12.13-2_amd64.deb ...
  Unpacking libcollada-parser1d:amd64 (1.12.13-2) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libcollada-parser1d_1.12.13-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/collada_parser/package.xml', which is also 
in package libcollada-parser-dev 1.12.6-5
  Errors were encountered while processing:
   /var/cache/apt/archives/libcollada-parser1d_1.12.13-2_amd64.deb


cheers,

Andreas


libcollada-parser-dev=1.12.6-5_libcollada-parser1d=1.12.13-2.log.gz
Description: application/gzip

Bug#975372: minidlna: "rm: cannot remove '/var/log/minidlna': Is a directory" on purge

[Alexander Gerasiov]

On Sun, 20 Dec 2020 11:50:42 +0200
Adrian Bunk  wrote:
> this is a regression in 1.2.1+dfsg-2 that is currently in both 
> buster-security (which was done on top of 1.2.1+dfsg-2 that
> introduced the regression, not on top of 1.2.1+dfsg-1 in buster) and
> in unstable/testing (which currently misses the CVE fixes).
> 
> It would be good if you could make an upload to unstable with this
> bug fixed on top of 1.2.1+dfsg-2+deb10u1, and then backport that
> change to buster.
> 
> Please coordinate with the security team whether this would warrant a 
> regression update to the DSA or should be done through the next point 
> release.

Hi, Team.

Does anyone mind against uploading fix to stable-proposed-update?
The fix is here:
https://salsa.debian.org/debian/minidlna/-/commits/buster-security/
Or should it go to buster-security?


Also uploaded to unstable as 1.2.1+dfsg-3

-- 
Best regards,
 Alexander Gerasiov

 Contacts:
 e-mail: a...@gerasiov.net  WWW: https://gerasiov.net  TG/Skype: gerasiov
 PGP fingerprint: 04B5 9D90 DF7C C2AB CD49  BAEA CA87 E9E8 2AAC 33F1

Bug#977905: librosbag-storage4d: missing Breaks+Replaces: librosbag-storage-dev (<< 1.15.9+ds1-5)

[Andreas Beckmann]

Package: librosbag-storage4d
Version: 1.15.9+ds1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../librosbag-storage4d_1.15.9+ds1-5_amd64.deb ...
  Unpacking librosbag-storage4d:amd64 (1.15.9+ds1-5) ...
  dpkg: error processing archive 
/var/cache/apt/archives/librosbag-storage4d_1.15.9+ds1-5_amd64.deb (--unpack):
   trying to overwrite '/usr/share/rosbag_storage/encryptor_plugins.xml', which 
is also in package librosbag-storage-dev:amd64 1.14.3+ds1-5+deb10u2
  Errors were encountered while processing:
   /var/cache/apt/archives/librosbag-storage4d_1.15.9+ds1-5_amd64.deb


cheers,

Andreas


librosbag-storage-dev=1.14.3+ds1-5+deb10u2_librosbag-storage4d=1.15.9+ds1-5.log.gz
Description: application/gzip

Processed: exaggerated severity and not a bug

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 977603 normal
Bug #977603 [g++-10] cc1plus: internal compiler error: in cpp_diagnostic_at, at 
libcpp/errors.c:41
Severity set to 'normal' from 'grave'
> close 977603
Bug #977603 [g++-10] cc1plus: internal compiler error: in cpp_diagnostic_at, at 
libcpp/errors.c:41
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
977603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977603
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: [pkg-uWSGI-devel] Bug#969372: INFO: Bug#969372: uwsgi-emperor: SysV init script does nothing

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +help
Bug #969372 {Done: Jonas Smedegaard } [uwsgi-emperor] 
uwsgi-emperor: SysV init script does nothing
Added tag(s) help.

-- 
969372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#969372: [pkg-uWSGI-devel] Bug#969372: INFO: Bug#969372: uwsgi-emperor: SysV init script does nothing

[Jonas Smedegaard]

Control: tags -1 +help

Quoting Rens Houben (2020-12-22 10:07:00)
> The issue arose because the init script isn't so much a script as it's 
> a set of variables plugged into the init.d helper scripts, and /those/ 
> have changed drastically from Jessie to Buster and onwards to call 
> systemctl -- but in uwsgi-emperor's case there doesn't appear to /be/ 
> a systemd service file to call on, so it quietly fails and does 
> nothing at all.
> 
> I'm currently writing at least a rudimentary systemd service file for 
> uwsgi-emperor to see if that makes it work; I can share it once I 
> finish if you'd like.

That would be quite helpful indeed.

  - 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#969372: INFO: Bug#969372: uwsgi-emperor: SysV init script does nothing

[Thomas Goirand]

On 12/22/20 10:07 AM, Rens Houben wrote:
> I'm currently writing at least a rudimentary systemd service file for
> uwsgi-emperor to see if that makes it work; I can share it once I finish
> if you'd like.
> 
> --Rens Houben.

Hi Rens,

Thanks for your reply and sharing of your investigations.

Very much, sharing your .service file would be helpful. None of the
UWSGI maintainers are currently using the emperor mode.

Cheers,

Thomas Goirand (zigo)

Bug#977900: node-autoprefixer: FTBFS: ENOENT: no such file or directory, open 'path'

[Andreas Beckmann]

Source: node-autoprefixer
Version: 10.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

node-autoprefixer/experimental recently started to FTBFS:

 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure --buildsystem=nodejs
mkdir node_modules
ln -s ../colorette node_modules/colorette
ln -s ../num2fraction node_modules/num2fraction
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/node-autoprefixer-10.0.0'
rollup --config debian/rollup.config.js

debian/autoprefixer.js → dist/autoprefixer.js...
[!] Error: Could not load path (imported by 
../../usr/share/nodejs/postcss/lib/map-generator.js): ENOENT: no such file or 
directory, open 'path'
Error: Could not load path (imported by 
../../usr/share/nodejs/postcss/lib/map-generator.js): ENOENT: no such file or 
directory, open 'path'

make[1]: *** [debian/rules:14: override_dh_auto_build] Error 1
make[1]: Leaving directory '/build/node-autoprefixer-10.0.0'
make: *** [debian/rules:11: binary] Error 2

A previous build on Oct 28 has been successful, so this current failure is 
probably
caused by some updated (transitive) build-depends.


Andreas


node-autoprefixer_10.0.0-1.log.gz
Description: application/gzip

Processed: block 976886 with 977898

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 976886 with 977898
Bug #976886 [movim] movim: Blocking transition of php-illuminate-database
976886 was not blocked by any bugs.
976886 was not blocking any bugs.
Added blocking bug(s) of 976886: 977898
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
976886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#977868: marked as done (osmcoastline: FTBFS in bullseye and sid)

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 14:39:53 +
with message-id 
and subject line Bug#977868: fixed in osmcoastline 2.2.4-3
has caused the Debian Bug report #977868,
regarding osmcoastline: FTBFS in bullseye and sid
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osmcoastline
Version: 2.2.4-2
Severity: serious
Tags: ftbfs bullseye sid

Hi Maintainer

As per Reproducible Builds [1], osmcoastline FTBFS in bullseye and sid.
I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/osmcoastline.html


 1/19 Test  #1: test-invalid-complex-overlap
.***Failed0.29 sec
+ cat
+ /build/1st/osmcoastline-2.2.4/obj-x86_64-linux-gnu/src/osmcoastline
--verbose --overwrite
--output-database=/build/1st/osmcoastline-2.2.4/obj-x86_64-linux-gnu/test/invalid-complex-overlap.db
/build/1st/osmcoastline-2.2.4/obj-x86_64-linux-gnu/test/invalid-complex-overlap.opl
+ RC=139
+ set -e
+ test 139 -eq 2

  Start 17: test-valid-island-from-one-way
 2/19 Test  #6: test-invalid-node-with-coastline-tag
.   Passed0.49 sec
  Start 18: test-valid-island-from-two-ways
 3/19 Test #13: test-usage-and-help
..   Passed0.44 sec
  Start 19: test-valid-two-small-islands
 4/19 Test  #4: test-invalid-duplicate-segments-2
   Passed0.51 sec
 5/19 Test  #7: test-invalid-part-reversed
...   Passed0.50 sec
 6/19 Test  #2: test-invalid-direction
...   Passed0.53 sec
 7/19 Test  #9: test-invalid-self-intersection-on-closed-ring-one-way
   Passed0.53 sec
 8/19 Test #10: test-invalid-self-intersection-on-closed-ring-two-ways
...   Passed0.59 sec
 9/19 Test  #3: test-invalid-duplicate-segments-1
   Passed0.63 sec
10/19 Test  #5: test-invalid-node-id-mismatch
   Passed0.63 sec
11/19 Test #12: test-overlapping-islands
.   Passed0.60 sec
12/19 Test #15: test-valid-inline-sea-with-island
   Passed0.64 sec
13/19 Test #14: test-valid-antimeridian
..   Passed0.70 sec
14/19 Test #16: test-valid-inline-sea
   Passed0.68 sec
15/19 Test #17: test-valid-island-from-one-way
...   Passed0.50 sec
16/19 Test #11: test-invalid-self-intersection-on-open-ring
..   Passed0.77 sec
17/19 Test #18: test-valid-island-from-two-ways
..   Passed0.45 sec
18/19 Test #19: test-valid-two-small-islands
.   Passed0.45 sec
19/19 Test  #8: test-invalid-ring-not-closed
.   Passed1.12 sec

95% tests passed, 1 tests failed out of 19

Total Test time (real) =   1.14 sec

The following tests FAILED:
 1 - test-invalid-complex-overlap (Failed)
Errors while running CTest
--- End Message ---
--- Begin Message ---
Source: osmcoastline
Source-Version: 2.2.4-3
Done: Bas Couwenberg 

We believe that the bug you reported is fixed in the latest version of
osmcoastline, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated osmcoastline package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 22 Dec 2020 14:58:28 +0100
Source: osmcoastline
Architecture: source
Version: 2.2.4-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 977868
Changes:
 osmcoastline (2.2.4-3) unstable; urgency=medium
 .
   * Bump watch file version to 4.
   * Bump Standards-Version to 4.5.1, no changes.
   * Add upstream patch to fix test-invalid-complex-overlap failure.
 (closes: #977868)
Checksums-Sha1:
 d3a3106d71830ab677bd0eb8dbb8b0321a151f44 

Bug#977890: marked as done (libcinnamon-menu-3-0: Upgrade 4.6.1-1->4.8.2-2 causes segfault when launching any application)

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 14:36:01 +
with message-id 
and subject line Bug#977890: fixed in cinnamon-menus 4.8.2-3
has caused the Debian Bug report #977890,
regarding libcinnamon-menu-3-0: Upgrade 4.6.1-1->4.8.2-2 causes segfault when 
launching any application
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcinnamon-menu-3-0
Version: 4.8.2-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?

Upgraded libcinnamon-menu-3-0 and gir1.2-cmenu-3.0 4.6.1-1->4.8.2-2 and
cinnamon-l10n from 4.6.2-1->4.8.2-2

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

Tried to launch any application from the menus or panel launcher buttons.

   * What was the outcome of this action?

cinnamon segfaulted with casting error, I assume because not all of cinnamon
upgraded.

   * What outcome did you expect instead?

That cinnamon launched the applications with no problem

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



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

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

Versions of packages libcinnamon-menu-3-0 depends on:
ii  libc6 2.31-5
ii  libglib2.0-0  2.66.3-2

libcinnamon-menu-3-0 recommends no packages.

libcinnamon-menu-3-0 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cinnamon-menus
Source-Version: 4.8.2-3
Done: Fabio Fantoni 

We believe that the bug you reported is fixed in the latest version of
cinnamon-menus, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Fabio Fantoni  (supplier of updated cinnamon-menus 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 22 Dec 2020 14:34:48 +0100
Source: cinnamon-menus
Architecture: source
Version: 4.8.2-3
Distribution: unstable
Urgency: high
Maintainer: Debian Cinnamon Team 
Changed-By: Fabio Fantoni 
Closes: 977890
Changes:
 cinnamon-menus (4.8.2-3) unstable; urgency=high
 .
   * Dump cinnamon breaks version to 4.8 (Closes: #977890)
Checksums-Sha1:
 74115a7cfc9d4af4a309be2c8b45150c50e21250 2077 cinnamon-menus_4.8.2-3.dsc
 42542ca5887e73d5b60f28cbeefdf3a34f587948 4996 
cinnamon-menus_4.8.2-3.debian.tar.xz
 a107ce4bad85673a5d2d17b0d9625d2eb16464df 9083 
cinnamon-menus_4.8.2-3_source.buildinfo
Checksums-Sha256:
 eec2f90c857e9b0b80e049000ca3351a642a848c7fde7bdf03d1356ec0f047fd 2077 
cinnamon-menus_4.8.2-3.dsc
 c2fecf5953f7c1bd34b7885d4adf334140b218c63e4caca32f11a9d3cfc346cc 4996 
cinnamon-menus_4.8.2-3.debian.tar.xz
 2151b27f7fc83ab64b94276f3ff7f45287dc647c2e032cc585ac9b30ea90e824 9083 
cinnamon-menus_4.8.2-3_source.buildinfo
Files:
 73f3811d3a12fb0365ee35ce3ab11ab0 2077 x11 optional cinnamon-menus_4.8.2-3.dsc
 6faef4da8c6a8777563c0be43c87d3e0 4996 x11 optional 
cinnamon-menus_4.8.2-3.debian.tar.xz
 e3cda19dcd8ea3c7270f909bdb5327fc 9083 x11 optional 
cinnamon-menus_4.8.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE68ws0vrA2voQX53I2A4JsIcUAGYFAl/h/fIACgkQ2A4JsIcU
AGYojAgAtz4yWVaW+VTVOkNwzBBQiAbo5tRlWM+UZfHFNdlamW+P/KSM2kBgN/oM
/6itB1fSfH+j0OI3CzUtEY4XGm/kcgI610H/W3pMQ1gYGvQB3gBTGkUfszziwZxa
ahqQ6k79wiCsgQJDvEmp2jrqt+Uj6tppHZdVDjGfyNjtFDo6t7sVXHIr3w+vhM2J
ooc9T0lUSBvTVt094k/XOrt7/eMAIGpjmax4AaQLDF6uDCnTC1ebj783UxRMeVvK
y8FFqKjIidbptXFDEFESDbb6oMY4+D7a2dEg2flYUxx9hIwNaYcl5CcpboMm+EQz
XOU1Zs97A5z1Uz0fMpBl06aIPsDD3A==
=F06X
-END PGP SIGNATURE End 

Bug#977461: marked as done (gcc-1[01]-offload-amdgcn,gcc-1[01]-hppa64-linux-gnu: shipping unversioned binaries causes file conflicts)

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 14:37:32 +
with message-id 
and subject line Bug#977461: fixed in gcc-10 10.2.1-2
has caused the Debian Bug report #977461,
regarding gcc-1[01]-offload-amdgcn,gcc-1[01]-hppa64-linux-gnu: shipping 
unversioned binaries causes file conflicts
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: 
gcc-10-offload-amdgcn,gcc-11-offload-amdgcn,gcc-10-hppa64-linux-gnu,gcc-11-hppa64-linux-gnu
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 10.2.1-1
Control: found -1 11-20201208-1

Hi,

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

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

  Preparing to unpack .../gcc-11-offload-amdgcn_11-20201208-1_amd64.deb ...
  Unpacking gcc-11-offload-amdgcn (11-20201208-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/gcc-11-offload-amdgcn_11-20201208-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/amdgcn-amdhsa/bin/ar', which is also in package 
gcc-10-offload-amdgcn 10.2.1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/gcc-11-offload-amdgcn_11-20201208-1_amd64.deb

These unversioned files are in conflict between the gcc versions:

usr/amdgcn-amdhsa/bin/ar
usr/amdgcn-amdhsa/bin/as
usr/amdgcn-amdhsa/bin/ld
usr/amdgcn-amdhsa/bin/nm
usr/amdgcn-amdhsa/bin/ranlib

usr/bin/hppa64-linux-gnu-lto-dump

Maybe the unversioned binaries should be managed by unversioned packages
from gcc-defaults instead.

cheers,

Andreas


gcc-10-offload-amdgcn=10.2.1-1_gcc-11-offload-amdgcn=11-20201208-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gcc-10
Source-Version: 10.2.1-2
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
gcc-10, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated gcc-10 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 22 Dec 2020 14:54:57 +0100
Source: gcc-10
Architecture: source
Version: 10.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Matthias Klose 
Closes: 977461
Changes:
 gcc-10 (10.2.1-2) unstable; urgency=medium
 .
   * Update to git 20201221 from the gcc-10 branch.
 - Fix PR rtl-optimization/97092, PR ada/98230, PR c++/64194, PR d/98277,
   PR fortran/98307.
   * For the gcn offload compiler, use a version fixing LLVM Bug 48201.
   * Don't install the lto-dump binary in the hppa64 package. Closes: #977461.
   * Refresh patches.
   * Strip compiler executables again.
Checksums-Sha1:
 ca340f8fa103e7b3b72fd1bce2c2ce7f81b98d3c 27667 gcc-10_10.2.1-2.dsc
 20fd89939a2fef062ed7c33a06aeee019da0cf6d 2311044 gcc-10_10.2.1-2.debian.tar.xz
 b24a3ee5b9cd6d34c5618bbc4f8e83589b077274 9346 gcc-10_10.2.1-2_source.buildinfo
Checksums-Sha256:
 efa99b93207e68215814fe955841e8954196f37e3bacc608772944573aef5a1b 27667 
gcc-10_10.2.1-2.dsc
 404109cfccfc23ae078fa3ca0cfde89636773399e60b86bc59482c60f32a9878 2311044 
gcc-10_10.2.1-2.debian.tar.xz
 87c3fb97d594502c7ff81651df81f33d325d31bb08bfc0c9e6cd7e609024c115 9346 
gcc-10_10.2.1-2_source.buildinfo
Files:
 c6352ba15b9c4fc395c2f2a0a7a76a88 27667 devel optional gcc-10_10.2.1-2.dsc
 b4f275ef16bac204480a68982910993a 2311044 devel optional 
gcc-10_10.2.1-2.debian.tar.xz
 a573e18a1867e1a855272b917414d2cb 9346 devel optional 
gcc-10_10.2.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAl/h/0cQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9e9FD/9fFbSi28N8sKqIIY6gkJ0MbZBiDlInQhy5
/Hfggn+uAzuVXxAJLQX8fPQ5hfQmH8nPJLySB0cPNSLETp6A4VlKFbdTr+3XnSwq
8UNDwmCTtJcEvwgxj+pCuipIUyRV4cCLairwmOdatsfkikGUEzQ2HIbvF4DBYYMX
E+/r3jhVMoJ3wkGvWgaMBJgGRnRA+NrbGMLytHWl+mCHWrCPuo3xLK/iaQI2LMe2

Processed: movim: diff for NMU version 0.17.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 976886 + patch
Bug #976886 [movim] movim: Blocking transition of php-illuminate-database
Ignoring request to alter tags of bug #976886 to the same tags previously set
> tags 976886 + pending
Bug #976886 [movim] movim: Blocking transition of php-illuminate-database
Added tag(s) pending.

-- 
976886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#977762: Bug#967027: cinnamon: uses libcroco which is unmaintained upstream

[Norbert Preining]

Hi Fabio,

I saw your commit. I will do the upload in a minute. Thanks.

> @Norbert: unfortunately it is not just a problem of  cinnamon not
> installable in testing for a few days, the outdated breaks in
> cinnamon-menus cause serious problems to all those who have installed
> and updated it :(

--
PREINING Norbert  https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#977864: fixed in twitter-bootstrap4 4.5.2+dfsg1-4

[Petter Reinholdtsen]

[Xavier]
> it is normal to find this issue in version 4.5.2+dfsg1-3 since it has
> been fixed in 4.5.2+dfsg1-4!

Ah, sorry for the misunderstanding.  I assumed the version I was
upgrading to was the latest upload in unstable, and did not notice the
versions were different.  It upgraded just fine today. :)

-- 
Happy hacking
Petter Reinholdtsen

Bug#977762: Bug#967027: cinnamon: uses libcroco which is unmaintained upstream

[Fabio Fantoni]

Il 21/12/2020 10:17, Norbert Preining ha scritto:
> On Mon, 21 Dec 2020, Fabio Fantoni wrote:
>> @Norbert: thanks, unfortunately the migration to testing of some
>> components has begun and having made a further upload of cinnamon (with
>> medium urgency) will block the completion for another 5 days
> Well, so let testing be broken for a few days. That is the least of my
> concern.

@Norbert: unfortunately it is not just a problem of  cinnamon not
installable in testing for a few days, the outdated breaks in
cinnamon-menus cause serious problems to all those who have installed
and updated it :(

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977890 (already
reported by 2 users)

commit prepared if you want uploaded:
https://salsa.debian.org/cinnamon-team/cinnamon-menus/-/commit/51f33421f7e1de6b575159122ca06b5cbe9ae7fe

I also added the break in cinnamon-translation to avoid other minor
issues (if you want upload it):
https://salsa.debian.org/cinnamon-team/cinnamon-translations/-/commit/b10b116a87ca33a9b3f93ab4b3af72324be11a0f

>
> Best
>
> Norbert
>
> --
> PREINING Norbert  https://www.preining.info
> Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
> GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#977890: marked as pending in cinnamon-menus

[Fabio Fantoni]

Control: tag -1 pending

Hello,

Bug #977890 in cinnamon-menus reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/cinnamon-team/cinnamon-menus/-/commit/51f33421f7e1de6b575159122ca06b5cbe9ae7fe


Dump cinnamon breaks version to 4.8

Closes: #977890


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/977890

Processed: Bug#977890 marked as pending in cinnamon-menus

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #977890 [libcinnamon-menu-3-0] libcinnamon-menu-3-0: Upgrade 
4.6.1-1->4.8.2-2 causes segfault when launching any application
Added tag(s) pending.

-- 
977890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#977397: marked as done (uim-el: missing *-uim in input-method-alist on Emacs 27)

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 13:38:54 +
with message-id 
and subject line Bug#977397: fixed in uim 1:1.8.8-7
has caused the Debian Bug report #977397,
regarding uim-el: missing *-uim in input-method-alist on Emacs 27
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: uim-el
Version: 1:1.8.8-6.1+b2
Severity: grave
Justification: renders package unusable
Tags: patch

Dear Maintainer,

I used the japanese-anthy-utf8-uim input-method on my Debian Emacs 26 env.
But after upgrading Emacs 27,
I cannot set input-method to japanese-anthy-utf8-uim.

(Same cause as #977257)

There is a problem at initializing uim-el.
So none of the input methods *-uim are prepared on startup.

>From *Message* buffer:
>Error while loading 50uim-el: Symbol’s function definition is void: 
>process-kill-without-query


How to fix:

Replace process-kill-without-query with set-process-query-on-exit-flag
in /usr/share/emacs/site-lisp/uim-el/*.el .
This patch fixes this problem.
- Begin
--- uim-1.8.8.orig/emacs/uim-helper.el
+++ uim-1.8.8/emacs/uim-helper.el
@@ -106,7 +106,7 @@
 (if (not proc)
 (error "uim.el: Couldn't invoke uim-el-helper-agent."))

-(process-kill-without-query proc)
+(set-process-query-on-exit-flag proc nil)

 ;; wait "OK"
 (let ((patience uim-startup-timeout) (ok nil))
--- uim-1.8.8.orig/emacs/uim.el
+++ uim-1.8.8/emacs/uim.el
@@ -488,7 +488,7 @@
 (error "uim.el: Couldn't invoke uim-el-agent."))

 ;; don't ask kill
-(process-kill-without-query proc)
+(set-process-query-on-exit-flag proc nil)

 ;; wait "OK"
 (let ((patience uim-startup-timeout) (ok nil))
- End


Regards,
Nobuhiro Ban




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

Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.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 uim-el depends on:
ii  emacs1:27.1+1-3
ii  emacs-gtk [emacsen]  1:27.1+1-3
ii  libc62.31-5
ii  libuim8  1:1.8.8-6.1+b2
ii  uim  1:1.8.8-6.1+b2
ii  uim-data 1:1.8.8-6.1

uim-el recommends no packages.

uim-el suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: uim
Source-Version: 1:1.8.8-7
Done: HIGUCHI Daisuke (VDR dai) 

We believe that the bug you reported is fixed in the latest version of
uim, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
HIGUCHI Daisuke (VDR dai)  (supplier of updated uim package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 22 Dec 2020 21:07:53 +0900
Source: uim
Architecture: source
Version: 1:1.8.8-7
Distribution: unstable
Urgency: medium
Maintainer: HIGUCHI Daisuke (VDR dai) 
Changed-By: HIGUCHI Daisuke (VDR dai) 
Closes: 953616 973459 977257 977397
Changes:
 uim (1:1.8.8-7) unstable; urgency=medium
 .
   [ NOKUBI Takatsugu ]
   * d/p/disable-composer-test.patch: add the patch to skip composer-test.
 (Closes: #973459)
 .
   [ HIGUCHI Daisuke (VDR dai) ]
   * d/p/replace_obsolete_since_emacs22.1.patch: Replace
 process-kill-without-query with set-process-query-on-exit-flag
 (Closes: #977397, #977257)
   * resurrect anthy for EUC-JP (Closes: #953616)
Checksums-Sha1:
 be59bd6bb525afbfda8a970eb04882cf401e2f7a 3639 uim_1.8.8-7.dsc
 42acff27cadc4617ff92444af178b703b49c1850 38680 uim_1.8.8-7.debian.tar.xz
Checksums-Sha256:
 02f563fcf2f6c32f5646b07d4d74b16409f08f9202245dffa092f1a0757026ab 3639 
uim_1.8.8-7.dsc
 33887a28e60ede69add4d693c48dff1af52338e18a5d6d5b4b661b617fb0b3c5 38680 
uim_1.8.8-7.debian.tar.xz
Files:
 79b243e4fed4b9bcc9c4c112dfcc0891 

Bug#973459: marked as done (uim: FAIL: test-composer.scm)

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 13:38:54 +
with message-id 
and subject line Bug#973459: fixed in uim 1:1.8.8-7
has caused the Debian Bug report #973459,
regarding uim: FAIL: test-composer.scm
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
973459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uim
Version: 1:1.8.8-6.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

uim failed to build on armel:
| =
|uim 1.8.8: test2/test-suite.log
| =
|
| # TOTAL: 6
| # PASS:  4
| # SKIP:  0
| # XFAIL: 1
| # FAIL:  1
| # XPASS: 0
| # ERROR: 0
|
| .. contents:: :depth: 2
|
| FAIL: test-composer.scm
| ===
|
| Error: in define: bad definition form: (define Aborted
| FAIL test-composer.scm (exit status: 134)
|
| XFAIL: test-fail.scm
| 
|
| failed: unconditional failure #1
| FAILED: 1 tests, 1 assertions, 0 successes, 1 failures, 0 errors
| XFAIL test-fail.scm (exit status: 70)
|
| 
| Testsuite summary for uim 1.8.8
| 
| # TOTAL: 6
| # PASS:  4
| # SKIP:  0
| # XFAIL: 1
| # FAIL:  1
| # XPASS: 0
| # ERROR: 0
| 
| See test2/test-suite.log
| Please report to uim...@googlegroups.com
| 

See
https://buildd.debian.org/status/fetch.php?pkg=uim=armel=1%3A1.8.8-6.1%2Bb2=1604084554=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: uim
Source-Version: 1:1.8.8-7
Done: HIGUCHI Daisuke (VDR dai) 

We believe that the bug you reported is fixed in the latest version of
uim, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 973...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
HIGUCHI Daisuke (VDR dai)  (supplier of updated uim package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 22 Dec 2020 21:07:53 +0900
Source: uim
Architecture: source
Version: 1:1.8.8-7
Distribution: unstable
Urgency: medium
Maintainer: HIGUCHI Daisuke (VDR dai) 
Changed-By: HIGUCHI Daisuke (VDR dai) 
Closes: 953616 973459 977257 977397
Changes:
 uim (1:1.8.8-7) unstable; urgency=medium
 .
   [ NOKUBI Takatsugu ]
   * d/p/disable-composer-test.patch: add the patch to skip composer-test.
 (Closes: #973459)
 .
   [ HIGUCHI Daisuke (VDR dai) ]
   * d/p/replace_obsolete_since_emacs22.1.patch: Replace
 process-kill-without-query with set-process-query-on-exit-flag
 (Closes: #977397, #977257)
   * resurrect anthy for EUC-JP (Closes: #953616)
Checksums-Sha1:
 be59bd6bb525afbfda8a970eb04882cf401e2f7a 3639 uim_1.8.8-7.dsc
 42acff27cadc4617ff92444af178b703b49c1850 38680 uim_1.8.8-7.debian.tar.xz
Checksums-Sha256:
 02f563fcf2f6c32f5646b07d4d74b16409f08f9202245dffa092f1a0757026ab 3639 
uim_1.8.8-7.dsc
 33887a28e60ede69add4d693c48dff1af52338e18a5d6d5b4b661b617fb0b3c5 38680 
uim_1.8.8-7.debian.tar.xz
Files:
 79b243e4fed4b9bcc9c4c112dfcc0891 3639 libs optional uim_1.8.8-7.dsc
 280ce335c295c5a6231cb27f4f9897b0 38680 libs optional uim_1.8.8-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECynYjkLmt2W42OpQeDlhndQ5Zo4FAl/h8QIACgkQeDlhndQ5
Zo6VRA/9GYJ+9pPIAWg0olleY9KYRa1r7nBtxdqIkNNZ6RCtKfwgECvwL1hPbY/U
gDxKHx9+VEwiBpMtZ8NLpvfgR+yd++cz93XEGaoxZoPoYvt2gM3OcxIrbJQxcNJD
0NXHgN7LU8tbTsjCyHpmoM0XlUPsnddmXluef8Slau7oYJfpD+HlCU3ea/TA63IY
EeYMVUt10q62kQq+f7lzRXDCWBRDJdXUc7EeiPUr6HPBpwiD/+5IpMKoeM8Lr8vn
nDVVv3sFmcs0qA7efsh2tGngVm7CLrUbT8qFQV+gcowaUkVp6mZoxBjd6qZyvl8K
dKD8WhqVWlgvAsSljNEswNVgydinOmnwW91en2AiPyY9LMjlu8KtfBGBJNX9tQT9
qW1pPS8EoafhgThjm6zhZ8TaYOv9UsjAfkEKZCyblw9uEV0V974BqsTDEqaPLadB
g/dUBsWsm6Dk++aqa0b0xOar47sfaRf0Jxx+j0w49FlUKrEXdpSmx3OeC9/azW50

Bug#977833: marked as done (librelaxng-datatype-java: fails to build source package)

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 13:29:15 +
with message-id <20201222132915.ga3...@layer-acht.org>
and subject line Re: Bug#977856: librepository: fails to build source package
has caused the Debian Bug report #977833,
regarding librelaxng-datatype-java: fails to build source package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librelaxng-datatype-java
Version: 1.0+ds1-3
Severity: serious

Dear Maintainer,

I wanted to do a source only upload of librelaxng-datatype-java
(because there are no .buildinfo files for it in the archive, 
as it has been uploaded before 2016), but it fails to build
the source package. The binary package builds just fine.

Steps to reproduce:

$ apt source librelaxng-datatype-java
$ cd librelaxng-datatype-java-*
$ dpkg-buildpackage
dpkg-buildpackage: info: source package librelaxng-datatype-java
dpkg-buildpackage: info: source version 1.0+ds1-3
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Giovanni Mascellani 
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
 fakeroot debian/rules clean
dh clean --with maven-repo-helper
dh: warning: Compatibility levels before 10 are deprecated (level 7 in use)
   dh_auto_clean
dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 7 
in use)
ant clean
/usr/bin/java: error while loading shared libraries: libjli.so: cannot open 
shared object file: No such file or directory
dh_auto_clean: error: ant clean returned exit code 127
make: *** [debian/rules:8: clean] Error 255
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2
$

(This is with or without any changes to the source package.)


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁   holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
 ⠈⠳⣄

In Europe there are people prosecuted by courts because they saved other people
from drowning in the  Mediterranean Sea.  That is almost as absurd  as if there
were people being prosecuted because they save humans from drowning in the sea.


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi Tony,

On Mon, Dec 21, 2020 at 08:22:23PM -0800, tony mancill wrote:
> That's interesting.  It builds successfully for me in a clean sid chroot
> using sbuild.  libjli.so is part of the JRE, which is a dependency of
> default-jdk:

thanks for confirming it's no problem on your side, which made me think
what's different here: i've been using a chroot without /proc mounted.
With /proc mounted, the source packages build just fine, thus closing
these bug reports again.

> Do you mind sharing the output of `apt-cache policy default-jdk` and
> `dpkg -l | grep openjdk` on your build system?  I'm curious as to how
> the build dep for default-jdk can be satisfied without the file being
> present.
sure!

$ apt-cache policy default-jdk
default-jdk:
  Installed: 2:1.11-72
  Candidate: 2:1.11-72
  Version table:
 *** 2:1.11-72 500
500 http://deb.debian.org/debian sid/main amd64 Packages
100 /var/lib/dpkg/status
$ dpkg -l | grep openjdk
ii  openjdk-11-jdk:amd64  11.0.9.1+1-1
amd64OpenJDK Development Kit (JDK)
ii  openjdk-11-jdk-headless:amd64 11.0.9.1+1-1
amd64OpenJDK Development Kit (JDK) (headless)
ii  openjdk-11-jre:amd64  11.0.9.1+1-1
amd64OpenJDK Java runtime, using Hotspot JIT
ii  openjdk-11-jre-headless:amd64 11.0.9.1+1-1
amd64OpenJDK Java runtime, using Hotspot JIT (headless)

-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁   holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
 ⠈⠳⣄

“If the fires of 2020 horrify you, consider that, no matter what we do, by
 2050, when the benefits of even fast climate action will only begin to arrive,
 the area burned annually in the (US) West is expected to at least double and
 perhaps quadruple.” (David Wallace-Wells)


signature.asc
Description: PGP signature
--- End Message ---

Bug#977856: marked as done (librepository: fails to build source package)

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 13:29:15 +
with message-id <20201222132915.ga3...@layer-acht.org>
and subject line Re: Bug#977856: librepository: fails to build source package
has caused the Debian Bug report #977856,
regarding librepository: fails to build source package
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librepository
Version: 1.1.6-3
Severity: serious

Dear Maintainer,

I wanted to do a source only upload of librepository
(because there are no .buildinfo files for it in the archive,
as it has been uploaded before 2016), but it fails to build
the source package. The binary package builds just fine.

Steps to reproduce:

$ apt source librepository
$ cd librepository-*
$ dpkg-buildpackage
dpkg-buildpackage: info: source package librepository
dpkg-buildpackage: info: source version 1.1.6-3
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Emmanuel Bourg 
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
 fakeroot debian/rules clean
dh clean --with javahelper
   dh_auto_clean
ant -propertyfile ./debian/ant.properties clean
/usr/bin/java: error while loading shared libraries: libjli.so: cannot open 
shared object file: No such file or directory
dh_auto_clean: error: ant -propertyfile ./debian/ant.properties clean returned 
exit code 127
make: *** [debian/rules:6: clean] Error 127
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2
$

(This is with or without any changes to the source package.)


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁   holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
 ⠈⠳⣄

Some people say that the climate crisis  is something that we all have created,
but  that is not true,  because if everyone is guilty  then no one is to blame.
And someone is to blame.  Some people, some companies,  some decision-makers in
particular, have known exactly what priceless values they have been sacrificing
to continue making unimaginable amounts of money. (Greta Thunberg)


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi Tony,

On Mon, Dec 21, 2020 at 08:22:23PM -0800, tony mancill wrote:
> That's interesting.  It builds successfully for me in a clean sid chroot
> using sbuild.  libjli.so is part of the JRE, which is a dependency of
> default-jdk:

thanks for confirming it's no problem on your side, which made me think
what's different here: i've been using a chroot without /proc mounted.
With /proc mounted, the source packages build just fine, thus closing
these bug reports again.

> Do you mind sharing the output of `apt-cache policy default-jdk` and
> `dpkg -l | grep openjdk` on your build system?  I'm curious as to how
> the build dep for default-jdk can be satisfied without the file being
> present.
sure!

$ apt-cache policy default-jdk
default-jdk:
  Installed: 2:1.11-72
  Candidate: 2:1.11-72
  Version table:
 *** 2:1.11-72 500
500 http://deb.debian.org/debian sid/main amd64 Packages
100 /var/lib/dpkg/status
$ dpkg -l | grep openjdk
ii  openjdk-11-jdk:amd64  11.0.9.1+1-1
amd64OpenJDK Development Kit (JDK)
ii  openjdk-11-jdk-headless:amd64 11.0.9.1+1-1
amd64OpenJDK Development Kit (JDK) (headless)
ii  openjdk-11-jre:amd64  11.0.9.1+1-1
amd64OpenJDK Java runtime, using Hotspot JIT
ii  openjdk-11-jre-headless:amd64 11.0.9.1+1-1
amd64OpenJDK Java runtime, using Hotspot JIT (headless)

-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁   holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀ PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
 ⠈⠳⣄

“If the fires of 2020 horrify you, consider that, no matter what we do, by
 2050, when the benefits of even fast climate action will only begin to arrive,
 the area burned annually in the (US) West is expected to at least double and
 perhaps quadruple.” (David Wallace-Wells)


signature.asc
Description: PGP signature
--- End Message ---

Bug#977891: opencascade: library package names do not follow SOVERSION

[Andreas Beckmann]

Source: opencascade
Version: 7.5.0+dfsg1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../0-libocct-foundation-7.5_7.5.0+dfsg1-1_amd64.deb ...
  Unpacking libocct-foundation-7.5:amd64 (7.5.0+dfsg1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-ytPrh7/0-libocct-foundation-7.5_7.5.0+dfsg1-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libTKMath.so.7', which is 
also in package libocct-foundation-7.3:amd64 7.3.0+dfsg1-5
  Preparing to unpack .../1-libocct-modeling-data-7.5_7.5.0+dfsg1-1_amd64.deb 
...
  Unpacking libocct-modeling-data-7.5:amd64 (7.5.0+dfsg1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-ytPrh7/1-libocct-modeling-data-7.5_7.5.0+dfsg1-1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libTKBRep.so.7', which is 
also in package libocct-modeling-data-7.3:amd64 7.3.0+dfsg1-5
  Preparing to unpack 
.../2-libocct-modeling-algorithms-7.5_7.5.0+dfsg1-1_amd64.deb ...
  Unpacking libocct-modeling-algorithms-7.5:amd64 (7.5.0+dfsg1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-ytPrh7/2-libocct-modeling-algorithms-7.5_7.5.0+dfsg1-1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libTKBO.so.7', which is also 
in package libocct-modeling-algorithms-7.3:amd64 7.3.0+dfsg1-5
  Preparing to unpack .../3-libocct-visualization-7.5_7.5.0+dfsg1-1_amd64.deb 
...
  Unpacking libocct-visualization-7.5:amd64 (7.5.0+dfsg1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-ytPrh7/3-libocct-visualization-7.5_7.5.0+dfsg1-1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libTKMeshVS.so.7', which is 
also in package libocct-visualization-7.3:amd64 7.3.0+dfsg1-5
  Preparing to unpack .../4-libocct-ocaf-7.5_7.5.0+dfsg1-1_amd64.deb ...
  Unpacking libocct-ocaf-7.5:amd64 (7.5.0+dfsg1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-ytPrh7/4-libocct-ocaf-7.5_7.5.0+dfsg1-1_amd64.deb 
(--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libTKBin.so.7', which is also 
in package libocct-ocaf-7.3:amd64 7.3.0+dfsg1-5
  Preparing to unpack .../5-libocct-data-exchange-7.5_7.5.0+dfsg1-1_amd64.deb 
...
  Unpacking libocct-data-exchange-7.5:amd64 (7.5.0+dfsg1-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-ytPrh7/5-libocct-data-exchange-7.5_7.5.0+dfsg1-1_amd64.deb
 (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libTKBinXCAF.so.7', which is 
also in package libocct-data-exchange-7.3:amd64 7.3.0+dfsg1-5
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-ytPrh7/0-libocct-foundation-7.5_7.5.0+dfsg1-1_amd64.deb
   
/tmp/apt-dpkg-install-ytPrh7/1-libocct-modeling-data-7.5_7.5.0+dfsg1-1_amd64.deb
   
/tmp/apt-dpkg-install-ytPrh7/2-libocct-modeling-algorithms-7.5_7.5.0+dfsg1-1_amd64.deb
   
/tmp/apt-dpkg-install-ytPrh7/3-libocct-visualization-7.5_7.5.0+dfsg1-1_amd64.deb
   /tmp/apt-dpkg-install-ytPrh7/4-libocct-ocaf-7.5_7.5.0+dfsg1-1_amd64.deb
   
/tmp/apt-dpkg-install-ytPrh7/5-libocct-data-exchange-7.5_7.5.0+dfsg1-1_amd64.deb

>From looking the the file list of libocct-data-exchange-7.5 I observed
that there are multiple shared libraries (and nothing else), but all have
the same SOVERSION (7). So why is the package naming following MAJOR.MINOR
instead of SOVERSION? The latter would ease maintenance by avoiding lots
of Breaks+Replaces in the future.
This is probably the same for all the packages shipping opencascade shared
libraries.

cheers,

Andreas

PS: If the libraries from 7.3 and 7.5 are not exchangeable (i.e. not API and ABI
compatible), they should not have the same SOVERSION.


libocct-data-exchange-7.3=7.3.0+dfsg1-5_libocct-data-exchange-7.5=7.5.0+dfsg1-1.log.gz
Description: application/gzip

Bug#977890: libcinnamon-menu-3-0: Upgrade 4.6.1-1->4.8.2-2 causes segfault when launching any application

[Jeffrey Ratcliffe]

Package: libcinnamon-menu-3-0
Version: 4.8.2-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?

Upgraded libcinnamon-menu-3-0 and gir1.2-cmenu-3.0 4.6.1-1->4.8.2-2 and
cinnamon-l10n from 4.6.2-1->4.8.2-2

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

Tried to launch any application from the menus or panel launcher buttons.

   * What was the outcome of this action?

cinnamon segfaulted with casting error, I assume because not all of cinnamon
upgraded.

   * What outcome did you expect instead?

That cinnamon launched the applications with no problem

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



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

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

Versions of packages libcinnamon-menu-3-0 depends on:
ii  libc6 2.31-5
ii  libglib2.0-0  2.66.3-2

libcinnamon-menu-3-0 recommends no packages.

libcinnamon-menu-3-0 suggests no packages.

-- no debconf information

Bug#969372: INFO: Bug#969372: uwsgi-emperor: SysV init script does nothing

[Rens Houben]

Hello,

I've come across the same bug while trying to set up a new service at work.

After some digging (we've currently got a mishmash of Jessie and Buster 
systems, not all of them have been upgraded yet) I discovered that the init 
script, such as it is, is identical in all versions, and it is not actually the 
problem.

Running the init script manually gave the following output:

rhouben@networking-lab-rh:/var/log/uwsgi$ sudo  /etc/init.d/uwsgi-emperor start
[ ok ] Starting uwsgi-emperor (via systemctl): uwsgi-emperor.service.


... Whereas on a system still running Jessie I got:
shadur@radius-srv-dc25:~$ sudo /etc/init.d/uwsgi-emperor restart
[] Restarting uWSGI Emperor server: uwsgi[uWSGI] getting INI configuration 
from /etc/uwsgi-emperor/emperor.ini
setting capability setgid [6]
setting capability setuid [7]
. ok


The issue arose because the init script isn't so much a script as it's a set of 
variables plugged into the init.d helper scripts, and /those/ have changed 
drastically from Jessie to Buster and onwards to call systemctl -- but in 
uwsgi-emperor's case there doesn't appear to /be/ a systemd service file to 
call on, so it quietly fails and does nothing at all.

I'm currently writing at least a rudimentary systemd service file for 
uwsgi-emperor to see if that makes it work; I can share it once I finish if 
you'd like.

--Rens Houben.



SYSTEMEC BV


Marinus Dammeweg 25, 5928 PW Venlo
Postbus 3290, 5902 RG Venlo
Industrienummer: 6817
Nederland

T: 077-3967572 (Support)
K.V.K. nummer: 12027782 (Venlo)


Neem een kijkje op onze vernieuwde website

[Systemec Datacenter Venlo, Nettetal en D?sseldorf]


ISO/IEC 27001:2017 gecertificeerd door
Digitrust, registratienummer DGT2020092101
NEN 7510-01:2017 gecertificeerd door
Digitrust, registratienummer 
DGTN2020092101


[Systemec Helpdesk]  
Helpdesk


[Aanmelden nieuwsbrief]  Aanmelden 
nieuwsbrief


Volg ons op: [Systemec Twitter]   [Systemec 
Facebook]   [Systemec Linkedin] 
  [Systemec Youtube] 

Bug#977781: marked as done (yarnpkg: fails to download modules)

[Debian Bug Tracking System]

Your message dated Tue, 22 Dec 2020 12:50:12 +
with message-id 
and subject line Bug#977781: fixed in node-yarnpkg 1.22.10+~cs22.25.14-1
has caused the Debian Bug report #977781,
regarding yarnpkg: fails to download modules
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
977781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: yarnpkg
Version: 1.22.10+~cs18.39.16-1
Severity: serious

Since yarnpkg add command did not return an error, the autpkgtest was 
succeeding even though it did not add any modules to node_modules 
directory.


I have fixed the faulty autopkgtest which now exposes the failure.
--- End Message ---
--- Begin Message ---
Source: node-yarnpkg
Source-Version: 1.22.10+~cs22.25.14-1
Done: Pirate Praveen 

We believe that the bug you reported is fixed in the latest version of
node-yarnpkg, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 977...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated node-yarnpkg package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 22 Dec 2020 17:31:25 +0530
Source: node-yarnpkg
Architecture: source
Version: 1.22.10+~cs22.25.14-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Pirate Praveen 
Closes: 977781
Changes:
 node-yarnpkg (1.22.10+~cs22.25.14-1) unstable; urgency=medium
 .
   * Team upload
   * Update tar-fs component to 2.1 and refactor watch file
 (Closes: #977781) Thanks to Akshay S Dinesh
   * New upstream version 1.22.10+~cs22.25.14
Checksums-Sha1:
 ec5ce575b8b424edcaeabc50725768a2306bc12d 8144 
node-yarnpkg_1.22.10+~cs22.25.14-1.dsc
 eb391458775cb84cd1a1fae062106bb87545 2691 
node-yarnpkg_1.22.10+~cs22.25.14.orig-decode-uri-component.tar.gz
 fd3c24d66c141625f594c77be7a8dafee2a66c8a 8550 
node-yarnpkg_1.22.10+~cs22.25.14.orig-dnscache.tar.gz
 b913564ae3be0eda6f3de36464837a9cd94b98ac 2478 
node-yarnpkg_1.22.10+~cs22.25.14.orig-gunzip-maybe.tar.gz
 497754b39bee2f1c4ade4521bfd2af0a7c1196e3 16129 
node-yarnpkg_1.22.10+~cs22.25.14.orig-hash-for-dep.tar.gz
 c862901c3c161fb09dac7cdc7e784f80e98f2f14 1760 
node-yarnpkg_1.22.10+~cs22.25.14.orig-is-deflate.tar.gz
 6ca8b07b99c77998025900e555ced8ed80879a83 875 
node-yarnpkg_1.22.10+~cs22.25.14.orig-is-gzip.tar.gz
 57179265b66df5647bd22f430267063218050c3f 2180 
node-yarnpkg_1.22.10+~cs22.25.14.orig-mkdirp-classic.tar.gz
 835a9da1551fa26f70e92329069a23aa6574d7e6 3502 
node-yarnpkg_1.22.10+~cs22.25.14.orig-normalize-url.tar.gz
 44610141ca24664cad35d1e607176193fd8f5b88 4799 
node-yarnpkg_1.22.10+~cs22.25.14.orig-npm-logical-tree.tar.gz
 3b35d84b7ccbbd262fff31dc10da56856ead6d67 3004 
node-yarnpkg_1.22.10+~cs22.25.14.orig-peek-stream.tar.gz
 a78c012b71c17e05f2e3fa2319dd330682efb3cb 4721 
node-yarnpkg_1.22.10+~cs22.25.14.orig-query-string.tar.gz
 35faaa5d54a9c7dd481eb7c4b2a44410c9c763d8 20767 
node-yarnpkg_1.22.10+~cs22.25.14.orig-resolve-package-path.tar.gz
 7f29be7d73c94dd92eccd5c5a15651181d7ecd3d 3392 
node-yarnpkg_1.22.10+~cs22.25.14.orig-string-replace-loader.tar.gz
 489a15ab85f1f0befabb370b7de4f9eb5cbe8784 7408 
node-yarnpkg_1.22.10+~cs22.25.14.orig-tar-fs.tar.gz
 9471efa3ef9128d2f7c6a7ca39c4dd6b5055b132 5874 
node-yarnpkg_1.22.10+~cs22.25.14.orig-v8-compile-cache.tar.gz
 70ee17e430d4d65e30f8b34751d69c5b9ef8e09d 74418435 
node-yarnpkg_1.22.10+~cs22.25.14.orig.tar.gz
 3e6a0ea84c02b532136b32bf5312a4986eb5a273 13240 
node-yarnpkg_1.22.10+~cs22.25.14-1.debian.tar.xz
 742d1e7023b69a2ce95cff1e719b4f157cde30fa 22114 
node-yarnpkg_1.22.10+~cs22.25.14-1_amd64.buildinfo
Checksums-Sha256:
 1bfc6229902d45c645cd0c5ccf9a2a4a0d881b2342c6e91cd53ef4bc167fa411 8144 
node-yarnpkg_1.22.10+~cs22.25.14-1.dsc
 0a3e427c86cd249b0b402907132bf8ba85efb2a34ed1d2b3aa4694fd21730ad6 2691 
node-yarnpkg_1.22.10+~cs22.25.14.orig-decode-uri-component.tar.gz
 103561e61f03394439beddf57daead326ce4e76d051c200d282db13e4b1a7e9d 8550 
node-yarnpkg_1.22.10+~cs22.25.14.orig-dnscache.tar.gz
 87e9b2228f20c9d6ada9131f7fff5f622fe575aad2cc582a0eec22489805c79e 2478