Bug#944731: webkit2gtk: Please drop libsecomp-dev build dependency where it's not supported

[Alberto Garcia]

On Thu, Nov 14, 2019 at 01:26:13PM +0100, John Paul Adrian Glaubitz wrote:
> Source: webkit2gtk
> Version: 2.26.2-1
> Severity: normal
> User: debian-...@lists.debian.org
> Usertags: m68k
> 
> Hello!
> 
> webkit2gtk is currently BD-Uninstallable because it build-depends on
> libsecomp-dev which is not available on all architectures.

Did you check that it builds, though? For m68k we had this
fix-ftbfs-m68k.patch to work around build failures, but I don't know
if it's still good enough and if the resulting binary works (for
example, if you can launch /usr/lib/*/webkit2gtk-4.0/MiniBrowser and
browse the web).

Thanks!

Berto

Bug#805445: More data points

[Bernhard Schmidt]

On Thu, Aug 16, 2018 at 12:41:39AM +0200, Bernhard Schmidt wrote:

Hi,

> I also see this issue on several stretch VMs. In network segments where
> Router Advertisements are present but the machines have a gateway set
> the systems are occasionally not reachable after a reboot (<1% of the
> cases I'd say, totally random). It looks like they already/still have an
> IPv6 default route configured by RA when ifupdown attempts to add the
> default route, which fails. Shortly after the RA route is dropped (due
> to accept_ra 0) and the machine is unreachable.
> 
> A possible solution could be to change "add" to "replace" in
> https://salsa.debian.org/debian/ifupdown/blob/master/inet6.defn#L97 .

I have now created a merge request for this change, as I'm still
frequently bitten by this bug

https://salsa.debian.org/debian/ifupdown/merge_requests/7

I have also done a local backport to the stretch version
(straightforward, but a bit of context is changed so it is easier to
redo).

@Guus: What do you think of this?

Bernhard

Bug#944737: tracker.debian.org: Show pseudo-excuses for experimental as well

[Stuart Prescott]

Package: tracker.debian.org
Severity: wishlist

Dear Maintainer,

TIL: https://release.debian.org/britney/pseudo-excuses-experimental.html

This file contains information on what would happen if that exact same set of
binary and source packages were in unstable and trying to migrate. A low
priority info field that said something like

  Packages in experimental:
  if these packages were in unstable, then they would not be able to migrate
  for the following reasons:
 …
  These issues might need addressing prior to uploading the package to unstable.

regards
Stuart

Bug#944733: grffile does not accept legacy options

[Norbert Preining]

tag 944733 + pending
thanks

Hi Kumar,

> ! LaTeX Error: Unknown option `space' for package `grffile'.

Yes, grffile is a dummy package, no need to load it, or directly only
load graphicx. The version currently in upstream TL already accepts the
old options, but the one that is in the Debian packages doesn't have the
feature by now.

Either wait for the next upload, or remove the option, or remove the
loading of grffile completely.

Thanks.

Norbert

--
PREINING Norbert   http://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#930764: cyrus-common 3.0.8-6 fails to configure package due to "unknown type of DB: BACKUP" on upgrade-db

[Andreas Sundstrom]

Package: cyrus-common
Version: 3.0.8-6+deb10u1
Followup-For: Bug #930764

Dear Maintainer,

The problem is also present in 3.0.8-6+deb10u1.
So when upgrading from 3.0.8-6 to that (through proposed-updates) the 
cyrus-common package
postinst fails and the package is left in a "failed" state.

Output from retrying the configuration of the package:

root@matrix:/usr/share/doc/cyrus-common# dpkg --configure --pending 
Setting up cyrus-common (3.0.8-6+deb10u1) ...
Creating/updating cyrus user account...
The user `cyrus' is already a member of `sasl'.
/usr/lib/cyrus/bin/upgrade-db: Unknown type of DB: BACKUP
dpkg: error processing package cyrus-common (--configure):
 installed cyrus-common package post-installation script subprocess returned 
error exit status 1
dpkg: dependency problems prevent configuration of cyrus-clients:
 cyrus-clients depends on cyrus-common (>= 3.0.8); however:
  Package cyrus-common is not configured yet.

dpkg: error processing package cyrus-clients (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of cyrus-admin:
 cyrus-admin depends on cyrus-common; however:
  Package cyrus-common is not configured yet.

dpkg: error processing package cyrus-admin (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of cyrus-imapd:
 cyrus-imapd depends on cyrus-common (= 3.0.8-6+deb10u1); however:
  Package cyrus-common is not configured yet.

dpkg: error processing package cyrus-imapd (--configure):
 dependency problems - leaving unconfigured
Processing triggers for libc-bin (2.28-10) ...
Errors were encountered while processing:
 cyrus-common
 cyrus-clients
 cyrus-admin
 cyrus-imapd

Bug#943992: transition: qscintilla2, soname 13 -> 15

[Lisandro Damián Nicanor Pérez Meyer]

On Thu, 14 Nov 2019 13:50:38 +0200 Graham Inggs  wrote:
> Control: tags -1 confirmed
> 
> Hi Gudjon
> 
> Please go ahead.
> 
> Regards
> Graham
> 
> 
> 

Bug#921491: debirf: Broken on usr merged systems

[Yann Vernier]

Having run into this issue also, I must note that this behaviour of dpkg 
contradicts their FAQ:

https://wiki.debian.org/Teams/Dpkg/FAQ#Q:_Will_dpkg_replace_a_symlink_with_a_directory_or_vice_versa.3F

Q: Will dpkg replace a symlink with a directory or vice versa?
A: No. As dpkg does not currently track file metadata, it does not know if a 
symlink or directory was switched by a previous package or by the sysadmin. As 
part of the dpkg credo, preserving human configuration is of utmost importance, 
and this kind of change has always been considered as so.

As of now, this should be handled by the package maintainer scripts (possibly 
with aid from dpkg-maintscript-helper), failing to do so should be considered a 
serious bug.

Bug#943992: transition: qscintilla2, soname 13 -> 15

[Lisandro Damián Nicanor Pérez Meyer]

On 19/11/14 01:50, Graham Inggs wrote:
> Control: tags -1 confirmed
> 
> Hi Gudjon
> 
> Please go ahead.

Just for the record: I have seen the FTBFS due to symbols, I'll fix them as 
soon as it is tried an all archs.

And sorry if you received empty mails, it seems I can't still properly set up 
neomutt :-(
 

Bug#944736: gcc-9 doesn't link properly when using ld.bfd

[Gilles Crèvecœur]

Package: gcc-9
Version: 9.2.1-19
Severity: important

Dear Maintainer,

When compiling this short example:

/* a.c begins here */
#include 
#include 

int main(void) {
  mpf_t  y;
  mpf_init2(y, 128);
  mpf_sqrt_ui(y, 2UL);
  gmp_printf("%.*Ff\n", 38, y);
  return 0;
}
/* a.c ends here */

with the command :
 $ gcc -lgmp a.c

gcc produces this error:
/usr/bin/ld: /tmp/cclW7Wdd.o: in function `main':
a.c:(.text+0x15): undefined reference to `__gmpf_init2'
/usr/bin/ld: a.c:(.text+0x26): undefined reference to `__gmpf_sqrt_ui'
/usr/bin/ld: a.c:(.text+0x43): undefined reference to `__gmp_printf'
collect2: error: ld returned 1 exit status

Notice, libgmp is installed, according to this commands:
$ apt-cache policy libgmp-dev
returns:
  libgmp-dev:
  Installed: 2:6.1.2+dfsg-4
  Candidate: 2:6.1.2+dfsg-4
  Version table:
  *** 2:6.1.2+dfsg-4 900
900 https://deb.debian.org/debian sid/main amd64 Packages
100 /var/lib/dpkg/status

But that works as exepected when compiling with clang, and with gcc-8.
That also works with the command:
 $ gcc -fuse-ld=gold -lgmp a.c
It was also successful when I tried with lld from the package lld-8.

I have obtained the same results with th following snippets:
/* b.c begins here */
#include 

int main(void) {
  gchar *str="Just a string";
  gchar *str2;
  str2 = g_strdup(str);
  return 0;
}
/* b.c ends here */
I compiled the latter with:
 $ gcc $(pkg-configs --cflags --libs glib-2.0) b.c
which returns:
/usr/bin/ld: /tmp/ccuQaGQ7.o: in function `main':
b.c:(.text+0x1b): undefined reference to `g_strdup'
collect2: error: ld returned 1 exit status

But that linked properly with ld.gold and lld-8.

I can't figure out how to correct this issue. One can
symlinks /usr/bin/ld to /usr/bin/ld.gold to not have to pass
--fuse-ld=gold, but this is twisted. The default bfd linker should
work.

Cheers
--
Gilles Crèvecœur



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

Kernel: Linux 5.3.1-e1 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gcc-9 depends on:
ii  binutils  2.33.1-2
ii  cpp-9 9.2.1-19
ii  gcc-9-base9.2.1-19
ii  libc6 2.29-3
ii  libcc1-0  9.2.1-19
ii  libgcc-9-dev  9.2.1-19
ii  libgcc1   1:9.2.1-19
ii  libgmp10  2:6.1.2+dfsg-4
ii  libisl21  0.21-2
ii  libmpc3   1.1.0-1
ii  libmpfr6  4.0.2-1
ii  libstdc++69.2.1-19
ii  zlib1g1:1.2.11.dfsg-1+b1

Versions of packages gcc-9 recommends:
ii  libc6-dev  2.29-3

Versions of packages gcc-9 suggests:
ii  gcc-9-doc 9.2.0-1
ii  gcc-9-locales 9.2.1-19
pn  gcc-9-multilib
pn  libasan5-dbg  
pn  libatomic1-dbg
pn  libgcc1-dbg   
pn  libgomp1-dbg  
pn  libitm1-dbg   
pn  liblsan0-dbg  
pn  libquadmath0-dbg  
pn  libtsan0-dbg  
pn  libubsan1-dbg 

-- no debconf information

Bug#838994: Bug#891493: unresolved gtk2-engines-murrine situation (was: numix-gtk-theme: Undocumented and very likely also broken Breaks against murrine-themes since 2.6.7-2)

[Mike Gabriel]

Hi Yves-Alexi,

On  Do 14 Nov 2019 08:03:57 CET, Yves-Alexis Perez wrote:


On Wed, 2019-11-13 at 20:58 +, Mike Gabriel wrote:

One last question: For the themes you maintain, is it ok if I provide
the "Provides: any-murrine-theme" patches (as MRs or pushed commits)
and possibly even NMU them for those murrine-like themes that need them?

Like in numix-gtk-theme [1].

Alternative option is me filing wishlist bugs against all related packages.


Go ahead with NMU, and yes I guess you can directly commit/push to the
repository. At that point I think I should just remove myself from
maintainers/uploaders of the theme packages, I'm unlikely to have time for
them in the near future.

Regards,
- --
Yves-Alexis


ok. Will do the NMUs. Let me know, if / when you remove yourself from  
Uploaders: / Maintainer: fields (I will probably miss it if not pinged  
explicitly).


Thanks+Greets,
Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpc7UlQyCL4n.pgp
Description: Digitale PGP-Signatur

Bug#934753: dropbear-initramfs: please add an autopkgtest

[Johannes Schauer]

Control: block -1 by 944729

Hi,

On Fri, 16 Aug 2019 14:45:17 +0200 Guilhem Moulin  wrote:
> > If you like the script, then I could prepare a patch against src:dropbear
> > which implements an autopkgtest that runs the script.
> Can't hurt indeed, thanks!

just a quick status update: it seems to be impossible right now to have tests
of this kind run on our CI. We don't have user namespaces, cannot mount, cannot
do kpartx and using guestfish fails for an unknown reason which leads to the
resulting disk image being corrupted. Fixing the guestfish bug is tricky
because the error only occurs on Debian CI and not locally, so I prepared
another autopkgtest for libguestfs-tools only to see that libguestfs-tools
cannot even be built on salsa CI because the artifacts are too large:

https://salsa.debian.org/salsa/support/issues/175

Since I cannot test on ci.debian.net myself, I filed a bug with patch to
src:libguestfs and we will see whether that works or not:

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

Since all kinds of other operations are not permitted on salsa CI, using
libguestfs is as far as I know the only way to create a dropbear-initramfs test
which creates the disk image by itself instead of downloading it from
elsewhere. This I'm blocking this bug by the libguestfs bug. If we can make the
latter work, then I can continue working on this one.

Thanks!

cheers, josch


signature.asc
Description: signature

Bug#944735: RM: rapmap [arm64 mips64el ppc64el] -- ANAIS; non-amd64 not supported by upstream

[Michael R. Crusoe]

Package: ftp.debian.org
Severity: normal

Thanks!

Bug#944671: [Debian-med-packaging] Bug#944671: orthanc-dicomweb: missing build on armel

[Sébastien Jodogne]

Dear Ivo,

Please could you indicate where I can find information about how to 
remove the old armel build?


some info is here:

https://wiki.debian.org/ftpmaster_Removals

Note that you can close this bug once the removal is done (otherwise 
this bug would prevent migration to testing).


Thanks for your kind explanation!

As instructed on the page you sent, I have just introduced the related 
"RM: orthanc-dicomweb [armel]" bug to ask for the removal:

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

Regards,
Sébastien-

Bug#944734: New upstream version available

[Bastian Venthur]

Package: docker-compose
Version: 1.21.0-3
Severity: wishlist

Dear Maintainers,

the current version in unstable (1.21.0) has been uploaded more than a year
ago. The current version contains a lot of bug fixes and improvements over the
version we have in Sid. Please consider updating the package.


Cheers,

Bastian

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

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

Versions of packages docker-compose depends on:
ii  python3  3.7.5-1
ii  python3-cached-property  1.5.1-4
ii  python3-distutils3.8.0-1
ii  python3-docker   3.4.1-4.1
ii  python3-dockerpty0.4.1-2
ii  python3-docopt   0.6.2-2.1
ii  python3-jsonschema   2.6.0-4
ii  python3-requests 2.21.0-1
ii  python3-six  1.13.0-1
ii  python3-texttable1.6.2-2
ii  python3-websocket0.53.0-2
ii  python3-yaml 5.1.2-1

Versions of packages docker-compose recommends:
ii  docker.io  19.03.4+dfsg2-2

docker-compose suggests no packages.

-- no debconf information

Bug#944733: grffile does not accept legacy options

[Kumar Appaiah]

Package: texlive-latex-extra
Version: 2019.20191112-1
Severity: important

When trying to use asymptote to make some graphics, I got this:

...
(/usr/share/texlive/texmf-dist/tex/latex/grffile/grffile.sty)

! LaTeX Error: Unknown option `space' for package `grffile'.

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

l.33 \makeatletter

It turns out that a recent (11th November, 2019) update to grffile
solves this problem, since it silently accepts legacy options.

Thanks.

Kumar

-- Package-specific info:
##
 List of ls-R files

-rw-r--r-- 1 root root 2581 Nov 14 18:49 /var/lib/texmf/ls-R
lrwxrwxrwx 1 root root 29 Jul 31 12:51 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Nov 12 10:00 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Nov 12 10:00 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 root root 475 Sep  2 14:32 /etc/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Nov 12 10:00 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Nov 12 10:00 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 2887 Nov 14 18:48 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Aug 17  2017 mktex.cnf
-rw-r--r-- 1 root root 475 Sep  2 14:32 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'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages texlive-latex-extra depends on:
ii  preview-latex-style11.91-2
ii  python 2.7.17-1
ii  python33.7.5-1
ii  tex-common 6.12
ii  texlive-base   2019.20191112-1
ii  texlive-binaries   2019.20190605.51237-3
ii  texlive-latex-recommended  2019.20191112-1
ii  texlive-pictures   2019.20191112-1

Versions of packages texlive-latex-extra recommends:
ii  texlive-fonts-recommended  2019.20191112-1
ii  texlive-plain-generic  2019.20191112-1

Versions of packages texlive-latex-extra suggests:
ii  icc-profiles2.1-2
ii  libfile-which-perl  1.23-1
pn  libspreadsheet-parseexcel-perl  
ii  python-pygments 2.3.1+dfsg-1
pn  texlive-latex-extra-doc 

Versions of packages tex-common depends on:
ii  dpkg  1.19.7
ii  ucf   3.0038+nmu1

Versions of packages tex-common suggests:
ii  debhelper  12.7.1

Versions of packages texlive-latex-extra is related to:
ii  tex-common6.12
ii  texlive-binaries  2019.20190605.51237-3

-- no debconf information

Bug#944675: udev: me too

[Michael Biebl]

Control: forwarded -1 https://github.com/systemd/systemd/issues/14027

Am 14.11.19 um 14:23 schrieb Gunther Furtado:

> Keyboard and mouse not working in X.org with udev 243-5 #14027

Thanks, marking accordingly.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#940127: ghostscript makes c2esp autopkgtest timeout

[Jonas Smedegaard]

Quoting Didier 'OdyX' Raboud (2019-09-22 15:30:53)
> Le dimanche, 22 septembre 2019, 13.25:19 h CEST Brian Potkin a écrit :
> > On Sat 21 Sep 2019 at 17:39:20 +0200, Didier 'OdyX' Raboud wrote:
> > > Le samedi, 21 septembre 2019, 16.24:30 h CEST Brian Potkin a écrit :
> > > > > There's clearly a regression in ghostscript 9.28 that started
> > > > > segfaulting
> > > > > in the c2esp filter chain. But I can't manage to reproduce it outside
> > > > > of
> > > > > the "cups + c2esp + cups-filters (gstoraster) + ghostscript"
> > > > > environment.
> > > > > 
> > > > > Brian; Till: any idea?
> > > > 
> > > > No ideas from me really. I too get gstoraster stopping when attempting
> > > > to print /usr/share/cups/data/form_russian.pdf; but the same is true for
> > > > form_english.pdf.
> > > 
> > > Ah, sorry; I formulated my inquiry weakly. Let me try again:
> > > 
> > > Do you have a hint on how to reproduce the failing ghostscript call (or
> > > the
> > > gstoraster call) directly, without using CUPS in the middle?
> > 
> > Would this do?
> > 
> > cat /usr/share/cups/data/form_russian.pdf | gs -dQUIET -dPARANOIDSAFER
> > -dNOPAUSE -dBATCH -dNOINTERPOLATE -dNOMEDIAATTRS -dShowAcroForm
> > -sstdout=%stderr -sOutputFile=%stdout -sDEVICE=cups -r600x600
> > -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -dcupsBitsPerColor=8
> > -dcupsColorOrder=0 -dcupsColorSpace=4 -scupsPageSizeName=A4
> > -I/usr/share/cups/fonts -c '< > 3.00] /Margins[00]>>setpagedevice' -f -_ > out.ras
> 
> The problem is… This doesn't segfault. :-(

This bugreport seems to only really describe broken behaviour of c2esp.

Yes, it smells quite strongly of being _caused_ by some bug in 
ghostscript, but when only proven breakable in an environment created 
inside of c2esp, it seems more sensible to me that this bugreport is 
tied to c2esp rather than ghostscript.

@Didier: Since you reassigned this to (only) ghostscript, would you 
please consider re-reassigning to (only) c2esp instead?

Reason I ask is that ghostscript is now security-buggy in testing since 
a month, seemingly blocked only by this issue.  If reassigning does not 
seem sensible, then how about lowering severity (maybe only 
temporarily)?


 - 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#944732: RM: orthanc-dicomweb [armel] -- ROM; node-axios is not available on armel

[Sebastien Jodogne]

Package: ftp.debian.org
Severity: normal

The reason for this removal is discussed in bug Bug#944671:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944671



Note: this was a request for a partial removal from testing, converted in one 
for unstable

Bug#944675: udev: me too

[Gunther Furtado]

Dear Maintainer,


I've done it. Hope it helps.


Keyboard and mouse not working in X.org with udev 243-5 #14027


Cheers,


Em 14/11/2019 10:35, Michael Biebl escreveu:

Am 14.11.19 um 13:25 schrieb Gunther Furtado:

Package: udev
Version: 243-5
Followup-For: Bug #944675

Dear Maintainer,

Same thing here (different hardware).


Anyone, who is affected by this, willing to file this upstream at
https://github.com/systemd/systemd/issues?



--

"Mas, afinal, só as criaturas que nunca
escreveram cartas de amor é que são ridículas." Fernando Pessoa

Gunther Furtado
Curitiba - Paraná - Brasil
gunfurt...@gmail.com

Bug#944420: Bug confirmed with 5.x kernel on Manjaroo, too

[Philipp Klaus Krause]

Apparently someone has the same problem (AMD 3400G APU, mainboard with
B450 chipset, 5.x linux kernel, green screen crash just after login)
using a RC of linux 5.4 on Manjaro:

https://forum.manjaro.org/t/manjaro-with-ryzen-3-3200g-vega-8-any-experience/110497/18

Bug#944227: transition: prompt-toolkit

[Graham Inggs]

Control: tags -1 moreinfo

Hi Gordon

Please file bugs for the affected packages that do not currently support 
ptk 2, and mark those bugs as blocking this one.


Do the affected packages have versioned Depends, or did you add Breaks 
against those packages in your package?  In either case, you can go 
ahead and file those bugs with severity Serious.


Regards
Graham

Bug#917927: [libreoffice-impress] Blank screen with OpenGL transitions

[Laurent Bigonville]

Package: libreoffice-impress
Followup-For: Bug #917927

Hello,

I did some testing and it seems that if I swap the libOGLTranslo.so
library built by the debian package (experimental) by the one shipped by
the official build.

So the issue seems to be with this and not really with a system
dependency. Note that the size of the two files are substencially
different (239k for the debian one and 292k for the upstream one).

So there is maybe something wrong with the compilation of this file?

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.3.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages libreoffice-impress depends on:
ii  libc62.29-3
ii  libepoxy01.5.3-0.1
ii  libetonyek-0.1-1 0.1.9-1
ii  libgcc1  1:9.2.1-19
ii  libmwaw-0.3-30.3.15-2
ii  libodfgen-0.1-1  0.1.7-1
ii  libreoffice-core 1:6.3.3-2
ii  libreoffice-draw 1:6.3.3-2
ii  librevenge-0.0-0 0.0.4-6+b1
ii  libstaroffice-0.0-0  0.0.6-1
ii  libstdc++6   9.2.1-19
ii  uno-libs36.3.3-2
ii  ure  6.3.3-2

libreoffice-impress recommends no packages.

Versions of packages libreoffice-impress suggests:
ii  bluez  5.50-1+b1

Versions of packages libreoffice-core depends on:
ii  fontconfig  2.13.1-2+b1
ii  fonts-opensymbol2:102.11+LibO6.3.3-2
ii  libboost-locale1.67.0   1.67.0-13
ii  libc6   2.29-3
ii  libcairo2   1.16.0-4
ii  libclucene-contribs1v5  2.3.3.4+dfsg-1+b1
ii  libclucene-core1v5  2.3.3.4+dfsg-1+b1
ii  libcmis-0.5-5v5 0.5.2-1
ii  libcups22.3.0-7
ii  libcurl3-gnutls 7.66.0-1+b1
ii  libdbus-1-3 1.13.12-2bigon1
ii  libdconf1   0.34.0-1
ii  libeot0 0.01-5+b1
ii  libepoxy0   1.5.3-0.1
ii  libexpat1   2.2.9-1
ii  libexttextcat-2.0-0 3.4.5-1
ii  libfontconfig1  2.13.1-2+b1
ii  libfreetype62.10.1-2
ii  libgcc1 1:9.2.1-19
ii  libglib2.0-02.62.2-3
ii  libgpgmepp6 1.13.1-1
ii  libgraphite2-3  1.3.13-11
ii  libgstreamer-plugins-base1.0-0  1.16.1-1
ii  libgstreamer1.0-0   1.16.1-1
ii  libharfbuzz-icu02.6.4-1
ii  libharfbuzz0b   2.6.4-1
ii  libhunspell-1.7-0   1.7.0-2+b1
ii  libhyphen0  2.8.8-7
ii  libice6 2:1.0.9-2
ii  libicu6363.2-2
ii  libjpeg62-turbo 1:1.5.2-2+b1
ii  liblcms2-2  2.9-4
ii  libldap-2.4-2   2.4.48+dfsg-1+b2
ii  libmythes-1.2-0 2:1.2.4-3+b1
ii  libneon27-gnutls0.30.2-3
ii  libnspr42:4.23-1
ii  libnss3 2:3.47-1
ii  libnumbertext-1.0-0 1.0.5-3
ii  liborcus-0.14-0 0.14.1-6
ii  libpng16-16 1.6.37-1
ii  libpoppler820.71.0-6
ii  librdf0 1.0.17-1.1+b1
ii  libreoffice-common  1:6.3.3-2
ii  librevenge-0.0-00.0.4-6+b1
ii  libsm6  2:1.2.3-1
ii  libstdc++6  9.2.1-19
ii  libx11-62:1.6.8-1
ii  libxext62:1.3.3-1+b2
ii  libxinerama12:1.1.4-2
ii  libxml2 2.9.4+dfsg1-7+b3
ii  libxmlsec1  1.2.28-2
ii  libxmlsec1-nss  1.2.28-2
ii  libxrandr2  2:1.5.1-1
ii  libxrender1 1:0.9.10-1
ii  libxslt1.1  1.1.32-2.2
ii  uno-libs3   6.3.3-2
ii  ure 6.3.3-2
ii  zlib1g  1:1.2.11.dfsg-1+b1

Versions of packages libreoffice-core recommends:
ii  gstreamer1.0-libav 1.16.1-1
ii  gstreamer1.0-plugins-bad   1.16.1-1+b3
ii  gstreamer1.0-plugins-base  1.16.1-1
ii  gstreamer1.0-plugins-good  1.16.1-1
ii  gstreamer1.0-plugins-ugly  1.16.1-1
ii  libpaper-utils 1.1.28+b1

Versions of packages libreoffice-draw depends on:
ii  libavahi-client3 0.7-4+b1
ii  libavahi-common3 0.7-4+b1
ii  libc62.29-3
ii  libcdr-0.1-1 0.1.5-1
ii  libdbus-1-3  1.13.12-2bigon1
ii  libfreehand-0.1-10.1.2-2
ii  libgcc1  1:9.2.1-19
ii  

Bug#944671: [Debian-med-packaging] Bug#944671: orthanc-dicomweb: missing build on armel

[Ivo De Decker]

Hi,

On 11/14/19 12:44 PM, Sébastien Jodogne wrote:

Hello,

Thanks for your feedback. Indeed, "node-axios" is needed to build the 
orthanc-dicomweb package.


Please could you indicate where I can find information about how to 
remove the old armel build?


some info is here:

https://wiki.debian.org/ftpmaster_Removals

Note that you can close this bug once the removal is done (otherwise 
this bug would prevent migration to testing).


Andreas, I see that you are uploader of this package. I suspect you 
could help Sébastien if more info is needed?


Thanks,

Ivo

Bug#944163: interimap: seems --repair doesn't work

[Jonas Smedegaard]

Quoting Guilhem Moulin (2019-11-07 00:45:48)
> On Wed, 06 Nov 2019 at 12:44:08 +0100, Jonas Smedegaard wrote:
> > When I switched, I removed the local folder and had interimap 
> > syncronize it from scratch.  Or at least that is my belief: Does 
> > your forensics analysis above imply that I failed at that, and the 
> > local copy cannot have been initialized by interimap?

...and I since then did this:

  interimap --config hb --delete --target=database,local INBOX
  interimap --config hb

...which seemingly succeeded in throwing away local copy of INBOX and 
re-fetching it from remote INBOX, but then fails similarly with Drafts.

So I can now read my INBOX again, and we can continue debugging Drafts 
which are less crucial for me to have syncronized. :-)

...because surprisingly to me, attempting to throw away local copy of 
_Drafts_ failed:

jonas@auryn:~$ interimap --config hb --delete --target=database,local Drafts
jo...@jawa.homebase.dk's password: 
local: IMAP traffic (bytes): recv 571 sent 46
remote: IMAP traffic (bytes): recv 625 (compr. 594, factor 0.95) sent 71 
(compr. 80, factor 1.13)
jonas@auryn:~$ interimap --config hb Drafts
jo...@jawa.homebase.dk's password: 
remote: ERROR: UIDVALIDITY changed! (1571588832 != 1154884797)  Need to 
invalidate the UID cache.
local: IMAP traffic (bytes): recv 630 sent 109
remote: IMAP traffic (bytes): recv 684 (compr. 650, factor 0.95) sent 134 
(compr. 141, factor 1.05)

Am I perhaps misunderstanding and UIDVALIDITY is tied to whole account, 
not each mailbox?  But if that's the case then it confuses me that now 
sync'ing _only_ INBOX succeeds (it didn't previously).

Here is the above, repeated with --debug:

jonas@auryn:~$ interimap --config hb --debug Drafts
>>> interimap 0.4
local: S: * PREAUTH [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE 
IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT 
MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS 
LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN 
CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY LITERAL+ 
NOTIFY SPECIAL-USE] Logged in as jonas
local: C: 00 ENABLE QRESYNC
local: S: * ENABLED QRESYNC
local: S: 00 OK Enabled (0.001 + 0.000 secs).
jo...@jawa.homebase.dk's password: 
remote: S: * PREAUTH [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE 
IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT 
MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS 
LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN 
CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY LITERAL+ NOTIFY 
SPECIAL-USE COMPRESS=DEFLATE] Logged in as jonas
remote: C: 00 COMPRESS DEFLATE
remote: S: 00 OK Begin compression (0.001 + 0.000 secs).
remote: C: 01 ENABLE QRESYNC
remote: S: * ENABLED QRESYNC
remote: S: 01 OK Enabled (0.001 + 0.000 secs).
local: C: 01 LIST "" Drafts RETURN (SUBSCRIBED STATUS (UIDVALIDITY UIDNEXT 
HIGHESTMODSEQ))
local: S: * LIST (\Subscribed \UnMarked) "." Drafts
local: S: * STATUS Drafts (UIDNEXT 962 UIDVALIDITY 1571588832 HIGHESTMODSEQ 4)
local: S: 01 OK List completed (0.006 + 0.000 + 0.005 secs).
remote: C: 02 LIST "" Drafts RETURN (SUBSCRIBED STATUS (UIDVALIDITY UIDNEXT 
HIGHESTMODSEQ))
remote: S: * LIST (\Subscribed \UnMarked) "." Drafts
remote: S: * STATUS Drafts (UIDNEXT 962 UIDVALIDITY 1571588832 HIGHESTMODSEQ 4)
remote: S: 02 OK List completed (0.015 + 0.000 + 0.014 secs).
local: Update last clean state for Drafts: (UIDVALIDITY 1571588832 
HIGHESTMODSEQ 1 UIDNEXT 1)
remote: ERROR: UIDVALIDITY changed! (1571588832 != 1154884797)  Need to 
invalidate the UID cache.
local: IMAP traffic (bytes): recv 630 sent 109
remote: IMAP traffic (bytes): recv 684 (compr. 652, factor 0.95) sent 134 
(compr. 141, factor 1.05)
Cleaning up...
jonas@auryn:~$ interimap --config hb --delete --target=database,local Drafts
jo...@jawa.homebase.dk's password: 
remote: IMAP traffic (bytes): recv 625 (compr. 594, factor 0.95) sent 71 
(compr. 80, factor 1.13)
local: IMAP traffic (bytes): recv 571 sent 46
jonas@auryn:~$ interimap --config hb --debug Drafts
>>> interimap 0.4
local: S: * PREAUTH [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE 
IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT 
MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS 
LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN 
CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY LITERAL+ 
NOTIFY SPECIAL-USE] Logged in as jonas
local: C: 00 ENABLE QRESYNC
local: S: * ENABLED QRESYNC
local: S: 00 OK Enabled (0.001 + 0.000 secs).
jo...@jawa.homebase.dk's password: 
remote: S: * PREAUTH [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE 
IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT 
MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE 

Bug#944731: webkit2gtk: Please drop libsecomp-dev build dependency where it's not supported

[John Paul Adrian Glaubitz]

Source: webkit2gtk
Version: 2.26.2-1
Severity: normal
User: debian-...@lists.debian.org
Usertags: m68k

Hello!

webkit2gtk is currently BD-Uninstallable because it build-depends on
libsecomp-dev which is not available on all architectures.

Could you change the build dependencies and configuring in debian/rules
such that libsecomp-dev isn't used on architectures where it isn't
available?

Thanks,
Adrian

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

Bug#944675: udev: me too

[Michael Biebl]

Am 14.11.19 um 13:25 schrieb Gunther Furtado:
> Package: udev
> Version: 243-5
> Followup-For: Bug #944675
> 
> Dear Maintainer,
> 
> Same thing here (different hardware).
> 

Anyone, who is affected by this, willing to file this upstream at
https://github.com/systemd/systemd/issues?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#835566: please clarify docs regarding mr run

[Marc Haber]

Thanks for giving this so much thought. Those things are all valid, I
would probably not come up with this kind of creativity myself. Please
consider writing similary inspiring text in the docs.  No code changes
needed then.

> You could just evaluate it as shell code instead, or run a subshell:
> 
>[DEFAULT]
>run = eval "$*"
> 
>[DEFAULT]
>run = sh -c "$*"
> 
> Then you would be able to run something like this:
> 
>$ mr run mr config '$MR_REPO' foo=bar bar=baz

Wouldnt the subshell immediately invoke quoting hell?

> I'm inclined to make these changes to myrepos:
> 
>  * Make the config section optional when the current dir is a
>registered repos and derive the section from the current dir.
>  * Add a recursive option that would apply to the config and register
>commands and cause them to do their jobs recursively.

Thank you very much.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#941479: text in a new split panel doesn't fill all the vertical space

[Egmont Koblinger]

Hi,

Is this behavior fully reproducible for you? (I cannot reproduce it.)

Could you please try a few things for me?

- What does "stty size" report in the faulty pane? (I'm wondering if
it matches the screen size shown in the red bar, or if it's the
default 80x24, or perhaps something else.)

- What does "echo $LINES $COLUMNS" say?

- Does slightly resizing the window, or slightly dragging the
separator between the two terminals fix the issue?

- Does this command (clearing the scroll region) fix the issue:  printf '\e[r'

- How does a fullscreen application (e.g. "mc") look like in that panel?

- If you start selecting with the mouse, can you select row-by-row
over the large unused area?

- Could you test with VTE master? I particularly suspect that
https://gitlab.gnome.org/GNOME/vte/commit/07aad3e0d5 (a partial fix
for https://gitlab.gnome.org/GNOME/vte/issues/188) could be relevant,
although it's not clear to me how an intermittent problem with the
initial size could get permanently stuck.

- Do you have anything special in your shell startup, e.g.
automatically launching screen/tmux/byobu, or some weird 3rd party
hacks? If so, can you try with the default shell configs?


thanks,
egmont

Bug#944042: Help needed to adapt python-skbio to Python3(?) / Pandas

[Andreas Tille]

Control: tags -1 help
Control: tags -1 upstream
Control: forwarded -1 https://github.com/biocore/scikit-bio/issues/1678

Hi Rebecca,

thanks a lot for working on the Pandas migration.

On Wed, Nov 13, 2019 at 10:19:56PM +, Rebecca N. Palmer wrote:
> The ones that are blocking pandas [1] are python-skbio,
> 
> [1] https://qa.debian.org/excuses.php?package=pandas (cnvkit since fixed)

I've checked the issue with some patch from upstream[1] but failed.  I
also tried to build HEAD from upstream which also leaves three remaining
errors which I reported in issue #1678[2]:


==
ERROR: test_munging_invalid_type_to_self_type 
(skbio.sequence.tests.test_sequence.TestDistance)
--
Traceback (most recent call last):
  File 
"/build/python-skbio-0.5.5a/.pybuild/cpython3_3.7_skbio/build/skbio/sequence/tests/test_sequence.py",
 line 2369, in test_munging_invalid_type_to_self_type
Sequence("ACGT").distance(42)
  File 
"/build/python-skbio-0.5.5a/.pybuild/cpython3_3.7_skbio/build/skbio/sequence/_sequence.py",
 line 1539, in distance
other = self._munge_to_self_type(other, 'distance')
  File 
"/build/python-skbio-0.5.5a/.pybuild/cpython3_3.7_skbio/build/skbio/sequence/_sequence.py",
 line 2161, in _munge_to_self_type
return self.__class__(other)
  File 
"/build/python-skbio-0.5.5a/.pybuild/cpython3_3.7_skbio/build/skbio/sequence/_sequence.py",
 line 622, in __init__
s = np.frombuffer(sequence, dtype=np.uint8)
TypeError: a bytes-like object is required, not 'int'

==
ERROR: test_init_invalid_sequence 
(skbio.sequence.tests.test_sequence.TestSequence)
--
Traceback (most recent call last):
  File 
"/build/python-skbio-0.5.5a/.pybuild/cpython3_3.7_skbio/build/skbio/sequence/tests/test_sequence.py",
 line 465, in test_init_invalid_sequence
Sequence(('a', 'b', 'c'))
  File 
"/build/python-skbio-0.5.5a/.pybuild/cpython3_3.7_skbio/build/skbio/sequence/_sequence.py",
 line 622, in __init__
s = np.frombuffer(sequence, dtype=np.uint8)
TypeError: a bytes-like object is required, not 'tuple'

==
FAIL: test_no_variation_pearson 
(skbio.stats.distance.tests.test_mantel.MantelTests)
--
Traceback (most recent call last):
  File 
"/build/python-skbio-0.5.5a/.pybuild/cpython3_3.7_skbio/build/skbio/stats/distance/tests/test_mantel.py",
 line 247, in test_no_variation_pearson
npt.assert_equal(obs, (np.nan, np.nan, 3))
  File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 
355, in assert_equal
assert_equal(actual[k], desired[k], 'item=%r\n%s' % (k, err_msg), verbose)
  File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 
427, in assert_equal
raise AssertionError(msg)
AssertionError:
Items are not equal:
item=0

 ACTUAL: 0.0
 DESIRED: nan

--
Ran 2352 tests in 44.011s

FAILED (SKIP=30, errors=2, failures=1)


I somehow suspect that the two errors above might be caused by a broken
Python3 conversion - any help to fix this would be welcome.

Kind regards

   Andreas.

[1] 
https://github.com/biocore/scikit-bio/commit/9c061da7e2746aee403b41621f71b118ce5c52f8
[2] https://github.com/biocore/scikit-bio/issues/1678

-- 
http://fam-tille.de

Bug#944730: iproute2: `ip route get` doesn't work for subnets anymore

[Clément 'wxcafé' Hertling]

Package: iproute2
Version: 5.3.0-1
Severity: normal
Tags: upstream

`ip route get 1.0.0.0/1` used to return the route for `1.0.0.0/32`,
which was flawed behavior but at least somewhat worked in that it
returned something.

`ip route get 0.0.0.0/0`, which should have worked, used to return
`need at least a destination address`, which was incorrect.

Now, `ip route get `1.0.0.0/1` returns
`Error: ipv4: Invalid values in header for route get request.`, and
`ip route get 0.0.0.0/0` returns
`Error: ipv4: rtm_src_len and rtm_dst_len must be 32 for IPv4`. It
seems iproute2 doesn't 'support' querying subnets anymore, which is
broken behavior.

Thanks

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages iproute2 depends on:
ii  debconf [debconf-2.0]  1.5.73
ii  libbsd00.10.0-1
ii  libc6  2.29-3
ii  libcap21:2.27-1
ii  libcap2-bin1:2.27-1
ii  libdb5.3   5.3.28+dfsg1-0.6
ii  libelf10.176-1.1
ii  libmnl01.0.4-2+b1
ii  libselinux12.9-2+b2
ii  libxtables12   1.8.3-2

Versions of packages iproute2 recommends:
pn  libatm1  

Versions of packages iproute2 suggests:
pn  iproute2-doc  

-- debconf information excluded

Bug#944725: iproute2: `ip route get` cannot lookup in other routing tables

[Luca Boccassi]

On Thu, 14 Nov 2019 06:20:51 -0500 =?utf-
8?b?Q2zDqW1lbnQgJ3d4Y2Fmw6knIEhlcnRsaW5n?= <
wxc...@wxcafe.net
> wrote:
> Package: iproute2
> Version: 5.3.0-1
> Severity: normal
> Tags: ipv6 upstream
> 
> `ip route get` is a great tool to lookup how the host will route to a
> specific destination.
> Unfortunately, while many other `ip route` subcommands can use `table
> foo` to work with a specific routing table, `ip route get` can't:
> 
> ```
> # ip route get 62.210.115.205
> 62.210.115.205 via 10.242.10.13 dev tun0 src 10.242.10.14 uid 1000 
> cache 
> # ip route get 62.210.115.205 table local
> Error: inet prefix is expected rather than "table".
> ```
> 
> It'd be great to be able to use routing tables normally with ip route
> get as with other iproute2 tools
> 
> Thank you

Could you please test the following simple patch:

--- a/ip/iproute.c
+++ b/ip/iproute.c
@@ -71,6 +71,7 @@ static void usage(void)
"[ mark NUMBER ] [ vrf NAME ]\n"
"[ uid NUMBER ] [ ipproto PROTOCOL 
]\n"
"[ sport NUMBER ] [ dport NUMBER 
]\n"
+   "[ table TABLE_ID ]\n"
"   ip route { add | del | change | append | replace } 
ROUTE\n"
"SELECTOR := [ root PREFIX ] [ match PREFIX ] [ exact PREFIX 
]\n"
"[ table TABLE_ID ] [ vrf NAME ] [ proto RTPROTO 
]\n"
@@ -2044,6 +2045,18 @@ static int iproute_get(int argc, char **argv)
invarg("Invalid \"ipproto\" value\n",
   *argv);
addattr8(, sizeof(req), RTA_IP_PROTO, ipproto);
+   } else if (matches(*argv, "table") == 0) {
+   __u32 tid;
+
+   NEXT_ARG();
+   if (rtnl_rttable_a2n(, *argv))
+   invarg("\"table\" value is invalid\n", *argv);
+   if (tid < 256)
+   req.r.rtm_table = tid;
+   else {
+   req.r.rtm_table = RT_TABLE_UNSPEC;
+   addattr32(, sizeof(req), RTA_TABLE, tid);
+   }
} else {
inet_prefix addr;
 
-- 
Kind regards,
Luca Boccassi


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

Bug#930869: Please keep pm-utils

[Adam Borowski]

On Thu, Nov 14, 2019 at 09:13:51AM +0100, Andras Korn wrote:
> I just stumbled on this bugreport.
> 
> I'm a happy pm-utils user and would like the package to stick around. I use
> it on dozens of computers ranging from servers to desktops to laptops.
> 
> From reading the bugreport, there doesn't appear to be any identifiable,
> specific, actionable reason for removing it, does there?

There's none as far as I can tell, indeed.

After a thought, even cleaning away the quirks would be counterproductive. 
They apply to old i386 machines that need real mode BIOS calls; while I and
most of us have no such hardware to test, it's still used by some users.
But keeping such i386 support is not _my_ itch to scratch, I personally
wouldn't cry if those parts were trimmed away.

Thus:
* on old buggy hardware pm-utils works while new stuff doesn't
* on old non-buggy, and on modern hardware, pm-utils works and is more
  convenient to use (eg. on headless boxes)

Ie, this bug report is outright bogus.  Without even a single identifiable
actionable problem, there's nothing to fix.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol,
⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month.
⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake,
⠈⠳⣄ etc), let the drink age at least 3-6 months.

Bug#939929: terminator: crash when trying to start

[Egmont Koblinger]

Hi,

Could you please share your terminator config file
(/home/benoit/.config/terminator/config)?

If you move that file away, does terminator 1.91-4 start up?

thanks,
e.

Bug#944729: libguestfs: Please add an autopkgtest

[Johannes 'josch' Schauer]

Source: libguestfs
Version: 1:1.40.2-2+b10
Severity: wishlist
Tags: patch

Hi,

it would be great if src:libguestfs would include an autopkgtest, so
that we regularly verify that basic functionality still works and as yet
another example of how to use libguestfs from a script.

I attached a patch which first creates a tarball containing a Debian
unstable chroot and then uses guestfish to create a disk image with
extlinux. Lastly, qemu is used to boot the image and we verify that
everything works by connecting to it via ssh.

If you want to verify that all of this works you can run:

$ sudo debian/tests/extlinux

In principal, all the tools the script uses can also work without
superuser privileges. But due to limitations on ci.debian.net and
salsa-ci, we cannot use linux user namespaces and need root instead. If
you want to run the script on your local machine without root
permissions, then replace --mode=root with --mode=unshare in the
autopkgtest and then run the script without sudo in front. It will work
just as well.

I also added a debian/salsa-ci.yml but that one is not useful yet,
because libguestfs seems too large for salsa-ci. See:
https://salsa.debian.org/salsa/support/issues/175

Thanks!

cheers, josch
>From a650d5c1f9bc260996e25079d50114cb7dbddc5a Mon Sep 17 00:00:00 2001
From: Johannes 'josch' Schauer 
Date: Thu, 14 Nov 2019 11:21:03 +0100
Subject: [PATCH] add autopkgtest

---
 debian/salsa-ci.yml   | 14 ++
 debian/tests/control  |  2 +
 debian/tests/extlinux | 99 +++
 3 files changed, 115 insertions(+)
 create mode 100644 debian/salsa-ci.yml
 create mode 100644 debian/tests/control
 create mode 100644 debian/tests/extlinux

diff --git a/debian/salsa-ci.yml b/debian/salsa-ci.yml
new file mode 100644
index 0..ab4d9f016
--- /dev/null
+++ b/debian/salsa-ci.yml
@@ -0,0 +1,14 @@
+---
+include:
+  - https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/salsa-ci.yml
+  - 
https://salsa.debian.org/salsa-ci-team/pipeline/raw/master/pipeline-jobs.yml
+
+variables:
+  SALSA_CI_DISABLE_APTLY: 1
+  SALSA_CI_DISABLE_AUTOPKGTEST: 0
+  SALSA_CI_DISABLE_BLHC: 1
+  SALSA_CI_DISABLE_LINTIAN: 1
+  SALSA_CI_DISABLE_PIUPARTS: 1
+  SALSA_CI_DISABLE_REPROTEST: 1
+  SALSA_CI_DISABLE_BUILD_PACKAGE_ALL: 1
+  SALSA_CI_DISABLE_BUILD_PACKAGE_ANY: 1
diff --git a/debian/tests/control b/debian/tests/control
new file mode 100644
index 0..a46476f58
--- /dev/null
+++ b/debian/tests/control
@@ -0,0 +1,2 @@
+Tests: extlinux
+Depends: libguestfs-tools, mmdebstrap, linux-image-amd64, openssh-client
diff --git a/debian/tests/extlinux b/debian/tests/extlinux
new file mode 100644
index 0..e2f39ef84
--- /dev/null
+++ b/debian/tests/extlinux
@@ -0,0 +1,99 @@
+#!/bin/sh
+
+set -exu
+
+ssh="ssh -oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no -i id_rsa 
-T"
+
+pkgs="linux-image-amd64,openssh-server,systemd-sysv,libpam-systemd,policykit-1"
+pkgs="$pkgs,iproute2,util-linux,e2fsprogs,ifupdown,net-tools,netbase"
+pkgs="$pkgs,iputils-ping,isc-dhcp-client,lvm2,parted,cryptsetup"
+pkgs="$pkgs,dropbear-initramfs,busybox,fdisk,mmdebstrap,udev"
+
+# we have to use root mode on salsa CI because:
+#  - unshare mode fails because /sys is mounted read-only
+#and kernel.unprivileged_userns_clone is not set to 1
+#  - fakechroot mode fails because of failing postinst of linux-image-amd64
+#  - proot mode produces wrong permissions
+mmdebstrap --mode=root --variant=apt --include=$pkgs \
+   --customize-hook='chroot "$1" passwd --delete root' \
+   --customize-hook='chroot "$1" useradd --home-dir /home/user 
--create-home user' \
+   --customize-hook='chroot "$1" passwd --delete user' \
+   --customize-hook='echo host > "$1/etc/hostname"' \
+   --customize-hook='echo "127.0.0.1 localhost host" > "$1/etc/hosts"' \
+   --customize-hook='echo "/dev/sda1 / auto errors=remount-ro 0 1" > 
"$1/etc/fstab"' \
+   unstable debian-unstable.tar
+
+cat << END > extlinux.conf
+default linux
+timeout 0
+
+label linux
+kernel /vmlinuz
+append initrd=/initrd.img root=/dev/sda1 net.ifnames=0 console=ttyS0
+END
+
+cat << END > interfaces
+auto lo
+iface lo inet loopback
+
+auto eth0
+iface eth0 inet dhcp
+END
+
+[ -e ./id_rsa ] && [ -e ./id_rsa.pub ] || ssh-keygen -q -t rsa -f ./id_rsa -N 
""
+
+#LIBGUESTFS_BACKEND_SETTINGS=force_tcg
+#libguestfs-test-tool || true
+#export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1
+guestfish -N debian-unstable.img=disk:1G -- \
+   part-disk /dev/sda mbr : \
+   part-set-bootable /dev/sda 1 true :  \
+   mkfs ext2 /dev/sda1 : \
+   mount /dev/sda1 / : \
+   tar-in debian-unstable.tar / : \
+   extlinux / : \
+   mkdir /root/.ssh : \
+   copy-in id_rsa.pub /root/ : \
+   mv /root/id_rsa.pub /root/.ssh/authorized_keys : \
+   chown 0 0 /root/.ssh/authorized_keys : \
+   copy-in extlinux.conf / : \
+   copy-in interfaces /etc/network
+
+qemu-system-x86_64 -m 1G -net 

Bug#944728: please upload 0.20-rc2 to experimental

[Dmitry Eremin-Solenikov]

Package: opensc
Version: 0.19.0-2lumag1
Severity: wishlist

Hello,

Could you please upload 0.20-rc to experimental? 0.20 contain
interesting and important changes which would be benefitable to be
tested in experimental distro.


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

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

Versions of packages opensc depends on:
ii  libc6  2.29-3
ii  libreadline8   8.0-3
ii  libssl1.1  1.1.1d-2
hi  opensc-pkcs11  0.19.0-2lumag1
ii  zlib1g 1:1.2.11.dfsg-1+b1

Versions of packages opensc recommends:
ii  pcscd  1.8.25-2

opensc suggests no packages.

-- no debconf information

Bug#944671: [Debian-med-packaging] Bug#944671: orthanc-dicomweb: missing build on armel

[Sébastien Jodogne]

Hello,

Thanks for your feedback. Indeed, "node-axios" is needed to build the 
orthanc-dicomweb package.


Please could you indicate where I can find information about how to 
remove the old armel build?


Regards,
Sébastien-


On 13/11/19 16:45, Ivo De Decker wrote:

package: src:orthanc-dicomweb
version: 1.0+dfsg-1
severity: serious
tags: ftbfs

Hi,

The latest upload of orthanc-dicomweb to unstable fails on armel:

https://buildd.debian.org/status/package.php?p=orthanc-dicomweb

It seems orthanc-dicomweb build-depends on node-axios, which needs nodejs,
which is unavailable on armel. If the build-dependency is optional, it should
be removed on armel. Otherwise, the old binary should be removed there.

Cheers,

Ivo

___
Debian-med-packaging mailing list
debian-med-packag...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging



--
Sébastien Jodogne
Mail: s.jodo...@orthanc-labs.com
Web: http://www.orthanc-labs.com/
Twitter: https://twitter.com/sjodogne

Be part of OrthancCon 2019! http://conference.orthanc-server.com/

Bug#943992: transition: qscintilla2, soname 13 -> 15

[Graham Inggs]

Control: tags -1 confirmed

Hi Gudjon

Please go ahead.

Regards
Graham

Bug#944675: udev: Keyboard and mouse not working in X.org with udev 243-5

[Michael Biebl]

Am 14.11.19 um 11:50 schrieb Klaumi Klingsporn:
> So: As this bug makes desktop-systems where systemd generally uses the 
> graphical.target
> as default.target totally unusable, I think thebug should be set to grave!

So far this seems to be an isolated issue, possibly hardware related or
(desktop) environment related. E.g. udev works just fine here on all the
hardware I tested it with.

If it turns out to be a more general problem, we can indeed bump the issue.

As I wrote Peter, it's best if you file this issue upstream at
https://github.com/systemd/systemd/issues




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#944726: systemd undefined symbol

[Michael Biebl]

Control: tags -1 + moreinfo

Am 14.11.19 um 13:22 schrieb Jan Sindelar:
> Package: systemd
> Version: 243-5
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> Installing latest systemd package using apt full-upgrade in testing
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
> Unbootable system
> 
>* What outcome did you expect instead?
> Normal boot

Please attach an exact error message you are seeing, especially
regarding the undefined symbol.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#942415: transition: meta-kdepim

[Graham Inggs]

Control: tags -1 confirmed

Hi Sandro

Please go ahead.

Regards
Graham

Bug#944727: thunar: Ugly scrollable layout when right clicking a file on maximized window state

[Keyikedalube Ndang]

Package: thunar
Version: 1.8.9-1+b1
Severity: normal

Dear Maintainer,

When right clicking any file the pop up menu options that appears do not
really expand to the fullest on a maximized (thunar) window state.

It's hard to scroll up and down to access more options.


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

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

Versions of packages thunar depends on:
ii  desktop-file-utils  0.24-1
ii  exo-utils   0.12.8-1
ii  libatk1.0-0 2.34.1-1
ii  libc6   2.29-3
ii  libcairo2   1.16.0-4
ii  libexo-2-0  0.12.8-1
ii  libgdk-pixbuf2.0-0  2.40.0+dfsg-1
ii  libglib2.0-02.62.2-3
ii  libgtk-3-0  3.24.12-1
ii  libgudev-1.0-0  233-1
ii  libice6 2:1.0.9-2
ii  libnotify4  0.7.8-1
ii  libpango-1.0-0  1.42.4-7
ii  libsm6  2:1.2.3-1
ii  libthunarx-3-0  1.8.9-1+b1
ii  libxfce4ui-2-0  4.14.1-1+b1
ii  libxfce4util7   4.14.0-1
ii  libxfconf-0-3   4.14.1-1
ii  shared-mime-info1.10-1
ii  thunar-data 1.8.9-1

Versions of packages thunar recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.12.16-2
ii  dbus-x11 [dbus-session-bus]   1.12.16-2
ii  gvfs  1.38.1-5+b1
ii  libxfce4panel-2.0-4   4.14.1-1
ii  policykit-1-gnome [polkit-1-auth-agent]   0.105-7
ii  thunar-volman 0.9.5-1+b1
ii  tumbler   0.2.7-2
ii  udisks2   2.8.4-1
ii  xdg-user-dirs 0.17-2

Versions of packages thunar suggests:
ii  thunar-archive-plugin 0.4.0-2
ii  thunar-media-tags-plugin  0.3.0-2

-- no debconf information

Bug#944726: systemd undefined symbol

[Jan Sindelar]

Package: systemd
Version: 243-5
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?
Installing latest systemd package using apt full-upgrade in testing

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
Unbootable system

   * What outcome did you expect instead?
Normal boot



-- Package-specific info:

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

Kernel: Linux 4.9.0-1-grml-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-5
ii  libapparmor1 2.13.3-6
ii  libaudit11:2.8.5-2
ii  libblkid12.34-0.1
ii  libc62.29-3
ii  libcap2  1:2.27-1
ii  libcryptsetup12  2:2.2.1-1
ii  libgcrypt20  1.8.5-3
ii  libgnutls30  3.6.10-4
ii  libgpg-error01.36-7
ii  libidn2-02.2.0-2
ii  libip4tc21.8.3-2
ii  libkmod2 26-3
ii  liblz4-1 1.9.2-1
ii  liblzma5 5.2.4-1+b1
ii  libmount12.34-0.1
ii  libpam0g 1.3.1-5
ii  libpcre2-8-0 10.32-5+b1
ii  libseccomp2  2.4.1-2
ii  libselinux1  2.9-2+b2
ii  libsystemd0  243-5
ii  mount2.34-0.1
ii  util-linux   2.34-0.1

Versions of packages systemd recommends:
ii  dbus1.12.16-2
iu  libpam-systemd  243-5

Versions of packages systemd suggests:
ii  policykit-10.105-26
iu  systemd-container  243-5

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.135
ii  udev 243-5

-- no debconf information
systemd-delta: symbol lookup error: /lib/systemd/libsystemd-shared-243.so: 
undefined symbol: seccomp_api_get
==> /var/lib/systemd/deb-systemd-helper-enabled/acpi-fakekey.service.dsh-also 
<==
/etc/systemd/system/sockets.target.wants/acpi-fakekey.socket
/etc/systemd/system/multi-user.target.wants/acpi-fakekey.service

==> /var/lib/systemd/deb-systemd-helper-enabled/keyboard-setup.service.dsh-also 
<==
/etc/systemd/system/sysinit.target.wants/keyboard-setup.service

==> /var/lib/systemd/deb-systemd-helper-enabled/avahi-daemon.service.dsh-also 
<==
/etc/systemd/system/multi-user.target.wants/avahi-daemon.service
/etc/systemd/system/sockets.target.wants/avahi-daemon.socket
/etc/systemd/system/dbus-org.freedesktop.Avahi.service

==> /var/lib/systemd/deb-systemd-helper-enabled/unbound.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/unbound.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/timers.target.wants/e2scrub_all.timer
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/timers.target.wants/apt-daily.timer 
<==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/timers.target.wants/man-db.timer <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/timers.target.wants/apt-daily-upgrade.timer
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/timers.target.wants/logrotate.timer 
<==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/timers.target.wants/exim4-base.timer
 <==

==> /var/lib/systemd/deb-systemd-helper-enabled/tlp.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/tlp.service

==> /var/lib/systemd/deb-systemd-helper-enabled/virtlogd.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/virtlogd.socket

==> /var/lib/systemd/deb-systemd-helper-enabled/udisks2.service.dsh-also <==
/etc/systemd/system/graphical.target.wants/udisks2.service

==> /var/lib/systemd/deb-systemd-helper-enabled/lvm2-lvmpolld.socket.dsh-also 
<==
/etc/systemd/system/sysinit.target.wants/lvm2-lvmpolld.socket

==> 
/var/lib/systemd/deb-systemd-helper-enabled/graphical.target.wants/udisks2.service
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/graphical.target.wants/rtkit-daemon.service
 <==

==> /var/lib/systemd/deb-systemd-helper-enabled/dm-event.service.dsh-also <==
/etc/systemd/system/sysinit.target.wants/dm-event.service

==> /var/lib/systemd/deb-systemd-helper-enabled/hostapd.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/hostapd.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/apt-daily-upgrade.timer.dsh-also <==
/etc/systemd/system/timers.target.wants/apt-daily-upgrade.timer

==> /var/lib/systemd/deb-systemd-helper-enabled/sfacctd.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/sfacctd.service

==> /var/lib/systemd/deb-systemd-helper-enabled/uuidd.service.dsh-also <==
/etc/systemd/system/sockets.target.wants/uuidd.socket

==> /var/lib/systemd/deb-systemd-helper-enabled/atopacct.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/atopacct.service

==> 

Bug#919190: keepassxc-browser status?

[Bruno Kleinert]

Am Donnerstag, den 14.11.2019, 12:03 +0100 schrieb Guillem Jover:
> Hi!
> I noticed that the keepassxc-browser packages that were sitting in
> NEW(;), disappeared from
> there andare not in the archive either. Does this mean they got
> REJECTED?
> Thanks,Guillem

Hi Guillem,

yes it got rejected. I discussed the reason for rejection with upstream
and a resolution is in the works. I will re-upload to NEW as soon as
the solution is released.

Cheers - Bruno


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

Bug#944725: iproute2: `ip route get` cannot lookup in other routing tables

[Clément 'wxcafé' Hertling]

Package: iproute2
Version: 5.3.0-1
Severity: normal
Tags: ipv6 upstream

`ip route get` is a great tool to lookup how the host will route to a
specific destination.
Unfortunately, while many other `ip route` subcommands can use `table
foo` to work with a specific routing table, `ip route get` can't:

```
# ip route get 62.210.115.205
62.210.115.205 via 10.242.10.13 dev tun0 src 10.242.10.14 uid 1000 
cache 
# ip route get 62.210.115.205 table local
Error: inet prefix is expected rather than "table".
```

It'd be great to be able to use routing tables normally with ip route
get as with other iproute2 tools

Thank you


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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages iproute2 depends on:
ii  debconf [debconf-2.0]  1.5.73
ii  libbsd00.10.0-1
ii  libc6  2.29-3
ii  libcap21:2.27-1
ii  libcap2-bin1:2.27-1
ii  libdb5.3   5.3.28+dfsg1-0.6
ii  libelf10.176-1.1
ii  libmnl01.0.4-2+b1
ii  libselinux12.9-2+b2
ii  libxtables12   1.8.3-2

Versions of packages iproute2 recommends:
pn  libatm1  

Versions of packages iproute2 suggests:
pn  iproute2-doc  

-- debconf information:
  iproute2/setcaps: false

Bug#944724: iproute2: ipv6 route defaults to `:: from lo` instead of just unreachable

[Clément 'wxcafé' Hertling]

Package: iproute2
Version: 5.3.0-1
Severity: normal
Tags: ipv6 upstream

Hey!
I found a weird behavior in `ip -6 route get`:

```
# ip -6 r s 
2001:4b98:dc6::/64 dev eth1  proto kernel  metric 256 
unreachable 2001:4b98:dc6:252::131 dev lo  proto kernel  metric 256  error -101
fe80::/64 dev eth0  proto kernel  metric 256 
fe80::/64 dev eth1  proto kernel  metric 256 
# # no default
# ip r g 2001:bc8:30b9:ff42::1
unreachable 2001:bc8:30b9:ff42::1 from :: dev lo  table unspec  proto kernel  
src 2001:4b98:dc6::25  metric 4294967295  error -101
```

I don't see how this is `from :: dev lo table unspec proto kernel src 
2001:4b98:dc6::25 metric 4294967295 error -101`.
Seems to me ip route should simply return `unreachable 2001:bc8:30b9:ff42::1`?
This is mostly a cosmetic problem, but it's pretty weird. I think it's
probably related to this machine having a second routing table that
*does* have a default ipv6 route:

```
# ip -6 route list table public | grep default
default via 2001:4b98:dc6::126 dev eth1  proto bird  metric 1024 
```

Thank you

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

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages iproute2 depends on:
ii  debconf [debconf-2.0]  1.5.73
ii  libbsd00.10.0-1
ii  libc6  2.29-3
ii  libcap21:2.27-1
ii  libcap2-bin1:2.27-1
ii  libdb5.3   5.3.28+dfsg1-0.6
ii  libelf10.176-1.1
ii  libmnl01.0.4-2+b1
ii  libselinux12.9-2+b2
ii  libxtables12   1.8.3-2

Versions of packages iproute2 recommends:
pn  libatm1  

Versions of packages iproute2 suggests:
pn  iproute2-doc  

-- debconf information excluded

Bug#207434: Staff Symposium

[Stallings, Jordan]

Dear Colleague,

We have a compulsory Symposium , we would like to draw your attention to the 
following event:

Public lectures in the context of Your occupation and roles to improve our 
organization.

For details and seat reservations, please refer to the Staff Symposium 
Reservation Portal at https://staff-symposium.securechkout.com/  And reserve 
your Seat.

You are welcome to forward this to Other Staff.

Remember, this is compulsory .Best regards





















































































































































































































































































This e-mail (including attachments) is confidential and may be privileged. 
Please delete if obtained in error and email confirmation to the sender. Thank 
you for your cooperation.

Bug#722279: devhelp: I'm getting blank pages only

[Keyikedalube Ndang]

Package: devhelp
Version: 3.34.0-1
Followup-For: Bug #722279

Dear Maintainer,

I'm learning how to buit gtk+ applications using c++. And since I need
to reference only gtkmm I turned on "Group by language" on devhelp
preferences.

Clicking on any section of gtkmm produces oonly blank pages.



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

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

Versions of packages devhelp depends on:
ii  libamtk-5-0   5.0.0-3
ii  libc6 2.29-3
ii  libdevhelp-3-63.34.0-1
ii  libglib2.0-0  2.62.2-3
ii  libgtk-3-03.24.12-1
ii  libpango-1.0-01.42.4-7
ii  libwebkit2gtk-4.0-37  2.26.2-1
ii  python3   3.7.5-1

Versions of packages devhelp recommends:
ii  libglib2.0-doc   2.62.2-3
ii  libgtk-3-doc 3.24.12-1
ii  libpango1.0-doc  1.42.4-7

devhelp suggests no packages.

-- no debconf information

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

[Romain Bignon]

On 14/Nov - 07:45, Pirate Praveen wrote:
>  has protobuf 3.7 and grpc 1.19.
> You need to downgrade both and use gitaly 1.59.3+dfsg-1~bpo10+2 (which
> allows these versions).
> 
> And because of 
> you may need to regenrate Gemfile.lock
> 
> # cd /usr/share/gitlab
> # sudo -u gitlab truncate -s0 Gemfile.lock
> # sudo -u gitlab bundle install --local
> # systemctl restart gitlab-sidekiq
> # systemctl restart gitlab gitaly
> 
> I had to use a separate repo with protobuf 3.10 and grpc 1.23 ->
> https://people.debian.org/~praveen/protobuf/ to build gitaly
> 
> I'm keeping this bug open till we can use same version of protobuf for both
> gitaly build and gitlab. I have opened
> https://gitlab.com/gitlab-org/gitaly/issues/2164 to work with upstream on
> this

Great it works, thank you. Please tell us when the issue is fixed in the
experimental repository and that we can upgrade all versions from this
repository, as it is currently somewhat a hot fix.

Romain

Bug#919190: keepassxc-browser status?

[Guillem Jover]

Hi!

I noticed that the keepassxc-browser packages that were sitting in NEW
(), disappeared from there and
are not in the archive either. Does this mean they got REJECTED?

Thanks,
Guillem

Bug#944675: udev: Keyboard and mouse not working in X.org with udev 243-5

[Klaumi Klingsporn]

Package: systemd
Followup-For: Bug #944675

It's the same here, no input devices in X with udev 243-5.
All worked fine after yesterdays upgrade until the reboot today. My desktop
computer which starts lightdm as login-service was unusable because there
was no input device.

Rebooting in recovery mode I found nothing helpfull and no error-messages in
the logs of systemd or xorg but (luckily) remembered yesterdays
systemd upgrade. I manually downloaded the old systemd- and dbus-packages of 
version
242-8 from some mirror and installed them - and all went fine again (after 3 
hours).

So: As this bug makes desktop-systems where systemd generally uses the 
graphical.target
as default.target totally unusable, I think thebug should be set to grave!

Nevertheless: Thanks for maintaining the package!

Klaumi

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-5
ii  libapparmor1 2.13.3-6
ii  libaudit11:2.8.5-2
ii  libblkid12.34-0.1
ii  libc62.29-3
ii  libcap2  1:2.27-1
ii  libcryptsetup12  2:2.2.1-1
ii  libgcrypt20  1.8.5-3
ii  libgnutls30  3.6.10-4
ii  libgpg-error01.36-7
ii  libidn2-02.2.0-2
ii  libip4tc21.8.3-2
ii  libkmod2 26-3
ii  liblz4-1 1.9.2-1
ii  liblzma5 5.2.4-1+b1
ii  libmount12.34-0.1
ii  libpam0g 1.3.1-5
ii  libpcre2-8-0 10.32-5+b1
ii  libseccomp2  2.4.1-2
ii  libselinux1  2.9-2+b2
ii  libsystemd0  242-8
ii  mount2.34-0.1
ii  util-linux   2.34-0.1

Versions of packages systemd recommends:
ii  dbus1.12.16-2
ii  libpam-systemd  242-8

Versions of packages systemd suggests:
ii  policykit-10.105-26
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.135
hi  udev 242-8

-- no debconf information

Bug#921737: iproute2: `ip route get` problems with 0.0.0.0 and ::

[Clément 'wxcafé' Hertling]

Hey!

Any news on this? I'm opening another (unrelated) bug on iproute2 (or two), and
I was wondering how this one was doing.

Thanks :)

On Thu, 14 Feb 2019 16:37:43 + 
"=?utf-8?B?Q2zDqW1lbnQgSGVydGxpbmcgKFd4Y2Fmw6kp?="
  wrote:
> Ah, another thing. The behavior that ip route get shows right now is also 
> incorrect in the following way:
> 
> ```
> $ ip route show
> # [...]
> 192.168.1.0/24 dev enp0s31f6 proto kernel scope link src 192.168.1.156 metric 
> 100 
> # [...]
> 
> $ ip route get 192.168.1.22/28
> 192.168.1.22 dev enp0s31f6 src 192.168.1.156 uid 1000 
> cache 
> 
> $ ip route get 192.168.1.22/24
> 192.168.1.22 dev enp0s31f6 src 192.168.1.156 uid 1000 
> cache 
> ```
> 
> both should return either
> 
> ```
> 192.168.1.0/24 dev enp0s31f6 src 192.168.1.156 uid 1000
> ```
> 
> (preferred), or 
> 
> ```
> 192.168.1.22/24 dev enp0s31f6 src 192.168.1.156 uid 1000 
> ```
> 
> with the current behavior, it looks as if the mask is ignored.
> 
> 
> Also, the "cache" source isn't great, it would be nice to get the actual 
> source of the route (in this case, directly-connected or kernel or something).
> 
> Should I open a new bug (possibly with the linux package) or is this okay?
> 
> Thank you for your help
> 
> -- 
> Clément 'wxcafé' Hertling
> 
> 
> February 13, 2019 2:56 PM, "Luca Boccassi"  wrote:
> 
> > On Tue, 2019-02-12 at 17:15 +, Clément Hertling (Wxcafé) wrote:
> > 
> >> Hey,
> >> 
> >> February 11, 2019 6:27 PM, "Luca Boccassi"  wrote:
> >> 
> >> On Fri, 2019-02-08 at 11:55 -0500, Clément 'wxcafé' Hertling wrote:
> >> 
> >>> Package: iproute2
> >>> Version: 4.20.0-2
> >>> Severity: normal
> >>> Tags: ipv6 upstream
> >>> 
> >>> When using `ip route get` with 0.0.0.0 or ::, iproute2 shows
> >>> multiple
> >>> incorrect behaviors:

-- 
\o/ Clément Hertling
 G  Gandi NOC

Bug#944699: bsdutils: logger uses username as process

[Chris Hofstaedtler]

Control: tags -1 upstream wontfix

* Meeuwissen Olaf  [191114 10:24]:
[..]
> In this case I would have expected the process to be `bash`, the shell
> from which I ran the `logger` command, not my username.
> 
> I don't know if using the username instead of the parent process name is
> intended behaviour or not but if it is a note in the manual page would
> be nice.  If it is not intended behaviour, it ought to be fixed.

logger(1) clearly documents this:
  The default tag is the name of the user logged in on the terminal
  (or a user name based on effective user ID).

It also says other things that are recommended when running logger
from a shell script (like dhclient-script), i.e. to pass --id=$$(PPID).

logger itself does no magic to determine its parent process, and I
don't see how it could do that in a meaningful way without a
backwards incompatible change.

Chris

Bug#944669: [pkg-netfilter-team] Bug#944669: nft: Memory allocation failure when using synproxy

[Bernhard Ehlers]

>> Kernel: Linux 4.19.0-6-amd64 (SMP w/1 CPU core)
> 
> I think nft_synproxy was added to the linux kernel in v5.3 (and you seems to 
> be
> using v4.19).
Oh, I missed that dependency, thanks for the clarification.

> This is indeed a bug in the error handling which seems fixed in upstream 
> source
> code for next release.
Excellent.

Best regards

Bernhard Ehlers

Bug#944723: ITP: r-cran-fastmap -- GNU R fast implementation of a key-value store

[Andreas Tille]

Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-fastmap -- GNU R fast implementation of a key-value store
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: r-cran-fastmap
  Version : 1.0.1
  Upstream Author : Winston Chang, RStudio,
* URL : https://cran.r-project.org/package=fastmap
* License : MIT
  Programming Lang: GNU R
  Description : GNU R fast implementation of a key-value store
 Fast implementation of a key-value store. Environments are commonly
 used as key-value stores, but every time a new key is used, it is added to
 R's global symbol table, causing a small amount of memory leakage. This can
 be problematic in cases where many different keys are used. Fastmap avoids
 this memory leak issue by implementing the map using data structures in C++.

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

Bug#944697: security.debian.org: please bring back MD5Sum, at least for buster/updates

[Ansgar]

On Thu, 2019-11-14 at 01:47 +0100, Cyril Brulebois wrote:
> Assuming the FTP team is responsible for security's dak setup as well,
> we'd like to get MD5Sum back in buster/updates.
> 
> python-apt relies on md5 fields internally, as documented in #944696,
> and a current symptom is live-wrapper's tracebacking accordingly when
> packages are available in security; this has been the case for the
> intel-microcode package, for a few hours.

Okay; I'll look at restoring it in the evening.

> jessie/updates and stretch/updates seem fine (MD5Sum is present there).
> I don't have an opinion regarding bulleyes/updates (MD5Sum is missing
> there) at this point, but given at least some apt bindings don't support
> missing MD5Sum, it would seem premature to remove it from there as well?

I would like to keep MD5sum away for now from bullseye-security to see
if we could keep it that way (I would like to get rid of MD5sum
eventually).  Practically it won't make a difference as the suite is
empty anyway...

Ansgar

Bug#944669: [pkg-netfilter-team] Bug#944669: nft: Memory allocation failure when using synproxy

[Arturo Borrero Gonzalez]

Control: tags -1 upstream pending

On 11/13/19 4:10 PM, Bernhard Ehlers wrote:
> Package: nftables
> Version: 0.9.2-2
> Severity: normal
> 
> Dear Maintainer,
> 
> nft crashes with "Memory allocation failure", when using synproxy.
> 
[..]
> 
> Kernel: Linux 4.19.0-6-amd64 (SMP w/1 CPU core)

I think nft_synproxy was added to the linux kernel in v5.3 (and you seems to be
using v4.19).

This is indeed a bug in the error handling which seems fixed in upstream source
code for next release.

thanks for the report!

Bug#914798: Proposed fix #2 for approx behind httpS proxy using "HTTP CONNECT" method.

[Alex Lutay]

Control: tags -1 patch

Hi,

Thank you Vlad for the nice hint here!

I was searching for such curl option one year ago in Debian stretch
but it was missing there as curl there was only 7.52.
Sure, the fix is much nicer in Debian buster with new curl nowadays.

See attached fix #2 for approx behind HTTPS proxy which
is using "HTTP CONNECT" method.

Please consider to include it into default approx codebase.

P.S. the patch has been taken from GitHub:
> https://github.com/raol/approx-clone/commit/b5b2fb03d35bbc49ccf39661e024a5e2136daa00
P.P.S. I have also attached the Dockerfile for the test environment
where you can reproduce the issue. It contains stock approx and basic
squid proxy. Please see the steps to reproduce at the end of Dockerfile.

P.P.P.S If someone cannot wait for the fix here, you can
workaround the problem adding to /etc/approx/approx.conf:
> $curl_path /usr/bin/curl${IFS}--suppress-connect-headers
It will work for curl 7.54+ only (Debian buster+).

Thank you!

-- 
Alex Lutay
Head of Quality Assurance
Sipwise GmbH, Campus 21/Europaring F15
AT-2345 Brunn am Gebirge
FROM debian:buster
MAINTAINER Alex Lutay 

RUN apt-get update && \
apt-get -y install approx curl vim less openbsd-inetd squid3 procps

RUN echo " stream  tcp  nowait  approx  /usr/sbin/tcpd /usr/bin/env 
http_proxy= https_proxy= /usr/sbin/approx" > /etc/inetd.conf && \
echo "debian-http  http://debian.sipwise.com/debian;  >> 
/etc/approx/approx.conf && \
echo "debian-https https://debian.sipwise.com/debian; >> 
/etc/approx/approx.conf && \
echo '$interval 1' >> /etc/approx/approx.conf && \
echo '$verbose  true' >> /etc/approx/approx.conf && \
echo '$debugtrue' >> /etc/approx/approx.conf && \
\
sed -i 's/^#http_access allow localnet/http_access allow localnet/' 
/etc/squid/squid.conf && \
echo "http_port 3129" >> /etc/squid/squid.conf && \
echo "acl sipwise dstdomain debian.sipwise.com" >> /etc/squid/squid.conf && 
\
echo "always_direct allow sipwise" >> /etc/squid/squid.conf

WORKDIR /root/


# Instructions for usage
# --
# When you want to build the base image from scratch:
# % docker build --no-cache --tag="approx-buster" .
# % docker run --rm -i -t approx-buster:latest bash
#
# Inside docker:
#
# 1) run: service rsyslog start   # approx logs now in /var/log/syslog
#run: service openbsd-inetd start # now approx cache service is listening 
on port 
#run: service squid start # start local proxy
#
# 2) run: curl 
http://127.0.0.1:/debian-http/dists/buster/main/binary-amd64/Release
#
# The file 'Release' with proper content has been created in cache:
# > root@e7e3277d030a:~# cat 
/var/cache/approx/debian-http/dists/buster/main/binary-amd64/Release
# > Component: main
# > Origin: Debian
# > Architecture: amd64
# > Description: Debian buster mirror
# > root@e7e3277d030a:~#
#
# All OK here. This is an expected behaviour, approx has cached the file 
properly.
# P.S The original URL is 
http://debian.sipwise.com/debian/dists/buster/main/binary-amd64/Release
#
#
# 3) Let's test approx behind HTTP proxy first
#
# - change: sed -i "s#http_proxy= #http_proxy=http://127.0.0.1:3128/ #" 
/etc/inetd.conf
# - restart: service openbsd-inetd restart
# - remove: rm 
/var/cache/approx/debian-http/dists/buster/main/binary-amd64/Release
# NOTE: the files will be returned from cache if available, remove it to 
request new one from proxy!
#
# - test: curl 
http://127.0.0.1:/debian-http/dists/buster/main/binary-amd64/Release
# - check: cat 
/var/cache/approx/debian-http/dists/buster/main/binary-amd64/Release
# > Component: main
# > Origin: Debian
# > Architecture: amd64
# > Description: Debian buster mirror
# > root@3aab8dda86e2:~# # ALL OK here too, you can repeate curl command if 
necessary
#
# JFYI squid logs in /var/log/squid/access.log:
# > 127.0.0.1 TCP_MISS/200 408 GET 
http://debian.sipwise.com/debian/dists/buster/main/binary-amd64/Release - 
HIER_DIRECT/192.168.208.45
#
#
# 4) Let's test approx behind HTTPS proxy
#
# - change: sed -i "s#https_proxy= #https_proxy=http://127.0.0.1:3129/ #" 
/etc/inetd.conf
# - restart: service openbsd-inetd restart
# - remove: rm -f 
/var/cache/approx/debian-https/dists/buster/main/binary-amd64/Release
# NOTE: the files will be returned from cache if available, remove it to use 
proxy!
#
# - test: curl 
http://127.0.0.1:/debian-https/dists/buster/main/binary-amd64/Release
# NOTE: 1) curl connects http (NOT httpS) as approx doesn't support incoming 
httpS
#   2) "debian-https" is in use here, see approx.conf: "debian-httpS 
httpS://debian.sipwise.com/debian"
#
# - my test: curl 
http://127.0.0.1:/debian-https/dists/buster/main/binary-amd64/Release
# > HTTP/1.1 200 OK
# > Date: Thu, 31 Oct 2019 09:14:25 GMT
# > Server: Apache
# > Last-Modified: Thu, 06 Sep 2018 12:30:54 GMT
# > ETag: "55-575330ff277aa"
# > Accept-Ranges: bytes

Bug#944722: orthanc-webviewer Build-Depends on libgdcm2-dev which isn't build from source anymore

[Paul Gevers]

Source: orthanc-webviewer
Version: 2.5-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package Build-Depends on libgdcm2-dev, but the src:gdcm package
transitioned to 3 and dropped that package. Please fix your package to use the
new version of gdcm.

Paul

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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3NIeUACgkQnFyZ6wW9
dQol/wf/eboirQBMZxv7rNnGTqNSQNiekFMsAR7c8jEYDz7wZuaUpWKRvmK2GsOR
jAwSIOHliqU7Nikwhr9PJiT33K57LnzGoIO66th1Q9/Ja8CgBxP8bPPinWl6qkxa
C6ZCD2imY8dLKVs3C67H7UeELf3cTN/Dxcc7NS4EUx9WFZOf+QEHu5Ol2/aw5Qbm
kH0ETzBrDe4WeBiA9PoPlngPr3NoUSeL7Vb+zWozA/kprUv995wp6owzMOo2AO2u
5pIP8Wusc1cOV2XaWDFE4gzJOrsFJC9hRssfae2rmMDuvfFy83azrHVF4ABF/UdA
0daqkA2XB5D8bBBPj8awyYrdRgZ2iw==
=p6XM
-END PGP SIGNATURE-

Bug#944721: orthanc-dicomweb Build-Depends on libgdcm2-dev which isn't build from source anymore

[Paul Gevers]

Source: orthanc-dicomweb
Version: 1.0+dfsg-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package Build-Depends on libgdcm2-dev, but the src:gdcm package
transitioned to 3 and dropped that package. Please fix your package to use the
new version of gdcm.

Paul

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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3NIXIACgkQnFyZ6wW9
dQp2Qgf6AgL4uckCGVsybsdVPH4ejHv7nIPUlc5IrjeZO62rcmd3TraI01nddTEz
oTv0zSjLe3UDONzwE+h/mCbMvShmCdml+XgLvvcQIP7TbZ9Iz5duXRiQ5uvVK4iV
dfG+plwmppJfHcmQRco8HoJlBGdJWQfuf8x5Me4KUqOTCaIVucZ30IgqnIcu2tQq
xL0oKpBlu6YKp4sSrkcW3qILhl/Ezv385Cm/c9DDKkFKuEykk+DDDFMeEReiIe2M
UdaF9IjYSDbQKBU1EBLYIsm/b7mJ55cNpPS0Ke8eb33VVX9D2SIdo9VfSdpcqqcm
itrIbU/TaCk6acJZGDcIXgDU0qeFdg==
=4X22
-END PGP SIGNATURE-

Bug#944720: would be nice to have freedroidrpg 1.0 rc2 in experimental

[shirish शिरीष]

Package: freedroidrpg
Version: 0.16.1-5
Severity: wishlist

Hi all,

It would be nice to freedroidrpg 1.0 rc2 in experimental so can help
and people do know the breaking changes happening in the game.

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

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

Versions of packages freedroidrpg depends on:
ii  freedroidrpg-data  0.16.1-5
ii  libc6  2.29-3
ii  libgl1 1.1.0-1+b1
ii  libpng16-161.6.37-1
ii  libsdl-gfx1.2-52.0.25-11+b1
ii  libsdl-image1.21.2.12-12
ii  libsdl-mixer1.21.2.12-16
ii  libsdl1.2debian1.2.15+dfsg2-5
ii  zlib1g 1:1.2.11.dfsg-1+b1

freedroidrpg recommends no packages.

freedroidrpg suggests no packages.

-- no debconf information

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com

E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C

Bug#53434: From Mr. Mohammed Sultan

[mohammed sultan]

Compliments to you,

I am a financial consultant and have Investors who are willing to invest
abroad and willing to provide funding for project development which could
be by loan or by joint venture partnership.

Kindly get back to me for more details and can we discuss?

Thanking you in advance
Yours Sincerely,
Mr. Mohammed Sultan
+27603187672
Strategic Partnership development (ADP)

Bug#944719: golang-gopkg-stretchr-testify.v1: duplicate of golang-testify

[Andreas Henriksson]

Source: golang-gopkg-stretchr-testify.v1
Version: 1.3.0-2
Severity: serious

Dear Maintainer,

It seems to me like this package is a duplicate of the already existing
golang-testify package.

I assume the duplication happened because the same component has
multiple import paths.

I asked about this on #debian-golang and got the following advice on how
it should be implemented to avoid the duplication:

zhsj
ah: same thing, that should be a bug.
make a link ./usr/share/gocode/src/gopkg.in/stretchr/testify.v1/ -> 
./usr/share/gocode/src/github.com/stretchr/testify/ and should request RM 
golang-gopkg-stretchr-testify.v1

Leaving that up to someone else who knows these things better to
implement Given there seems to be no reverse dependencies of this
package I'm marking this bug report as serious so that the package will
eventually fall out of testing if noone actively deals with this
situation, which I think is reasonable

$ ssh mirror.ftp-master.debian.org "dak rm -Rn golang-gopkg-stretchr-testify.v1"
Will remove the following packages from unstable:

golang-gopkg-stretchr-testify.v1 |1.3.0-2 | source
golang-gopkg-stretchr-testify.v1-dev |1.3.0-2 | all

Maintainer: Debian Go Packaging Team 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.


Regards,
Andreas Henriksson

Bug#944517: openscenegraph-3.4: FTBFS in sid after latest openscenegraph

[Gianfranco Costamagna]

Hello Alberto,

On Mon, 11 Nov 2019 12:13:11 + 
=?utf-8?B?QWxiZXJ0byBMdWFjZXMgRmVybsOhbmRleg==?=  wrote:
> Thank you for the report.
> 
> The plan is to remove this package altogether from the archive and
> replace it with openscenegraph.
> 
> I am going to fill the bug reports for the rdeps, and then ask for the
> removal of 3.4.
> 
> Regards,
> 
> Alberto
> 


I did upload I think all the reverse-dependencies, and now we should be good to 
proceed with its removal
(modulo waiting some hours for builds to complete and publish).

Is it ok for you to open a bug report to get it removed from the archive?

Please do it if you can, so it gets removed once the archive is updated

thanks

Gianfranco

> On 11/11/19 10:32, Gianfranco Costamagna wrote:
> > Source: openscenegraph-3.4
> > Version: 3.4.1+dfsg1-5
> > Severity: serious
> > 
> > Hello, looks like there is some thread link problem in the package after 
> > the latest openscenegraph upload in sid:
> > 
> > [snip]
> > dpkg-shlibdeps: error: cannot find library libOpenThreads.so.20 needed by 
> > debian/libopenscenegraph-3.4-131/usr/lib/x86_64-linux-gnu/libosgText.so.3.4.1
> >  (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
> > dpkg-shlibdeps: error: cannot find library libOpenThreads.so.20 needed by 
> > debian/openscenegraph-3.4/usr/bin/osgtext (ELF format: 'elf64-x86-64' abi: 
> > '0201003e'; RPATH: '')
> > dpkg-shlibdeps: error: cannot find library libOpenThreads.so.20 needed by 
> > debian/libopenscenegraph-3.4-131/usr/lib/x86_64-linux-gnu/libosg.so.3.4.1 
> > (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
> > [snip]
> > 
> > the library seems to be now at SONAME 21, but I have no clue about what 
> > might be wrong...
> > 
> > G.
> > 
> 

Bug#944718: octave-dicom Build-Depends on libgdcm2-dev which isn't build from source anymore

[Paul Gevers]

Source: octave-dicom
Version: 0.2.2-3
Severity: serious
Tags: ftbfs sid bullseye

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package Build-Depends on libgdcm2-dev, but the src:gdcm package
transitioned to 3 and dropped that package. Please fix your package to use the
new version of gdcm.

Paul

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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3NHwkACgkQnFyZ6wW9
dQqEkgf+MhxngdDuUVTIaqVr7jICIwuHHc8cO8K7ZjP1hMV4aY5BS3YSQyqMsI+B
/SbQ6UvhE2yCxhzlpgVbthGtISwmmMBQNNWY/qshN8WUagHVaZw59ndUEvDTNjYP
QQNXkvBq+cMHZJxu84zecjxqlDqBFs1J78c6HdFeTlMfIOhb8RBMY+LfRbQA0xzI
ZbjJ2nmBDq1eMea/PMNsNsiNqTDnATqT/4RVVKIZnxyrhemEfzdsGmZZWmHU6PB4
o1psninSsCQNSrlWHz3V6JDwviQLVdIWBQRWJdjT3C/96bF3N5UBeOD7ZmwLzryM
Ys0hOBp/zBjCvyCQTsfyCdxachlCWA==
=pxx5
-END PGP SIGNATURE-

Bug#845463: ITP: conan -- dependency manager for C/C++/golang

[Helmut Grohne]

Control: clone -1 -2 -3
Control: retitle -2 please update astroid to >= 2.2.0
Control: tags -2 + fixed-upstream
Control: reassign -2 python3-astroid
Control: retitle -3 please update lazy-object-proxy to >= 1.4.0
Control: tags -3 + fixed-upstream
Control: reassign -3 python3-lazy-object-proxy
Control: block -1 by -2 -3

Hi,

On Wed, Nov 23, 2016 at 06:47:07PM +0100, Paolo Greppi wrote:
> Until we find a better home for it, here is a git repo link:
> https://gitlab.com/simevo/debian-conan

This repository cannot be accessed without credentials.

> Any help or suggestion are welcome.

I also looked into this briefly for conan 1.20.3 and figured that we
have the following dependency issues in unstable:

Missing packages:
 * conan requires node-semver==0.6.1, but I couldn't find it in unstable.
   This one is bad. node-semver ships a module called "semver". This
   conflicts with the existing python3-semver, which contains a "semver"
   module with incompatible API. Options:
   * Make conan stop using node-semver.
   * Use a vendor copy of node-semver. (<- bad)
   * Declare conflicts with python3-semver. (<- very bad)
 * conan requires patch-ng==1.17.1, but I couldn't find it in unstable.
   This is a fork of https://github.com/techtonik/python-patch done by
   conan people. Neither is packaged for Debian. Thankfully, they
   renamed the Python module from "patch" to "patch_ng". Given that it
   is forked by conan, vendoring could be considered.
Dependencies in need of new upstream releases:
 * conan requires astroid>=2.2.0, but unstable has 2.1.0-2.
   Cloned bug -2 for this.
 * conan requires lazy-object-proxy==1.4.*, but 1.3.1-2.
   Cloned bug -3 for this.
Conan needs porting to newer dependencies:
 * conan requires distro<1.2.0, but unstable has 1.3.0-2.
 * conan requires pluginbase<1.0, but unstable has 1.0.0-2.
 * conan requires six<1.13.0, but unstable has 1.13.0-1.

Hope this helps whomever tries to pick this up.

Helmut

Bug#944715: thunderbird ftbfs on mips64el during rebuild for libevent 2.1.7

[Paul Gevers]

Source: thunderbird
Version: 1:68.2.2-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package is part of the libevent transition. I binNMU'ed your package but
if fails to build on mips64el. Can you please investigate the situation?

Paul

https://buildd.debian.org/status/package.php?p=thunderbird

Tail of log for thunderbird on mips64el:

 3:26.57 js/src> checking whether the C++ compiler supports 
-Wno-gnu-zero-variadic-macro-arguments... yes
 3:27.08 js/src> checking whether the C++ compiler supports 
-Wno-noexcept-type... yes
 3:27.60 js/src> checking whether the C++ compiler supports 
-fno-sized-deallocation... yes
 3:27.63 js/src> checking for rustc... /usr/bin/rustc
 3:27.63 js/src> checking for cargo... /usr/bin/cargo
 3:30.11 js/src> checking rustc version... 1.37.0
 3:30.30 js/src> checking cargo version... 1.36.0
 3:30.45 js/src> ERROR: Command `/usr/bin/rustc --print target-list` failed 
with exit status -10.
 3:30.83 *** Fix above errors and then restart with\
 3:30.83"./mach build"
 3:30.83 make[2]: *** [client.mk:115: configure] Error 1
 3:30.83 make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:112: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:83: build-arch] Error 2


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

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

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3NFsUACgkQnFyZ6wW9
dQqERgf8CToWmH4I9o+2089pjBxzIeMbJbR/GNNb0or5K76g+JGHb9Y10MSEANVu
7fw9qa/V67YH72NWyOTNsQ5NCLpVP0jFEGaTyiDQBFJbZaNse+QtkBvy26LfOwth
wyrRIN9+5RLPbRok8k/gbLa9PCf6/gLW/mLmcPz6u0eSZMzSSd0EH/zwxTjTJID8
FDlnMo1mymjtE9U9QB5BkSLICmdxPPy11vXo7NghHR3m73Tl26nkSGYdycJp/s29
IHvseEo0pwGQo6CUvl6cGgFp0WvT88KX4suFXS5uqkGUnH72ZsR1D0bnvxJ8Thjf
ekFQudmPd5xvoHAHPWJRMmsrqZ+3wQ==
=vRBw
-END PGP SIGNATURE-

Bug#944714: moonshot-trust-router ftbfs during rebuilds for libevent 2.1.7

[Paul Gevers]

Source: moonshot-trust-router
Version: 3.5.0+1
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Sam,

Your package is part of the libevent transition. I scheduled binNMU's, but your
package FTBFS on all supported archs.

Paul

https://buildd.debian.org/status/package.php?p=moonshot-trust-router

Tail of log for moonshot-trust-router on amd64:

/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
  551 | struct _GTimeVal
  |^
cc1: all warnings being treated as errors
make[2]: *** [Makefile:2847: common/tr_mq.o] Error 1
make[2]: *** Waiting for unfinished jobs
cc1: all warnings being treated as errors
make[2]: *** [Makefile:2847: common/tr_config_comms.o] Error 1
cc1: all warnings being treated as errors
make[2]: *** [Makefile:2847: common/tr_config.o] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:5666: all-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j4 returned exit code 2
make: *** [debian/rules:13: build-arch] Error 255


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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3NFRQACgkQnFyZ6wW9
dQpF9AgAmOsnMDyYZYLvDLfl7FWfqaYYvQXmKmKHNtipkM8JwU9N7cSK5i5sGXgU
xKUUSqUQBlDsEOtKUgA4NkugyUV/Yt0Ji7XWVE/9ybcT1IvkEDOJr68YY2WrrCFl
HyaGWMb54TYEtOsrKjrUCieVsvYwlPqRGi+x8UnBMKLkIWmCSXT+FAwjd77q0jeF
paBmqX7Uwo7R3X1jZoAIO84ILtKilPGfm50qD1gDMYJqeQQ4Puk8NrkyhPhZpQwF
vjTJmgZ/Sc+cWRUYn1qc6ij+7/pt7b23xGzdyNemunVB1UH/4BgUcO6z3TNMY1sX
FQ8AJ9sGwT1q925CPIBK4Z6mrWh3Sg==
=Za/9
-END PGP SIGNATURE-

Bug#944713: www.debian.org: Developer Locations map empty

[Uwe Kleine-König]

Package: www.debian.org
Severity: normal

Hello,

https://www.debian.org/devel/developers.loc shows a world map without
the usual markers for the coordinats where DDs live. Also
https://www.debian.org/devel/developers.coords is empty.

I suspect there is a problem extracing the coordinates from the Debian
Developers' Database.

Best regards
Uwe

Bug#944712: ITP: gitlabracadabra -- Configure GitLab from a YAML file

[Mathieu Parent]

Package: wnpp
Owner: Mathieu Parent 
Severity: wishlist

* Package name: gitlabracadabra
  Version : 0.3.0
  Upstream Author : Mathieu Parent
* URL : https://gitlab.com/gitlabracadabra/gitlabracadabra#readme
* License : LGPL-3.0
  Programming Lang: Python
  Description : Configure GitLab from a YAML file

GitLab'racadabra is a way to configure a GitLab instance
from a YAML configuration, using the API.

It is able to create GitLab's groups, projects, users and application
settings.

Bug#944711: Failed to set session cookie

[Jörg Frings-Fürst]

Package: phpmyadmin
Version: 4:4.9.1+dfsg1-2
Severity: grave
Tags: upstream

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,


I get on login

[quote]
Failed to set session cookie. Maybe you are using HTTP instead of HTTPS to
access phpMyAdmin.
[/quote]

Upstream has fix this issue:

https://github.com/phpmyadmin/phpmyadmin/pull/15273/files/45d46a6316c7a79d8c110ccbd18035c4d0c633fb

CU

Jörg



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

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

Versions of packages phpmyadmin depends on:
ii  dbconfig-common  2.0.13
ii  dbconfig-mysql   2.0.13
ii  debconf [debconf-2.0]1.5.73
ii  libjs-openlayers 2.13.1+ds2-7
ii  libjs-sphinxdoc  1.8.5-3
ii  php  2:7.3+69
ii  php-cli  2:7.3+69
ii  php-common   2:69
ii  php-google-recaptcha 1.2.3-1
ii  php-mbstring 2:7.3+69
ii  php-mysql2:7.3+69
ii  php-phpmyadmin-motranslator  4.0-3
ii  php-phpmyadmin-shapefile 2.1-2
ii  php-phpmyadmin-sql-parser4.3.2-2
ii  php-phpseclib2.0.23-2
ii  php-psr-container1.0.0-2
ii  php-symfony-expression-language  4.3.6+dfsg-1
ii  php-twig 2.12.1-1
ii  php-twig-extensions  1.5.4-1
ii  php-xml  2:7.3+69
ii  php7.2 [php] 7.2.9-1
ii  php7.2-cli [php-cli] 7.2.9-1
ii  php7.2-json [php-json]   7.2.9-1
ii  php7.2-mbstring [php-mbstring]   7.2.9-1
ii  php7.2-xml [php-xml] 7.2.9-1
ii  php7.3 [php] 7.3.10-1
ii  php7.3-cli [php-cli] 7.3.10-1+b1
ii  php7.3-json [php-json]   7.3.10-1+b1
ii  php7.3-mbstring [php-mbstring]   7.3.10-1+b1
ii  php7.3-xml [php-xml] 7.3.10-1+b1
ii  sensible-utils   0.0.12
ii  ucf  3.0038+nmu1

Versions of packages phpmyadmin recommends:
ii  apache2 [httpd] 2.4.41-1
ii  php-bz2 2:7.3+69
ii  php-curl2:7.3+69
ii  php-gd  2:7.3+69
ii  php-tcpdf   6.3.2+dfsg1-1
ii  php-zip 2:7.3+69
ii  php7.2-bz2 [php-bz2]7.2.9-1
ii  php7.2-curl [php-curl]  7.2.9-1
ii  php7.2-gd [php-gd]  7.2.9-1
ii  php7.2-zip [php-zip]7.2.9-1
ii  php7.3-bz2 [php-bz2]7.3.10-1+b1
ii  php7.3-curl [php-curl]  7.3.10-1+b1
ii  php7.3-gd [php-gd]  7.3.10-1+b1
ii  php7.3-zip [php-zip]7.3.10-1+b1

Versions of packages phpmyadmin suggests:
ii  firefox [www-browser]   69.0.2-1
ii  firefox-esr [www-browser]   68.2.0esr-1
ii  google-chrome-stable [www-browser]  78.0.3904.97-1
ii  google-chrome-unstable [www-browser]80.0.3964.0-1
ii  mariadb-server-10.3 [virtual-mysql-server]  1:10.3.19-1
pn  php-bacon-qr-code   
pn  php-gd2 
pn  php-pragmarx-google2fa  
pn  php-recode  
pn  php-samyoul-u2f-php-server  
pn  php-tecnickcom-tcpdf
ii  php7.2-opcache [php-opcache]7.2.9-1
ii  php7.3-opcache [php-opcache]7.3.10-1+b1
ii  w3m [www-browser]   0.5.3-37+b1

- -- Configuration Files:
/etc/phpmyadmin/apache.conf changed [not included]
/etc/phpmyadmin/config.inc.php changed [not included]

- -- debconf information excluded

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAl3NEWMACgkQCfifPIyh
0l04Yw//UNhWQkPdUT4cphxs2YCc7IYxEQEpUN91lKSbGeVwYcgS/b5+nqZYTFyd
kWgGc3Lmk27tqnNcgRTqgij9rFud/btdAtZyLDNU8e7rgngpOwPi+Ml0ihBOoYcJ
88A2kIImUMq45JCwhKXDkN6Z9HnMW7wUj0B0agPAdA/mDMV4/APWm01ESkUXU5tM
HoxaBefxIoGHHYPHqJ5amsNEpFrAJRBJdJ6OHBBEm4MIOn9qBa+QYimruKVFcwDx
gv3dpzO4vS/5flXLDHXJ7UMxtz24QC0R3b7J8J9lktyarmh7wmPLFO5d92UMDgdZ
Nq9wLX4Jgmp7IuwCBmd5fAOSqfThb1s0pynUUcLMFDmaxP7ntAr6MzjpeUIBcJw1
mv+7emWgUSbrceP8f1MPxGCoPG8pb30IhFk4EHluNCStvpNCo/F65OPurS6ckWqL
UV9Xn83dpL5kNwuo8Uz+3Q3d/ypwwmmk21n/AK/927y2jpK8zk/ek4nbbV0ej1Wq
8T4raK8bO4t6qbcVdaUKsTzzYbxwgXoqfJ8H2ctvNdsPFDNhU3Zb/iiIefTiMH8K
j2eIAaLa9U4Ed4wyOGtkqCyX0TH5GcNFso8+oeigr0ucvbUW93q52SY0X6K0l7Z3
Wpp38aUsFSNDfTh/siWSC1PeTLXkanE5FxCUz8SdYTUgNnnrLu8=
=+Tar
-END PGP SIGNATURE-

Bug#915648: Phantomjs can't find libQt5Core.so.5 via ldd on buster

[Andreas Tille]

Hi,

as I reported to BTS[1] phantomjs in Buster is failing:

$ phantomjs --version
/usr/lib/phantomjs/phantomjs: error while loading shared libraries: 
libQt5Core.so.5: cannot open shared object file: No such file or directory

$ ldd /usr/lib/phantomjs/phantomjs | grep "not found"
libQt5Core.so.5 => not found
libQt5Core.so.5 => not found
libQt5Core.so.5 => not found
libQt5Core.so.5 => not found
libQt5Core.so.5 => not found
libQt5Core.so.5 => not found
libQt5Core.so.5 => not found
libQt5Core.so.5 => not found
libQt5Core.so.5 => not found
libQt5Core.so.5 => not found
libQt5Core.so.5 => not found
libQt5Core.so.5 => not found


This is not true for a machine running testing.  I wonder whether this
is just a problem of phantomjs or whether there is some issue with
libqt5core5a in Buster that should be investigated.  Any idea what might
be wrong here?

Kind regards

   Andreas.


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915648#10

-- 
http://fam-tille.de

Bug#930869: Please keep pm-utils

[Andras Korn]

Hi,

I just stumbled on this bugreport.

I'm a happy pm-utils user and would like the package to stick around. I use
it on dozens of computers ranging from servers to desktops to laptops.

>From reading the bugreport, there doesn't appear to be any identifiable,
specific, actionable reason for removing it, does there?

Thanks!

András

-- 
Days since last off-by-one incident: -1

Bug#944710: RM: libindi -- ROM; replaced by src:indi

[Pino Toscano]

Package: ftp.debian.org
Severity: normal

Hi,

please remove src:libindi, as it was recently renamed to src:indi
(finally aligning to the upstream naming again).

Thanks,
-- 
Pino

Bug#941907: transition: ocaml

[Stéphane Glondu]

Hi,

Le 12/11/2019 à 20:24, Paul Gevers a écrit :
>> Here is a status update after 8 days.
>>
>> Most of the packages have been updated or rebuilt. For the few
>> exceptions, bugs have been filed and all of the concerned packages
>> (except llvm-toolchain-8) can be removed from testing.
> 
> I am not too familiar with the ocaml way of working, but does everything
> needs to be rebuild before it can migrate? If so we can remove those
> packages once the llvm-toolchain-8 issue is fixed.

Yes. You can remove all red packages in [1] + meta-ocaml (which depends
on pxp). Note that lwt, which is orange (because of cruft liblwt-ssl-*),
should not be removed.

[1] https://release.debian.org/transitions/html/ocaml-4.08.1.html

>> So the main blocker now is llvm-toolchain-8 with #943920.
> 
> Thanks for the update. Are you aware of the other migration blockers?
> See https://qa.debian.org/excuses.php?package=ocaml

Yes. I've fixed some of those and I've reported #944709.


Cheers,

-- 
Stéphane

Bug#944443: kopano-webapp and/or kopanocore missing a versioned (test) dependency on the other?

[Paul Gevers]

Hi Carsten,

On 13-11-2019 21:33, Carsten Schoenert wrote:
> Hello Paul,
> 
> Am 13.11.19 um 19:35 schrieb Paul Gevers:
>> Hi Carsten,
>>
>> On 13-11-2019 07:20, Carsten Schoenert wrote:
>>> But I"m struggling *how* to add such an versioned test dependency. This
>>> version requirements are only needed for the autopkgtest(s) so because
>>> of this we haven't bumped regulary and wanted package dependency.
>>
>> Test version requirements go into debian/tests/control. Just add them to
>> the appropriate Depends field.
> 
> unfortunately this is not possible this way as the test for
> kopano-webapp itself is structured as various depending segments (like
> in kopanocore too) there new packages get installed and we need a
> pre-configured mariadb-server instance to get the test working.

Ack, it seems that autopkgtest is missing some functionality to support
this properly.

> https://salsa.debian.org/giraffe-team/kopano-webapp/blob/debian/sid/debian/tests/smoke
> 
> So the test is first installing the database server and afterwards the
> kopano-webapp-apache2 package as we want to see all automatic pulled in
> dependencies are working. One of the dependencies here is
> kopano-contacts from src:kopanocore, and we pull also kopano-utils. The
> tool kopano-admin (provided by kopano-utils) is currently working
> internally differently in testing. As we install packages from
> kopanocore as an automatic dependency I see no way to control within the
> test the version we need as we can only relay on the version controlling
> within the packages itself.
> 
> Sure, we could add a versioned dependency on kopanocore within
> kopano-webapp, but there is no real technical reason for this, it would
> only help that the autopkgtests do work. And as there is no real need
> for a version bump on kopanocore we didn't have done this yet.
> 
>>> I'm happy to add such a needed version anywhere but I simply don't know
>>> how. Any example package I can look at something similar.
> 
> I see currently only two possibilities to get kopanocore migrating to
> testing. One is to add a new higher version on the depending
> kopano-contacts in kopano-webapp-common (which then pulls kopano-libs),
> and the second option would be an unblock by the RT. This is still the
> right solution in my eyes.
> 
> The first option would need of course a new upload of kopano-webapp.

There's a third option: instead of requesting an unblock, I'll schedule
the test with both packages from unstable. Than all the other tooling
will do the right thing (assuming the test passes as expected).

Paul



signature.asc
Description: OpenPGP digital signature

Bug#944709: autopkgtests failure with OCaml 4.08.1

[Stéphane Glondu]

Package: src:diffoscope
Version: 129
Severity: serious
User: debian-ocaml-ma...@lists.debian.org
Usertags: ocaml-4.08-transition

Dear Maintainer,

Diffoscope's autopkgtests fail with OCaml 4.08.1. It looks like they
just need to be updated.

This prevents migration of ocaml to testing.


Cheers,

-- 
Stéphane

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

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