Bug#929224: apt-cacher-ng, debootstrap and deb.debian.org combination fails

2019-05-22 Thread Sean Whitton
Hello Eduard,

On Wed 22 May 2019 at 09:24PM +02, Eduard Bloch wrote:

> Uhm, I suggest you do what it says and read the manual?

I am not trying to use an https mirror.

I don't know what's responsible for the attempt to use https, but I want
to use http://deb.debian.org/debian, and one of apt-cacher-ng,
debootstrap or the deb.debian.org service is blocking doing that.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#929385: ITP: sequoia -- a modern OpenPGP implementation in Rust

2019-05-22 Thread Paul Wise
On Wed, May 22, 2019 at 12:05:27PM -0400, Daniel Kahn Gillmor wrote:

> Sequoia offers an OpenPGP interface in a modern, memory-safe language.
> It offers two command-line utilities (sq and sqv) in addition to its
> Rust library implementation.

Please note that there is a file conflict with ispell:

ispell: /usr/bin/sq

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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


Bug#929413: virtualbox-guest-dkms: vbox_fb.c:336: error: unterminated #else

2019-05-22 Thread Kentaro Hayashi
Package: virtualbox-guest-dkms
Version: 6.0.8-dfsg-5
Severity: important
X-Debbugs-Cc: haya...@clear-code.com,locutusofb...@debian.org

Dear Maintainer,

   * What led up to the situation?

 Upgrading virtualbox-guest-dkms (6.0.8-dfsg-4 => 6.0.8-dfsg-5) causes
 post-installation script subprocess returned error exit status 10

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

 % sudo apt upgrade -V

   * What was the outcome of this action?

Setting up virtualbox-guest-dkms (6.0.8-dfsg-5) ...
Removing old virtualbox-guest-6.0.8 DKMS files...

--
Deleting module version: 6.0.8
completely from the DKMS tree.
--
Done.
Loading new virtualbox-guest-6.0.8 DKMS files...
Building for 5.0.0-trunk-amd64
Building initial module for 5.0.0-trunk-amd64
Error! Bad return status for module build on kernel: 5.0.0-trunk-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/6.0.8/build/make.log for more
information.
dpkg: error processing package virtualbox-guest-dkms (--configure):
 installed virtualbox-guest-dkms package post-installation script subprocess
returned error exit status 10

   * What outcome did you expect instead?

 % sudo apt upgrade -V succeeds without error.

   * Additional information:

make.log contains the following error.

CC [M]  /var/lib/dkms/virtualbox-guest/6.0.8/build/vboxvideo/vbox_ttm.o
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxvideo/vbox_fb.c:336: error:
unterminated #else
#if LINUX_VERSION_CODE >= KERNEL_VERSION(5, 2, 0)

It seems that debian/patches/new-kernel-5.2.patch doesn't have correct
#if #endif pairs.



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

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

Versions of packages virtualbox-guest-dkms depends on:
ii  dkms  2.6.1-4

virtualbox-guest-dkms recommends no packages.

virtualbox-guest-dkms suggests no packages.

-- no debconf information


make.log
Description: Binary data


Bug#929418: screen: /run/screen isn't created

2019-05-22 Thread Phil Dibowitz
Package: screen
Version: 4.6.2-3
Severity: normal

Dear Maintainer,

After a fresh eboot, trying to create a screen session fails with:

  [phil@rider ~]$ screen
  Cannot make directory '/run/screen': Permission denied

It's easy enough to make a 'screen' dir with 777 perms as screen
expects, but the user shouldn't have to do this manually.

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

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

Versions of packages screen depends on:
ii  libc6 2.28-10
ii  libpam0g  1.3.1-5
ii  libtinfo6 6.1+20181013-2
ii  libutempter0  1.1.6-3

screen recommends no packages.

Versions of packages screen suggests:
pn  byobu | screenie | iselect  
ii  ncurses-term6.1+20181013-2

-- debconf information:
  screen/403-copy-failed:
* screen/410-upgrade:



Bug#929193: remove key 6FB2A1C265FFB764 from /usr/share/keyrings/debian-archive-keyring.gpg

2019-05-22 Thread Pradeep Nambiar

  
  
This can be closed.
I removed key the expired key 6FB2A1C265FFB764 from
  /usr/share/keyrings/debian-archive-keyring.gpg using the command
  and it seem to fix this issue.
sudo gpg --no-default-keyring
  --keyring=/usr/share/keyrings/debian-archive-keyring.gpg
  --delete-key 6FB2A1C265FFB764

Thanks
  




Bug#929419: unblock: tasksel/3.53

2019-05-22 Thread Holger Wansing
Package: release.debian.org
Usertags: unblock


I would like to request an unblock for version 3.53 of tasksel.


The changings contain:

- Remove bubulle from uploaders.
- Translation update for Korean
- Trivial syntax fixes in changelog file.


A corresponding debdiff is attached.



Thanks
Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076
diff -Nru tasksel-3.52/debian/changelog tasksel-3.53/debian/changelog
--- tasksel-3.52/debian/changelog	2019-04-02 22:48:50.0 +0200
+++ tasksel-3.53/debian/changelog	2019-05-23 05:57:05.0 +0200
@@ -1,4 +1,18 @@
+tasksel (3.53) unstable; urgency=medium
+
+  * Team upload.
+
+  [ Cyril Brulebois ]
+  * Remove Christian Perrier from Uploaders, with many thanks for all
+his contributions over the years! (Closes: #927489)
+
+  [ Updated debconf translations ]
+  * Korean (ko.po) by Changwoo Ryu.
+
+ -- Holger Wansing   Thu, 23 May 2019 05:57:05 +0200
+
 tasksel (3.52) unstable; urgency=medium
+
   * Team upload.
 
   [ Updated translations ]
@@ -7,6 +21,7 @@
  -- Holger Wansing   Tue, 02 Apr 2019 22:48:50 +0200
 
 tasksel (3.51) unstable; urgency=medium
+
   * Team upload.
 
   * Add firefox-l10n-ne-np to task-nepali-desktop. Closes: #922123
@@ -32,6 +47,7 @@
  -- Holger Wansing   Sun, 10 Mar 2019 23:12:54 +0100
 
 tasksel (3.50) unstable; urgency=medium
+
   * Team upload.
 
   [ Yves-Alexis Perez ]
@@ -49,6 +65,7 @@
  -- Holger Wansing   Fri, 08 Feb 2019 22:28:45 +0100
 
 tasksel (3.49) unstable; urgency=medium
+
   * Team upload
 
   [ Tetsutaro KAWADA ]
diff -Nru tasksel-3.52/debian/control tasksel-3.53/debian/control
--- tasksel-3.52/debian/control	2019-03-10 23:11:31.0 +0100
+++ tasksel-3.53/debian/control	2019-04-22 09:13:13.0 +0200
@@ -2,8 +2,7 @@
 Section: tasks
 Priority: optional
 Maintainer: Debian Install System Team 
-Uploaders: Christian Perrier ,
-   Nicolas Braud-Santoni 
+Uploaders: Nicolas Braud-Santoni 
 Standards-Version: 4.1.4
 Build-Depends: po-debconf, debhelper (>= 9), gettext, dpkg-dev (>= 1.9.0)
 Vcs-Browser: https://salsa.debian.org/installer-team/tasksel
diff -Nru tasksel-3.52/debian/po/ko.po tasksel-3.53/debian/po/ko.po
--- tasksel-3.52/debian/po/ko.po	2018-08-10 21:25:13.0 +0200
+++ tasksel-3.53/debian/po/ko.po	2019-05-23 05:42:53.0 +0200
@@ -1,13 +1,13 @@
 # Sunjae Park , 2005
-# Changwoo Ryu , 2005.
+# Changwoo Ryu , 2005, 2019.
 #
 msgid ""
 msgstr ""
 "Project-Id-Version: tasksel_debian\n"
 "Report-Msgid-Bugs-To: task...@packages.debian.org\n"
 "POT-Creation-Date: 2018-05-23 01:37+0200\n"
-"PO-Revision-Date: 2007-12-30 07:11+0900\n"
-"Last-Translator: Sunjae Park \n"
+"PO-Revision-Date: 2019-05-20 08:09+0900\n"
+"Last-Translator: Changwoo Ryu \n"
 "Language-Team: Korean \n"
 "Language: ko\n"
 "MIME-Version: 1.0\n"
@@ -47,7 +47,7 @@
 #. Description
 #: ../templates:3001
 msgid "This can be preseeded to override the default desktop."
-msgstr ""
+msgstr "이 설정에 대해 미리 설정 기능을 이용해 기본 데스크톱을 바꿀 수 있습니다."
 
 #. Type: title
 #. Description


Bug#625847: Newer unattended-upgrades mails even if there aren't packages on hold

2019-05-22 Thread Sean Whitton
control: retitle -1 Option to send an e-mail only if packages were upgraded
control: severity -1 normal

Hello,

unattended-upgrades in stretch would not send an e-mail unless packages
were actually upgraded.  The version in buster sends an e-mail daily
even if there is nothing to do -- no packages on hold, and nothing
upgradeable.

It would be great to have an option to restore the stretch behaviour.
That would also satisfy the original reporter of this bug, I believe.

I'm raising the severity since this feels like a regression since
stretch, but I understand if the maintainers disagree.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#869217: munpack must realize that some input is CRLF else will shatter UTF-8

2019-05-22 Thread 積丹尼 Dan Jacobson
munpack must realize some archives, e.g., .mhtmls, come in CRLF format,
otherwise, it will shatter UTF-8 when decoding! E.g.,
$ cat -vte
Content-Transfer-Encoding: quoted-printable^M$
...
jidanni=E7=9A=84=E4=BE=BF=E5=88=A9=E8=B2=BC - =E6=8B=89=E5=90=89=E4=^M$
=BC=8A=E6=98=9F=E7=90=83 raGii.net - Powered by Ragii.com!^M$



Bug#929415: ferm: domain eb ip match wrong rule

2019-05-22 Thread sergio
Package: ferm
Version: 2.4-1
Severity: normal

Dear Maintainer,

I've already reported this problem but looks like author ignores me:
https://github.com/MaxKellermann/ferm/issues/32



The correct command, that works:

ebtables -t broute -A BROUTING --protocol IPV4 --ip-source  --jump ACCEPT

in ferm form:

% cat test.conf
domain eb table broute chain BROUTING {
proto IPV4 mod ip source  ACCEPT;
}
% /usr/sbin/ferm --shell --remote test.conf
...
ebtables -t broute -A BROUTING --protocol IPV4 --match ip --source  --jump 
ACCEPT

trying ro run it will give:

Unknown argument: '--match



Bug#929420: libsieve FTCBFS: does not pass --host to ./configure

2019-05-22 Thread Helmut Grohne
Source: libsieve
Version: 2.2.6-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

libsieve fails to cross build from source, because it does not pass
--host to ./configure. The easiest way of fixing that - using
dh_auto_configure - makes libsieve cross buildable. Please consider
applying the attached patch.

Helmut
diff -u libsieve-2.2.6/debian/changelog libsieve-2.2.6/debian/changelog
--- libsieve-2.2.6/debian/changelog
+++ libsieve-2.2.6/debian/changelog
@@ -1,3 +1,9 @@
+libsieve (2.2.6-3) UNRELEASED; urgency=medium
+
+  * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure. (Closes: #-1)
+
+ -- Helmut Grohne   Thu, 23 May 2019 06:12:17 +0200
+
 libsieve (2.2.6-2) unstable; urgency=medium
 
   * QA upload.
diff -u libsieve-2.2.6/debian/rules libsieve-2.2.6/debian/rules
--- libsieve-2.2.6/debian/rules
+++ libsieve-2.2.6/debian/rules
@@ -32,8 +32,8 @@
 configure-stamp:
dh_testdir
test -d debian/orig || mkdir debian/orig 
-   cd src && (autoreconf -f -i && ./configure --prefix=/usr)
-   #cd src && ./configure --prefix=/usr
+   cd src && autoreconf -f -i
+   dh_auto_configure --sourcedirectory=src -- --libdir='$${prefix}/lib'
touch $@
 
 build: build-stamp


Bug#928809: lintian: suggest adding gitlab-ci file

2019-05-22 Thread Niels Thykier
Chris Lamb:
> Dmitry Bogatov wrote:
> 
>>> [..]  I just think that lintian should be less pro-active at adding
>>> checks for things that are far from accepted.
>>
>> That is why I propose introducing concept of "controversial" checks.
> 
> I think we are all violently agreeing here. 
> 
>> Having Lintian plainly reject such proposals would mean need in creation
>> of something like "lintian-unofficial"
> 
> (Personally, I doubt someone would fork Lintian, more likely its
> output would become less and less "trusted". But both outcomes suck.)
> 
> 
> Best wishes,
> 

There would be no need to fork lintian over this.  Lintian supports
third-party checks (via third-party lintian profiles).  With files in
the proper place, you can have:

  lintian --profile debian/unofficial ...

run lintian's built-in plus the extra unofficial checks.

Thanks,
~Niels



Bug#929417: debconf: Readline frontend should check that stdin is a tty (to fix Docker build freezes)

2019-05-22 Thread Anders Kaseorg

Package: debconf
Version: 1.5.72
Tags: patch

When building a Debian- or Ubuntu-based Docker container, installing
perl (so that Term::Readline is available) and a package that asks a
Debconf question causes the build to freeze with an interactive readline
prompt that cannot be answered:

$ cat Dockerfile
FROM debian:sid-20190506-slim
RUN apt-get update
RUN apt-get -y --no-install-recommends install perl keyboard-configuration

$ docker build .
[…]
Setting up keyboard-configuration (1.191) ...
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
debconf: falling back to frontend: Readline
Configuring keyboard-configuration
--

Please select the layout matching the keyboard for this machine.

  1. English (US)
[…]
  21. Other
Keyboard layout:

Docker builds are noninteractive, of course, and stdin is connected to 
/dev/null.  What seems to have happened here is that apt created a pty and 
connected stdout and stderr to it, but left stdin connected to /dev/null. 
The Readline frontend checked that there’s a controlling tty (there is), 
but failed to check that stdin is a tty (it’s not).  So it proceeded to 
wait for input from a tty that will never provide it.


(Obviously one can set DEBIAN_FRONTEND=noninteractive as a workaround, but 
that shouldn’t be necessary, and is in fact discouraged: 
https://docs.docker.com/engine/faq/#why-is-debian_frontendnoninteractive-discouraged-in-dockerfiles 
because it’s often set in ways that persist for longer than intended.)


I’ll let the maintainers decide whether it’s worth updating the translated 
error message to be more technically accurate.


--- a/Debconf/FrontEnd/Readline.pm
+++ b/Debconf/FrontEnd/Readline.pm
@@ -44,8 +44,7 @@ sub init {
$this->SUPER::init(@_);

# Yeah, you need a controlling tty. Make sure there is one.
-   open(TESTTY, "/dev/tty") || die gettext("This frontend requires a controlling 
tty.")."\n";
-   close TESTTY;
+   -t STDIN || die gettext("This frontend requires a controlling 
tty.")."\n";

$Term::ReadLine::termcap_nowarn = 1; # Turn off stupid termcap warning.
$this->readline(Term::ReadLine->new('debconf'));

Bug#929421: zip4j -- java library for zip files

2019-05-22 Thread merkys
Package: wnpp
Owner: Andrius Merkys 
Severity: wishlist

* Package name    : zip4j
  Version : 1.3.3+ds
  Upstream Author : , Srikanth Reddy Lingala
* URL : http://www.lingala.net/zip4j
* License : Apache-2.0
  Programming Lang: Java
  Description : java library for zip files
 Features:
  * Create, Add, Extract, Update, Remove files from a Zip file
  * Read/Write password protected Zip files
  * AES 128/256 Encryption/Decryption
  * Standard Zip Encryption/Decryption
  * Zip64 format
  * Store (No Compression) and Deflate compression method
  * Create or extract files from Split Zip files (Ex: z01, z02,...zip)
  * Unicode file names
  * Progress Monitor

Remark: This package is to be maintained with Debian Java Maintainers at
   https://salsa.debian.org/java-team/zip4j

This package is required by deepboof, which I intend to package.

-- 
Andrius Merkys
Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325
LT-10257 Vilnius, Lithuania



Bug#929411: dstat: upstream discontinued due to reimplementation by RedHat

2019-05-22 Thread Otto Kekäläinen
> Upstream wrote on github that they are discontinuing the dstat project
> because RedHat reimplemented it and used the same name.
>
> https://github.com/dagwieers/dstat/issues/170
> https://www.redhat.com/en/blog/implementing-dstat-performance-co-pilot
> https://news.ycombinator.com/item?id=19986646

The project wasn't maintained anyway, so this makes no practical
difference. There was good open pull requests unhandled for years
(e.g. https://github.com/dagwieers/dstat/pull/96 since 2015) that
never got reviewed or merged. I offered to help with the project 6
months ago but got no response from the original author whatsoever,
until yesterday when he locked down all issues and thus prevented any
further communications (see
https://github.com/dagwieers/dstat/issues/158).

I have also contacted the current Debian maintainer last year and have
offered to maintain the package in Debian, but turns out this
maintainer was kicked out from Debian and thus not open for
collaboration.

I still use the tool and throwing away the current Python code base
would not seem to be like smart idea...



Bug#929412: Support mhtml / mht

2019-05-22 Thread 積丹尼 Dan Jacobson
Package: unar
X-Debbugs-Cc: Dag Ågren 
Version: 1.10.1-2+b4
Severity: wishlist
File: /usr/bin/unar

Would be great to support unarchiving mhtml files.

(I currently use

test $# -eq 1 ||{ echo $0: One arg please. 1>&2; exit 42;}
perl -pwle 's/\r$//;' $@| # Workaround for 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869217
/usr/bin/munpack -t 2>&1|
perl -nle '
# Workaround for https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=222582
use strict;
use warnings FATAL => q(all);
print STDERR;
if (m@^(part\d+) \((?:text|image)/(\w+)\)$@) {
my $f = $1 . "." . ( $2 eq "plain" ? "txt" : $2 );
if ( -f $f ) { print STDERR "$f exists already, skipping"; next }
else { die $! unless rename $1, $f }
print "$1->$f";
}

but I didn't try https://www.volkerschatz.com/unix/uware/unmht.html .)



Bug#929414: dbconfig-common: Assumes pgsql ident means dbuser must exist as a local user

2019-05-22 Thread Matthew Gabeler-Lee
Package: dbconfig-common
Version: 2.0.11
Severity: normal

dbconfig-common assumes that, if "ident" auth is used with postgresql, then
the database user must also exist as a local user.

This is ... not true.

The "peer" auth in postgresql just means that the identity of the connecting
user authenticates for the database user.  There is no requirement that the
two must be the same.

Given a setup like this, upgrades fail in strange ways:

runuser: options --{shell,fast,command,session-command,login} and --user 
are mutually exclusive

Running with `dbc_debug` shows a more useful sequence (long command lines
trimmed because it's only the start that is important):

creating database backup in /var/cache/dbconfig-common/backups/...
runuser --user  -- /bin/sh -c "...
unable to connect to postgresql server.
dumping database as user failed, retrying with administrator credentials.  
dbc_get_admin_pass() .
runuser --user postgres -- /bin/sh -c "...
runuser --user postgres -- /bin/sh -c "...
_dbc_apply_upgrades() 19.2.
applying upgrade sql for 18.12+dfsg-1 -> 19.2.
runuser --user  -- /bin/sh -c "...
error encountered processing /usr/share/dbconfig-common/data/...
runuser: options --{shell,fast,command,session-command,login} and --user 
are mutually exclusive

It doesn't help that `runuser` is giving a wildly misleading error here, but
the root cause is the `_dbc_psql_local_username` function having this logic:

if [ "${dbc_dbuser:-}" ] && id $dbc_dbuser >/dev/null 2>&1; then
echo $dbc_dbuser
return 0
else
dbc_error="ident method specified but local account doesn't 
exist. mapping isn't supported"
return 1
fi

This is exacerbated by the call sites for this function not checking for
errors, and blithely passing the empty username string to `runuser`.

Ironically, in this configuration (system user is providing the real
authentication for connection over a unix socket), it seems that selecting
password auth and giving a bogus password may work, since pgsql won't be
looking at the password at all.

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'testing-debug'), (500, 'stable'), (500, 
'oldstable'), (490, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.0.0-trunk-amd64 (SMP w/16 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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dbconfig-common depends on:
ii  debconf [debconf-2.0]  1.5.71
ii  ucf3.0038+nmu1

dbconfig-common recommends no packages.

Versions of packages dbconfig-common suggests:
ii  dbconfig-mysql2.0.11
ii  dbconfig-pgsql2.0.11
ii  dbconfig-sqlite3  2.0.11

-- debconf information excluded



Bug#929416: ferm: using legacy tools

2019-05-22 Thread sergio
Package: ferm
Version: 2.4-1
Severity: normal

Dear Maintainer,

1. With ebtables set to ebtables-nft (via alternatives):

# cat /etc/ferm/printer.ferm
@def $PrinterMAC = MAC;

domain eb table broute chain BROUTING {
daddr $PrinterMAC {
DROP;
}
}

# ferm /etc/ferm/printer.ferm
Policy ACCEPT not allowed for user defined chains.
Cannot rollback domain 'eb' because there is no ebtables-restore



2. With iptables set to iptables-nft (via alternatives) I've discovered
   NULL pointer dereference: https://bugzilla.kernel.org/show_bug.cgi?id=203681
   (Yes, this is not a ferm issue)


The question is: should ferm call *-legacy tools directly regardless
alternative settings?   



Bug#928923: Acknowledgement (linux-image-4.19.0-4-cloud-amd64: reports different NIC name than linux-image-amd64 on virtio-net)

2019-05-22 Thread Xinyue Lu
To reproduce this issue, one must set Machine Type in VM Hardware to
"q35" instead of the default i440fx.

The issue can still be reproduced on linux-image-4.19.0-5-cloud-amd64 4.19.37-3.



Bug#929005: superkb FTCBFS: upstream build system hard codes build architecture tools

2019-05-22 Thread Octavio Alvarez

On 5/22/19 7:59 AM, Helmut Grohne wrote:

On Wed, May 22, 2019 at 05:35:08AM -0500, Octavio Alvarez wrote:

First, in commit b364c89897 [1] I moved the help text outside of main.c into
a separate header file.


It seems to me that this commit misses the addition of the separate
header file.


Thank you for catching that. I added commit cf9a9bb3 [1] with the 
missing file.


Octavio.

[1] fix: added forgotten main-help-message.h
https://gitlab.com/alvarezp2000/superkb/commit/cf9a9bb303036085180181808078abe6ac652aff



Bug#929224: apt-cacher-ng, debootstrap and deb.debian.org combination fails

2019-05-22 Thread Eduard Bloch
Hallo,
* Sean Whitton [Sun, May 19 2019, 08:08:07AM]:

> I thought that the problem is that apt-cacher-ng is not able to resolve
> SRV records.  However, I'm not so sure about that now.  debootstrap uses
> wget to download stuff, so I tried this:
>
> root@iris:/srv/chroot>http_proxy=http://localhost:3142 wget 
> http://deb.debian.org/debian/dists/sid/Release
> URL transformed to HTTPS due to an HSTS policy
> --2019-05-19 07:54:37--  https://deb.debian.org/debian/dists/sid/Release
> Resolving localhost (localhost)... ::1, 127.0.0.1
> Connecting to localhost (localhost)|::1|:3142... connected.
> Proxy tunneling failed: CONNECT denied (ask the admin to allow HTTPS 
> tunnels)Unable to establish SSL connection.

Uhm, I suggest you do what it says and read the manual?

https://www.unix-ag.uni-kl.de/~bloch/acng/html/howtos.html#ssluse

The "laissez-faire method": in acng.conf (or related) configure the 
PassThroughPattern option to contain a regex like .* and configure the clients 
to use apt-cacher-ng as HTTP proxy and let the clients connect to https URLs 
"as usual". Some limited access control can be achieved through adjustment of 
the regular expression (.* permits access to any host and any port, including 
443 for https). Data is not cached on the server.

Also modified by debconf: dpkg-reconfigure -plow apt-cacher-ng

Best regards,
Eduard.



Bug#929401: debian-security-support: Updated Swedish translation

2019-05-22 Thread Andreas Ronnquist
Package: debian-security-support
Severity: wishlist
Tags: l10n

Dear Maintainer,

Please find attached a Swedish translation of the
debian-security-support package.

-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages debian-security-support depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.72
ii  gettext-base   0.19.8.1-9

debian-security-support recommends no packages.

debian-security-support suggests no packages.


-- Andreas Rönnquist
gus...@debian.org
# Swedish translations for debian-security-support package
# Svenska översättningar för paket debian-security-support.
# Copyright (C) 2019 Christoph Biedl
# This file is distributed under the same license as the debian-security-support package.
# Andreas Rönnquist , 2019.
#
msgid ""
msgstr ""
"Project-Id-Version: \n"
"Report-Msgid-Bugs-To: debian-security-supp...@packages.debian.org\n"
"POT-Creation-Date: 2016-06-07 12:13+0200\n"
"PO-Revision-Date: 2019-05-22 15:31+0200\n"
"Last-Translator: Andreas Rönnquist \n"
"Language-Team: Swedish\n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Poedit 1.8.11\n"

#: ../check-support-status.in:24
#, sh-format
msgid ""
"Unknown DEBIAN_VERSION $DEBIAN_VERSION. Valid values from $DEB_LOWEST_VER_ID "
"and $DEB_NEXT_VER_ID"
msgstr ""
"Okänd DEBIAN_VERSION $DEBIAN_VERSION. Giltiga värden från $DEB_LOWEST_VER_ID "
"och $DEB_NEXT_VER_ID"

#: ../check-support-status.in:63
msgid "Failed to parse the command line parameters"
msgstr "Misslyckades att tolka kommandoradsparametrarna"

#: ../check-support-status.in:72
#, sh-format
msgid "$name version $VERSION"
msgstr "$name version $VERSION"

#: ../check-support-status.in:101
msgid "E: Internal error"
msgstr "E: Internt fel"

#: ../check-support-status.in:117
msgid "E: Need a --type if --list is given"
msgstr "E: Behöver --type om --list är given"

#: ../check-support-status.in:130
#, sh-format
msgid "E: Unknown --type '$TYPE'"
msgstr "E: Okänd --type '$TYPE'"

#: ../check-support-status.in:152
msgid "E: Cannot detect dpkg version, assuming wheezy or newer"
msgstr "E: Kan inte detektera dpkg-version, antar wheezy eller nyare"

#: ../check-support-status.in:282
msgid "Future end of support for one or more packages"
msgstr "Framtida slut på support för ett eller flera paket"

#: ../check-support-status.in:285
msgid ""
"Unfortunately, it will be necessary to end security support for some "
"packages before the end of the regular security maintenance life cycle."
msgstr ""
"Tyvärr kommer det att bli nödvändigt att avsluta säkerhetsstödet för vissa "
"paket innan slutet på livscykeln för regelbundet säkerhetsunderhåll."

#: ../check-support-status.in:288 ../check-support-status.in:298
#: ../check-support-status.in:308
msgid "The following packages found on this system are affected by this:"
msgstr "De följande paketen på detta system påverkas av detta:"

#: ../check-support-status.in:292
msgid "Ended security support for one or more packages"
msgstr "Avslutat säkerhetsstöd för ett eller flera paket"

#: ../check-support-status.in:295
msgid ""
"Unfortunately, it has been necessary to end security support for some "
"packages before the end of the regular security maintenance life cycle."
msgstr ""
"Tyvärr har det blivit nödvändigt att avsluta säkerhetsstödet för vissa paket "
"innan slutet på livscykeln för regelbundet säkerhetsunderhåll."

#: ../check-support-status.in:302
msgid "Limited security support for one or more packages"
msgstr "Begränsad säkerhetsstöd för ett eller flera paket"

#: ../check-support-status.in:305
msgid ""
"Unfortunately, it has been necessary to limit security support for some "
"packages."
msgstr ""
"Tyvärr har det blivit nödvändigt att begränsa säkerhetsstödet för vissa "
"paket."

#: ../check-support-status.in:320
#, sh-format
msgid "* Source:$SRC_NAME, will end on $ALERT_WHEN"
msgstr "* Source:$SRC_NAME, kommer att avslutas $ALERT_WHEN"

#: ../check-support-status.in:323
#, sh-format
msgid "* Source:$SRC_NAME, ended on $ALERT_WHEN at version $ALERT_VERSION"
msgstr "* Source:$SRC_NAME, avslutades $ALERT_WHEN med version $ALERT_VERSION"

#: ../check-support-status.in:326
#, sh-format
msgid "* Source:$SRC_NAME"
msgstr "* Source:$SRC_NAME"

#: ../check-support-status.in:330
#, sh-format
msgid "  Details: $ALERT_WHY"
msgstr "  Detaljer: $ALERT_WHY"

#: ../check-support-status.in:333
msgid "  Affected binary package:"

Bug#929400: apng2gif FTCBFS: debian/rules hard codes gcc

2019-05-22 Thread Helmut Grohne
Source: apng2gif
Version: 1.8-0.1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

apng2gif fails to cross build from source, because debian/rules hard
codes the build architecture compiler gcc. The easiest way of fixing
this - using dpkg's buildtools.mk - makes apng2gif cross buildable.
Please consider applying the attached patch.

Helmut
diff --minimal -Nru apng2gif-1.8/debian/changelog apng2gif-1.8/debian/changelog
--- apng2gif-1.8/debian/changelog   2018-10-27 14:15:49.0 +0200
+++ apng2gif-1.8/debian/changelog   2019-05-22 22:24:11.0 +0200
@@ -1,3 +1,10 @@
+apng2gif (1.8-0.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: Seed CC from dpkg's buildtools.mk. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 22 May 2019 22:24:11 +0200
+
 apng2gif (1.8-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru apng2gif-1.8/debian/rules apng2gif-1.8/debian/rules
--- apng2gif-1.8/debian/rules   2018-10-27 14:15:49.0 +0200
+++ apng2gif-1.8/debian/rules   2019-05-22 22:24:10.0 +0200
@@ -2,7 +2,7 @@
 
 PACKAGE = apng2gif
 BIN= $(PACKAGE)
-CC := gcc
+-include /usr/share/dpkg/buildtools.mk
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 CFLAGS += -Wall -pedantic


Bug#928969: stterm: incorrect rendering of cyrillic letters with Terminus

2019-05-22 Thread Dmitry Bogatov


[2019-05-19 23:49] Paride Legovini 
> I tried with xterm and sakura, the Cyrillic string renders exactly as
> in stterm, with the correct character width and spacing.

> Let me know if there is anything else I can try.

Okay. I prepared kvm virtual machine image, that you can download
from "people.debian.org/~kaction/stterm-bug.img.xz".

After it boots, it shows Xdm prompt. Log is as "user:useruser". You will
have default "dwm" instance. Press Alt-Shift-Enter and some terminal
will appear.

There is ~user/I-Will-Show-You.sh script, that starts stterm to show
difference between cyrillic "Привет, мир!" and ascii "Hello, world!".

Hope, you will see same thing as me. After that, you can get root
permission with su and "root:rootroot".
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --



Bug#928809: lintian: suggest adding gitlab-ci file

2019-05-22 Thread Dmitry Bogatov


[2019-05-20 15:45] Mattia Rizzolo 
> On Fri, May 17, 2019 at 08:58:03AM +0100, Chris Lamb wrote:
> [...]
> > (This kind of conversation always makes me wonder if we need another
> > level of "extra pendatic" that people need to opt into... *g*)
>
> Nah.  I just think that lintian should be less pro-active at adding
> checks for things that are far from accepted.

That is why I propose introducing concept of "controversial" checks.

Having Lintian plainly reject such proposals would mean need in creation
of something like "lintian-unofficial", that would be wasted technical
effort on setting up new source package, re-using Lintian library and so
on.
-- 
Note, that I send and fetch email in batch, once every 24 hours.
 If matter is urgent, try https://t.me/kaction
 --



Bug#750781: not fixed

2019-05-22 Thread sergio
While the dirty hack of editing /lib/systemd/system/getty@.service works,

the right way of creating /etc/systemd/system/getty@.service works only for 
tty1:

$ ps aux | grep getty
... /sbin/agetty -f /etc/issue.linuxlogo -o -p -- \u --noclear tty1 linux
... /sbin/agetty -o -p -- \u --noclear tty2 linux
... /sbin/agetty -o -p -- \u --noclear tty3 linux
... /sbin/agetty -o -p -- \u --noclear tty4 linux
... /sbin/agetty -o -p -- \u --noclear tty5 linux
... /sbin/agetty -o -p -- \u --noclear tty6 linux

-- 
sergio.



Bug#929407: ruby-inherited-resources: /usr/lib/ruby/vendor_ruby/generators/rails/USAGE is already shipped by ruby-active-model-serializers

2019-05-22 Thread Andreas Beckmann
Package: ruby-inherited-resources
Version: 1.9.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Preparing to unpack .../ruby-inherited-resources_1.9.0-1_all.deb ...
  Unpacking ruby-inherited-resources (1.9.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-inherited-resources_1.9.0-1_all.deb (--unpack):
   trying to overwrite '/usr/lib/ruby/vendor_ruby/generators/rails/USAGE', 
which is also in package ruby-active-model-serializers 0.10.8-1
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-inherited-resources_1.9.0-1_all.deb


cheers,

Andreas


ruby-active-model-serializers=0.10.8-1_ruby-inherited-resources=1.9.0-1.log.gz
Description: application/gzip


Bug#929392: php-horde-image 2.5.3-1: autopkgtest regression

2019-05-22 Thread Steve Langasek
Source: php-horde-image
Version: 2.5.3-1
Severity: important
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan

Dear Mathieu,

The autopkgtests for php-horde-image 2.5.3-1 have never passed; they always
fail with this error:

autopkgtest [23:42:23]: test phpunit: [---
PHP Fatal error:  Uncaught Error: Class 'Horde_Image_Exif_TestBase' not found 
in 
/tmp/autopkgtest-lxc._0g2am78/downtmp/build.ir3/src/Horde_Image-2.5.3/test/Horde/Image/Exif/BundledTest.php:11
Stack trace:
#0 /usr/share/php/PHPUnit/Util/FileLoader.php(57): include_once()
#1 /usr/share/php/PHPUnit/Util/FileLoader.php(45): 
PHPUnit\Util\FileLoader::load('/tmp/autopkgtes...')
#2 /usr/share/php/PHPUnit/Framework/TestSuite.php(540): 
PHPUnit\Util\FileLoader::checkAndLoad('/tmp/autopkgtes...')
#3 /usr/share/php/PHPUnit/Framework/TestSuite.php(618): 
PHPUnit\Framework\TestSuite->addTestFile('/tmp/autopkgtes...')
#4 /usr/share/php/PHPUnit/Runner/BaseTestRunner.php(70): 
PHPUnit\Framework\TestSuite->addTestFiles(Array)
#5 /usr/share/php/PHPUnit/TextUI/Command.php(183): 
PHPUnit\Runner\BaseTestRunner->getTest('.', '', Array)
#6 /usr/share/php/PHPUnit/TextUI/Command.php(162): 
PHPUnit\TextUI\Command->run(Array, true)
#7 /usr/bin/phpunit(42): PHPUnit\TextUI\Command::main()
#8 {main}
  thrown in 
/tmp/autopkgtest-lxc._0g2am78/downtmp/build.ir3/src/Horde_Image-2.5.3/test/Horde/Image/Exif/BundledTest.php
 on line 11
autopkgtest [23:42:23]: test phpunit: ---]

  (https://ci.debian.net/packages/p/php-horde-image/unstable/amd64/)

This is a regression vs the previous version of php-horde-image, 2.5.2-3,
whose autopkgtests passed.

Since php-horde-image 2.5.3-1 was uploaded to Debian before autopkgtest
regressions became blocking for testing migration, 2.5.3-1 is in testing and
will be included in the next Debian release.  However, autopkgtest
regressions have always been blocking in Ubuntu, where this test also fails,
so FYI php-horde-image 2.5.3-1 will not be included in an Ubuntu release
until this is resolved.

(Also, obviously if the tests are consistently failing, this prevents you
from using this as an effective CI gate for Debian testing, so dependencies
of php-horde-image could at any point cause php-horde-image to have runtime
regressions in Debian testing.)

Regards,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature


Bug#929393: rust-lazy-static: please upgrade to 0.13.0

2019-05-22 Thread Daniel Kahn Gillmor
Package: src:rust-lazy-static
Severity: wishlist
Blocks: 929385 by -1
Control: tags -1 + patch

sequoia-openpgp wants lazy_static version 0.13.0.  we only have 0.11.0
in debian right now.

If i look for the dependencies, though:

aptitude '~Dlibrust-lazy-static'

There are 36 of them including cargo itself.  I'm not sure how to
efficiently and safely test them all to ensure that the upgrade doesn't
break anything, so rather than just applying the patch below, i'm
proposing it here.

  --dkg

From 55e59be404c29182671a97e9c674d7baabcc7b6e Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor 
Date: Tue, 21 May 2019 19:25:17 -0400
Subject: [PATCH] update lazy_static to 1.3.0

---
 src/lazy-static/debian/changelog   | 7 +++
 src/lazy-static/debian/copyright.debcargo.hint | 4 ++--
 2 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/src/lazy-static/debian/changelog b/src/lazy-static/debian/changelog
index b89d4e28..74518e5e 100644
--- a/src/lazy-static/debian/changelog
+++ b/src/lazy-static/debian/changelog
@@ -1,3 +1,10 @@
+rust-lazy-static (1.3.0-1) UNRELEASED-FIXME-AUTOGENERATED-DEBCARGO; urgency=medium
+
+  * Team upload.
+  * Package lazy_static 1.3.0 from crates.io using debcargo 2.2.10
+
+ -- Daniel Kahn Gillmor   Tue, 21 May 2019 19:24:40 -0400
+
 rust-lazy-static (1.2.0-1) unstable; urgency=medium
 
   * Package lazy_static 1.2.0 from crates.io using debcargo 2.2.9
diff --git a/src/lazy-static/debian/copyright.debcargo.hint b/src/lazy-static/debian/copyright.debcargo.hint
index 4cbce74e..3eb957a3 100644
--- a/src/lazy-static/debian/copyright.debcargo.hint
+++ b/src/lazy-static/debian/copyright.debcargo.hint
@@ -42,8 +42,8 @@ Comment:
 
 Files: debian/*
 Copyright:
- 2018 Debian Rust Maintainers 
- 2018 Paride Legovini 
+ 2018-2019 Debian Rust Maintainers 
+ 2018-2019 Paride Legovini 
 License: MIT or Apache-2.0
 
 License: Apache-2.0
-- 
2.20.1



signature.asc
Description: PGP signature


Bug#926681: Fwd: Bug#926681: unblock: acme-tiny/1:4.0.4-1

2019-05-22 Thread Samuel Henrique
Control: tags -1 - moreinfo


Bug#929395: typecatcher: FTBFS: dh: unable to load addon python3

2019-05-22 Thread Mattia Rizzolo
Source: typecatcher
Version: 0.3-1
Severity: serious

dpkg-buildpackage: info: source package typecatcher
dpkg-buildpackage: info: source version 0.3-1
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Andrew Starr-Bochicchio 

dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
dpkg-source: info: using options from typecatcher-0.3/debian/source/options: 
--extend-diff-ignore=(^|/)(po/typecatcher\.pot)$
 fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
dh: unable to load addon python3: Can't locate 
Debian/Debhelper/Sequence/python3.pm in @INC (you may need to install the 
Debian::Debhelper::Sequence::python3 module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 
/usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 12) line 
1.
BEGIN failed--compilation aborted at (eval 12) line 1.

make: *** [debian/rules:6: clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


Bug#929395: typecatcher: diff for NMU version 0.3-1.1

2019-05-22 Thread Mattia Rizzolo
Control: tags 929395 + patch
Control: tags 929395 + pending


Dear maintainer,

I've prepared an NMU for typecatcher (versioned as 0.3-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for typecatcher-0.3 typecatcher-0.3

 changelog |   25 +
 compat|1 -
 control   |   14 +++---
 copyright |2 +-
 rules |2 --
 5 files changed, 29 insertions(+), 15 deletions(-)

diff -Nru typecatcher-0.3/debian/changelog typecatcher-0.3/debian/changelog
--- typecatcher-0.3/debian/changelog	2017-09-04 02:48:32.0 +0200
+++ typecatcher-0.3/debian/changelog	2019-05-22 20:40:43.0 +0200
@@ -1,3 +1,20 @@
+typecatcher (0.3-1.1) unstable; urgency=medium
+
+  * Non-Maintainer Upload.
+
+  [ Ondřej Nový ]
+  * d/control: Remove ancient X-Python3-Version field
+  * d/copyright: Use https protocol in Format field
+  * d/changelog: Remove trailing whitespaces
+  * d/control: Set Vcs-* to salsa.debian.org
+
+  [ Mattia Rizzolo ]
+  * Add missing build-dependency on dh-python (Closes: #929395).
+  * Bump debhelper compat level to 12.
+  * Bump Standards-Version to 4.3.0, no changes needed.
+
+ -- Mattia Rizzolo   Wed, 22 May 2019 20:40:43 +0200
+
 typecatcher (0.3-1) unstable; urgency=medium
 
   * New upstream release.
@@ -5,10 +22,10 @@
   * Add debian/watch file.
   * debian/control:
- Depend on gir1.2-webkit2-4.0 and drop gir1.2-webkit-3.0.
-   - "Extra" priority has been deprecated; now "optional."  
-   - Move to "fonts" section (Closes: #820386). 
+   - "Extra" priority has been deprecated; now "optional."
+   - Move to "fonts" section (Closes: #820386).
- Bump Standards-Version to 4.1.0.
-  * Bump debian/compat to 10. 
+  * Bump debian/compat to 10.
 
  -- Andrew Starr-Bochicchio   Sun, 03 Sep 2017 20:48:32 -0400
 
@@ -17,7 +34,7 @@
   * Move VCS to to git.
   * debian/control:
- Drop unneeded dh-python build dep.
-   - Build depend on python3-gi for tests (Closes: #812181).  
+   - Build depend on python3-gi for tests (Closes: #812181).
- Bump Standards-Version to 3.9.6, no changes.
 
  -- Andrew Starr-Bochicchio   Fri, 22 Jan 2016 12:07:44 -0800
diff -Nru typecatcher-0.3/debian/compat typecatcher-0.3/debian/compat
--- typecatcher-0.3/debian/compat	2017-09-04 02:46:25.0 +0200
+++ typecatcher-0.3/debian/compat	1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-10
diff -Nru typecatcher-0.3/debian/control typecatcher-0.3/debian/control
--- typecatcher-0.3/debian/control	2017-09-04 02:46:40.0 +0200
+++ typecatcher-0.3/debian/control	2019-05-22 20:36:28.0 +0200
@@ -2,18 +2,18 @@
 Maintainer: Andrew Starr-Bochicchio 
 Section: fonts
 Priority: optional
-Build-Depends: debhelper (>= 10),
-   python3 (>= 3.2),
-   python3-distutils-extra,
+Build-Depends: debhelper-compat (= 12),
+   dh-python,
gir1.2-glib-2.0,
gir1.2-gtk-3.0,
gir1.2-webkit2-4.0,
+   python3 (>= 3.2),
+   python3-distutils-extra,
python3-gi
-Standards-Version: 4.1.0
-Vcs-Git: git://anonscm.debian.org/collab-maint/typecatcher.git
-Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/typecatcher.git
+Standards-Version: 4.3.0
+Vcs-Git: https://salsa.debian.org/debian/typecatcher.git
+Vcs-Browser: https://salsa.debian.org/debian/typecatcher
 Homepage: https://launchpad.net/typecatcher
-X-Python3-Version: >= 3.2
 
 Package: typecatcher
 Architecture: all
diff -Nru typecatcher-0.3/debian/copyright typecatcher-0.3/debian/copyright
--- typecatcher-0.3/debian/copyright	2017-09-04 02:15:17.0 +0200
+++ typecatcher-0.3/debian/copyright	2019-05-22 20:33:45.0 +0200
@@ -1,4 +1,4 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Name: typecatcher
 Upstream-Contact: Andrew Starr-Bochicchio 
 Source: https://launchpad.net/typecatcher
diff -Nru typecatcher-0.3/debian/rules typecatcher-0.3/debian/rules
--- typecatcher-0.3/debian/rules	2016-01-22 02:44:40.0 +0100
+++ typecatcher-0.3/debian/rules	2019-05-22 20:40:24.0 +0200
@@ -5,5 +5,3 @@
 else
 	dh $@ --with python3 --buildsystem=pybuild
 endif
-
-


signature.asc
Description: PGP signature


Bug#929397: ftp.d.o: please upload LTS .buildinfo files to ftp-master

2019-05-22 Thread Holger Levsen
Package: ftp.debian.org
Severity: wishlist

hi,

from #-security today:

  * | h01ger wonders how to tackle #862538
 zwiebelbot | (#debian-security) Debian#862538: security.debian.org: Please
  POST .buildinfo files to buildinfo.debian.net
  - https://bugs.debian.org/862538
| for ftp.d.o there's a cronjob running as my user on coccia.d.o,
  which surely is a hack, but works for now. with security.d.o 
  i have little  idea how to implement this, as i dont know how
  embargoed updates get published and whether we could hook in
  then+their somehow
| h01ger: Well, they do get uploaded to ftp-master after some time.
| oh, really? so this bug is moot? do you have an example?
| h01ger: Hmm, though LTS doesn't get pushed to ftp-master. 
  But everything merged into stable releases just gets uploaded
  to ftp-master, so .buildinfo should be available
  | for variable amounts of "some time" :)


Besides #862538 there are also #862073 and #763822 which are all related
but slightly different details. (and as indicated, we have a workaround for
#862073 which publishes .buildinfo files to both buildinfo.debian.net as 
well as buildinfos.debian.net...
and if you ever forget the details we maintain an overview at
https://wiki.debian.org/ReproducibleBuilds#Big_outstanding_issues )

This new bug shall just be about not copying the .buildinfo files from LTS
uploads to ftp-master.d.o.

Also please note that this bug will only become relevant when Stretch
becomes LTS as only dpkg from stretch (and newer) produces .buildinfo
files.

Thanks!


-- 
tschau,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

we'll all die. make a difference while you can. disobey. smile.


signature.asc
Description: PGP signature


Bug#929064: CVE-2018-16860

2019-05-22 Thread Jeffrey Altman
Brian May wrote:

> I am hardly authoritative on this, however my rough take right now is:
>
> * There is a vulerability.
> * The fix is simple. Looking at the Samba patches, I suspect we only
>   need the bit that alters krb5tgs.c - below.
> * Not convinced this can actually be exploited without AD. It is
>   unlikely you would be using the stock Heimdal with AD. So possible
>   we don't need to worry.

When authoring https://www.samba.org/samba/security/CVE-2018-16860.html
we tried to make it very clear that although this vulnerability exists
within the Heimdal KDC (as well as Microsoft Active Directory) the
exploit grants privilege escalation to any service that authenticates
users via a non-Kerberos mechanism and the obtains a Kerberos ticket for
the authenticated user issued with the service principal being the
requesting service's identity.

To make it clear that non-Windows services could be impacted we provided
an example of a web authentication service using OAuth or Shibboleth to
obtain AFS tokens on behalf of an authenticating user.

This vulnerability is very serious and should be patched immediately.
The minimal set of changes to address CVE-2018-16860 and CVE-2019-12098
can be found in this pull request:

  https://github.com/heimdal/heimdal/pull/555

Jeffrey Altman
Heimdal Project Manager





smime.p7s
Description: S/MIME Cryptographic Signature


Bug#909085: ispell: Sequoia & ispell's /usr/bin/sq

2019-05-22 Thread Daniel Kahn Gillmor
On Wed 2018-10-31 10:38:06 -0400, Daniel Kahn Gillmor wrote:
> fwiw, debian has been shipping a bugfix patch to ispell's sq for over 7
> years, despite several new upstream releases.
> debian/patches/0006-Fix-sq-and-unsq.patch also "addresses" that ispell
> upstream doesn't even ship sq and unsq by default.
>
> anyway, for simplicity, we might just stop shipping sq entirely, thereby
> falling in line with upstream.  The attached patch below (against the
> git repo in https://salsa.debian.org/debian/ispell) does that, i think.
>
> If someone really wants to keep sq, perhaps they could speak up here?

Having heard no one speak up in over six months, I've gone ahead and
built an NMU of ispell (version 3.4.00-6.1), applying these changes (and
doing some other minor packaging cleanup besides).

I've uploaded the 3.4.00-6 for debian unstable to DELAYED/15, so that
the maintainer has chance to cancel it if they care.

I've pushed my changes in git on the master branch over at
https://salsa.debian.org/debian/ispell

I'm also including the debdiff between 3.4.00-6 and 3.4.00-6.1 below.

Regards,

--dkg

diff -Nru ispell-3.4.00/debian/changelog ispell-3.4.00/debian/changelog
--- ispell-3.4.00/debian/changelog	2017-07-11 15:01:26.0 -0400
+++ ispell-3.4.00/debian/changelog	2019-05-22 15:28:50.0 -0400
@@ -1,3 +1,20 @@
+ispell (3.4.00-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Ondřej Nový ]
+  * d/copyright: Use https protocol in Format field
+  * d/control: Set Vcs-* to salsa.debian.org
+
+  [ Daniel Kahn Gillmor ]
+  * Stop shipping sq and unsq (Closes: #909085)
+  * fix logic bug in debian/packages.d/gen_debhelper_files.pl
+  * debian/watch: update to use https
+  * d/{copyright,control}: use current upstream URL
+  * avoid spelling errors in patch descriptions
+
+ -- Daniel Kahn Gillmor   Wed, 22 May 2019 15:28:50 -0400
+
 ispell (3.4.00-6) unstable; urgency=medium
 
   * New 0037-CC-from-environment.patch from Helmut Grohne to fix cross builds
diff -Nru ispell-3.4.00/debian/control ispell-3.4.00/debian/control
--- ispell-3.4.00/debian/control	2017-07-11 15:01:26.0 -0400
+++ ispell-3.4.00/debian/control	2019-05-22 15:26:38.0 -0400
@@ -17,9 +17,9 @@
  wbritish-large (>= 7.1),
  wbritish-small (>= 7.1)
 Standards-Version: 4.0.0
-Homepage: http://www.lasr.cs.ucla.edu/geoff/ispell.html
-Vcs-Git: https://anonscm.debian.org/git/users/robert/ispell.git
-Vcs-Browser: https://anonscm.debian.org/cgit/users/robert/ispell.git/
+Homepage: https://www.cs.hmc.edu/~geoff/ispell.html
+Vcs-Git: https://salsa.debian.org/debian/ispell.git
+Vcs-Browser: https://salsa.debian.org/debian/ispell
 
 Package: ispell
 Architecture: any
diff -Nru ispell-3.4.00/debian/copyright ispell-3.4.00/debian/copyright
--- ispell-3.4.00/debian/copyright	2017-07-11 15:01:26.0 -0400
+++ ispell-3.4.00/debian/copyright	2019-05-22 15:26:38.0 -0400
@@ -1,6 +1,6 @@
-Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
 Upstream-Contact: Geoff Kuenning 
-Source: http://www.lasr.cs.ucla.edu/geoff/ispell.html
+Source: https://www.cs.hmc.edu/~geoff/ispell.html
 
 Files: *
 Copyright:
diff -Nru ispell-3.4.00/debian/packages.d/gen_debhelper_files.pl ispell-3.4.00/debian/packages.d/gen_debhelper_files.pl
--- ispell-3.4.00/debian/packages.d/gen_debhelper_files.pl	2017-07-11 15:01:26.0 -0400
+++ ispell-3.4.00/debian/packages.d/gen_debhelper_files.pl	2019-05-22 15:26:38.0 -0400
@@ -54,7 +54,7 @@
 die "Invalid action $action" unless $cleanonly or $action eq "generate";
 
 my @debdirs = grep { -d $_ } ("./debian", "../debian", "../../debian");
-die "Cannot find debian dir" unless $#debdirs < 1;
+die "Cannot find debian dir" if $#debdirs < 1;
 chdir "$debdirs[0]/.." or die "Cannot chdir to $debdirs[0]/..: $!\n";
 
 my $dir="debian/packages.d";
diff -Nru ispell-3.4.00/debian/patches/0006-Fix-sq-and-unsq.patch ispell-3.4.00/debian/patches/0006-Fix-sq-and-unsq.patch
--- ispell-3.4.00/debian/patches/0006-Fix-sq-and-unsq.patch	2017-07-11 15:01:26.0 -0400
+++ ispell-3.4.00/debian/patches/0006-Fix-sq-and-unsq.patch	1969-12-31 19:00:00.0 -0500
@@ -1,239 +0,0 @@
-From: "Dr. Werner Fink" 
-Date: Thu, 31 May 2007 00:00:00 +0200
-Subject: 0006 Fix sq and unsq
-
-Fix sq/unsq, hint from Thomas Rachel
-
-The patch is taken from ispell-3.3.02-102.1.src.rpm from OpenSUSE.

- Makefile |  9 +++--
- sq.1 |  4 ++--
- sq.c | 32 
- unsq.c   | 29 ++---
- 4 files changed, 47 insertions(+), 27 deletions(-)
-
-diff --git a/Makefile b/Makefile
-index a11ed06..c8e4b23 100644
 a/Makefile
-+++ b/Makefile
-@@ -283,6 +283,7 @@ all:	all-languages
- programs: buildhash findaffix tryaffix ispell
- programs: icombine ijoin munchlist
- programs: subset zapdups
-+programs: sq unsq
- 
- 

Bug#929399: virtualbox-guest-dkms: error in building kernel module

2019-05-22 Thread Valery Senotov
Package: virtualbox-guest-dkms
Version: 6.0.8-dfsg-4
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Since last update (installed on my machine about a day ago) the package can't 
build kernel module because of failing of building vboxvideo. I've only found 
out that in the build directory of vboxvideo wrong include library path is used.


-- System Information:
Distributor ID: Parrot
Description:Parrot GNU/Linux 4.6
Release:4.6
Codename:   n/a
Architecture: x86_64

Kernel: Linux 5.1.0-parrot1-3t-amd64 (SMP w/4 CPU cores)
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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages virtualbox-guest-dkms depends on:
ii  dkms  2.6.1-4

virtualbox-guest-dkms recommends no packages.

virtualbox-guest-dkms suggests no packages.

-- no debconf information
DKMS make.log for virtualbox-guest-6.0.8 for kernel 5.1.0-parrot1-3t-amd64 
(x86_64)
Wed 22 May 22:51:02 MSK 2019
make: Entering directory '/usr/src/linux-headers-5.1.0-parrot1-3t-amd64'
  CC [M]  /var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/VBoxGuest-linux.o
  CC [M]  /var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/VBoxGuest.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/VBoxGuestR0LibGenericRequest.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/VBoxGuestR0LibHGCMInternal.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/VBoxGuestR0LibInit.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/VBoxGuestR0LibPhysHeap.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/VBoxGuestR0LibVMMDev.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/alloc-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/initterm-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/memobj-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/mpnotification-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/powernotification-r0drv.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/alloc-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/assert-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/initterm-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/memobj-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/memuserkernel-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/mp-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/mpnotification-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/process-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/semevent-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/semeventmulti-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/semfastmutex-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/semmutex-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/spinlock-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/thread-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/thread2-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/time-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/timer-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/linux/RTLogWriteDebugger-r0drv-linux.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/r0drv/generic/semspinmutex-r0drv-generic.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/common/alloc/alloc.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/common/err/RTErrConvertFromErrno.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/common/err/RTErrConvertToErrno.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/common/err/errinfo.o
  CC [M]  /var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/common/log/log.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/common/log/logellipsis.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/common/log/logrel.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/common/log/logrelellipsis.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/common/log/logcom.o
  CC [M]  
/var/lib/dkms/virtualbox-guest/6.0.8/build/vboxguest/common/log/logformat.o
  CC [M]  

Bug#929394: rust-libc: please update to 0.2.55

2019-05-22 Thread Daniel Kahn Gillmor
On Wed 2019-05-22 14:22:38 -0400, Daniel Kahn Gillmor wrote:
> There are 100 of them -- yikes!  I'm not sure how to efficiently and
> safely test them all to ensure that the upgrade doesn't break anything,
> so rather than just applying the patch below, i'm proposing it here.

We discussed the upgrade over on #debian-rust, and decided that because
this is a change in the PATCH version level, it is likely to be fine to
do the upgrade.

If we need something more subtle between 0.2.48 and 0.2.55 to make it
into buster (we do not anticipate needing that), we should be able to
use testing-proposed-updates instead.

--dkg


signature.asc
Description: PGP signature


Bug#905720: Bug#926681: unblock: acme-tiny/1:4.0.4-1

2019-05-22 Thread Samuel Henrique
Control: tags -1 - moreinfo


Bug#929403: php-horde-icalendar 2.1.8-1: autopkgtest regression

2019-05-22 Thread Steve Langasek
Source: php-horde-icalendar
Version: 2.1.8-1
Severity: important
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu eoan

Dear Mathieu,

The autopkgtests for php-horde-icalendar 2.1.8-1 have never passed; they
always fail with this error:

autopkgtest [13:09:30]: test phpunit: [---
PHP Fatal error:  Uncaught Error: Class 'Horde_Test_Case' not found in 
/tmp/autopkgtest-lxc.tfhylnhe/downtmp/build.NcJ/src/Horde_Icalendar-2.1.8/test/Horde/Icalendar/AttributeTest.php:13
Stack trace:
#0 /usr/share/php/PHPUnit/Util/FileLoader.php(57): include_once()
#1 /usr/share/php/PHPUnit/Util/FileLoader.php(45): 
PHPUnit\Util\FileLoader::load('/tmp/autopkgtes...')
#2 /usr/share/php/PHPUnit/Framework/TestSuite.php(540): 
PHPUnit\Util\FileLoader::checkAndLoad('/tmp/autopkgtes...')
#3 /usr/share/php/PHPUnit/Framework/TestSuite.php(618): 
PHPUnit\Framework\TestSuite->addTestFile('/tmp/autopkgtes...')
#4 /usr/share/php/PHPUnit/Runner/BaseTestRunner.php(70): 
PHPUnit\Framework\TestSuite->addTestFiles(Array)
#5 /usr/share/php/PHPUnit/TextUI/Command.php(183): 
PHPUnit\Runner\BaseTestRunner->getTest('.', '', Array)
#6 /usr/share/php/PHPUnit/TextUI/Command.php(162): 
PHPUnit\TextUI\Command->run(Array, true)
#7 /usr/bin/phpunit(42): PHPUnit\TextUI\Command::main()
#8 {main}
  thrown in 
/tmp/autopkgtest-lxc.tfhylnhe/downtmp/build.NcJ/src/Horde_Icalendar-2.1.8/test/Horde/Icalendar/AttributeTest.php
 on line 13
autopkgtest [13:09:31]: test phpunit: ---]

  (https://ci.debian.net/packages/p/php-horde-icalendar/unstable/amd64/)

This is a regression vs the previous version of php-horde-icalendar,
2.1.7-3, whose autopkgtests passed.

Since php-horde-icalendar 2.1.8-1 was uploaded to Debian before autopkgtest
regressions became blocking for testing migration, 2.1.8-1 is in testing and
will be included in the next Debian release.  However, autopkgtest
regressions have always been blocking in Ubuntu, where this test also fails,
so FYI php-horde-icalendar 2.1.8 will not be included in an Ubuntu release
until this is resolved.

(Also, obviously if the tests are consistently failing, this prevents you
from using this as an effective CI gate for Debian testing, so dependencies
of php-horde-icalendar could at any point cause php-horde-icalendar to have
runtime regressions in Debian testing.)

Regards,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature


Bug#929393: rust-lazy-static: please upgrade to 1.3.0

2019-05-22 Thread Daniel Kahn Gillmor
Control: retitle 929393 rust-lazy-static: please upgrade to 1.3.0

On Wed 2019-05-22 14:20:11 -0400, Daniel Kahn Gillmor wrote:
> sequoia-openpgp wants lazy_static version 0.13.0.  we only have 0.11.0
> in debian right now.

I mis-wrote this -- it should have said we want lazy_static 1.3.0, but
we currently have 1.2.0.

talking with kpcyrd and silwol[m] and Sylvestre on #debian rust today, i
think i gained enough insight and confidence to go ahead with this
upgrade.

First, we discussed whether to target unstable or experimental.  the
rough sense of the group was that unstable is ok. if we come up with
targeted fixes we want in buster before the release, we might use
testing-proposed-updates for that.

I also learned that lazy_static has a spin feature that is versioned
against spin 0.5.0 (0.4.10 is in testing), so upgrading spin initially
is probably advisable.  An updated spin is needed in other projects too,
so this update appears to be concretely useful.

finally, because of the semantic versioning, 1.3.0 is supposed to be a
safe upgrade from 1.2.0.  Indeed, other packages should have their build
(and runtime) dependencies set to just care about the major version (and
maybe >= some minor version, but upstream is supposed to avoid any
breaking changes in minor updates as long as the major version is
already >= 0.

So i've uploaded this package.  If there are problems with the upload or
the process, please let me know.

--dkg


signature.asc
Description: PGP signature


Bug#921694:

2019-05-22 Thread Samuel Henrique
Control: tags -1 - buster-ignore

Removing tag as that is making the package not being removed from Testing,
I thought it would be useful so it wouldn't be listed as a buster RC bug
but I will have to remove the tag now.



--
Samuel Henrique 


Bug#929394: rust-libc: please update to 0.2.55

2019-05-22 Thread Daniel Kahn Gillmor
Package: src:rust-libc
Severity: wishlist
Blocks: 929385 by -1
Control: tags -1 + patch

sequoia-openpgp wants memsec, which wants getrandom, which wants
rust-libc version 0.2.54 or greater.  but we only have rust-libc 0.2.48
in debian right now.

If i look for the dependencies, though:

aptitude '~Dlibrust-libc

There are 100 of them -- yikes!  I'm not sure how to efficiently and
safely test them all to ensure that the upgrade doesn't break anything,
so rather than just applying the patch below, i'm proposing it here.

  --dkg

From 545f9849017fb769bc036127d2515529bbc41179 Mon Sep 17 00:00:00 2001
From: Daniel Kahn Gillmor 
Date: Tue, 21 May 2019 17:40:35 -0400
Subject: [PATCH] update libc to 0.2.55

---
 src/libc/debian/changelog   | 7 +++
 src/libc/debian/copyright.debcargo.hint | 7 +++
 2 files changed, 14 insertions(+)

diff --git a/src/libc/debian/changelog b/src/libc/debian/changelog
index 1f6332fc..eafb81e8 100644
--- a/src/libc/debian/changelog
+++ b/src/libc/debian/changelog
@@ -1,3 +1,10 @@
+rust-libc (0.2.55-1) UNRELEASED-FIXME-AUTOGENERATED-DEBCARGO; urgency=medium
+
+  * Team upload.
+  * Package libc 0.2.55 from crates.io using debcargo 2.2.10
+
+ -- Daniel Kahn Gillmor   Tue, 21 May 2019 17:38:23 -0400
+
 rust-libc (0.2.48-1) unstable; urgency=medium
 
   * Package libc 0.2.48 from crates.io using debcargo 2.2.9
diff --git a/src/libc/debian/copyright.debcargo.hint b/src/libc/debian/copyright.debcargo.hint
index 51056c8a..314b788d 100644
--- a/src/libc/debian/copyright.debcargo.hint
+++ b/src/libc/debian/copyright.debcargo.hint
@@ -19,6 +19,13 @@ Comment:
  FIXME (overlay): These notices are extracted from files. Please review them
  before uploading to the archive.
 
+Files: ./src/hermit/mod.rs
+Copyright: 2018 The Rust Project Developers
+License: UNKNOWN-LICENSE; FIXME (overlay)
+Comment:
+ FIXME (overlay): These notices are extracted from files. Please review them
+ before uploading to the archive.
+
 Files: ./src/lib.rs
 Copyright: 2012-2015 The Rust Project Developers
 License: UNKNOWN-LICENSE; FIXME (overlay)
-- 
2.20.1



signature.asc
Description: PGP signature


Bug#929396: libtool is unable to link complex projects

2019-05-22 Thread Dmitry Mikhirev
Package: libtool
Version: 2.4.6-10
Severity: important

Dear maintainer, I faced a problem trying to build a project,
libtoolized by Buster's libtool. It is also reproducible wit libtool
from Sid. The trouble is that if libfoo.la and libbar.la were built,
where libbar.la depends on libfoo.la, and some binary is linked to
libbar.la, libfoo is not added to the linker command line. If I replace
ltmain.sh and libtool.m4 by the files from the original tarball, I'm
able to build the project successfully.

Steps to reproduce:

1. Get rpm 4.13.1 source tree
git clone g...@github.com:rpm-software-management/rpm.git
cd rpm
git checkout rpm-4.13.1-release
2. Run autoreconf
autoreconf -fiv
3. Download latest berkeley-db from
http://download.oracle.com/otn/berkeley-db/db-18.1.32.tar.gz (the bug
doesn't reproduce when building with system db package) and untar it:
tar -xf db-18.1.32.tar.gz
ln -s db-18.1.32 db
4. Install dependencies
sudo apt install build-essential libnss3-dev libnspr4-dev libpopt-dev 
libdb-dev zlib1g-dev libmagic-dev
5. Configure && make
CPPFLAGS='-I/usr/include/nspr -I/usr/include/nss' ./configure --without-lua 
--without-python
make

Expected result: rpm is built successfully.

Actual result:
/bin/bash ../libtool  --tag=CC   --mode=link gcc  -g -O2 -fPIC -DPIC 
-D_REENTRANT -Wall -Wpointer-arith -Wmissing-prototypes -Wstrict-prototypes  
-fno-strict-aliasing -fstack-protector -Wempty-body   -o rpmdb_dump  
../db3/db_dump.o ../db3/util_cache.o ../db3/util_sig.o librpm.la -ldl -lpthread 
libtool: link: gcc -g -O2 -fPIC -DPIC -D_REENTRANT -Wall -Wpointer-arith 
-Wmissing-prototypes -Wstrict-prototypes -fno-strict-aliasing -fstack-protector 
-Wempty-body -o .libs/rpmdb_dump ../db3/db_dump.o ../db3/util_cache.o 
../db3/util_sig.o  ./.libs/librpm.so -ldl -lpthread
/usr/bin/ld: ../db3/db_dump.o: in function `db_init':
/home/dmitry/src/rpm-github/db3/../db/util/db_dump.c:379: undefined 
reference to `__db_util_env_open_rpmdb'
/usr/bin/ld: ../db3/db_dump.o: in function `main':
/home/dmitry/src/rpm-github/db3/../db/util/db_dump.c:45: undefined 
reference to `__db_util_arg_progname_rpmdb'
/usr/bin/ld: /home/dmitry/src/rpm-github/db3/../db/util/db_dump.c:47: 
undefined reference to `__db_util_version_check_rpmdb'
/usr/bin/ld: /home/dmitry/src/rpm-github/db3/../db/util/db_dump.c:106: 
undefined reference to `__db_util_arg_password_rpmdb'
/usr/bin/ld: /home/dmitry/src/rpm-github/db3/../db/util/db_dump.c:199: 
undefined reference to `__db_util_env_create_rpmdb'
collect2: error: ld returned 1 exit status

In the linker command line librmio.so and libdb.so are missing, as well
as -L options specifying path to find them. Both libraries are listed
as dependency_libs in librpm.la.

After looking at Debian patches I assumed that this issue could be
introduced by the link_all_deplibs.patch. Although after reverting it, I
figured out that even librpm.so has disappeared from the linker command
line. So it seems that some another patch breaks the libtool linking
behavior even with link_all_deplibs=unknown.

-- System Information:
Debian Release: 10.0
  APT prefers testing-proposed-updates
  APT policy: (500, 'testing-proposed-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, mipsel

Kernel: Linux 4.9.0-9-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), 
LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libtool depends on:
ii  autotools-dev   20180224.1
ii  clang-3.5 [c-compiler]  1:3.5-10
ii  clang-5.0 [c-compiler]  1:5.0.2~svn328729-1~exp1~20180509123438.100
ii  clang-6.0 [c-compiler]  1:6.0.1-10
ii  clang-7 [c-compiler]1:7.0.1-8
ii  cpp 4:8.3.0-1
ii  file1:5.35-4
ii  gcc 4:8.3.0-1
ii  gcc-4.6 [c-compiler]4.6.3-14
ii  gcc-4.8 [c-compiler]4.8.4-1
ii  gcc-4.9 [c-compiler]4.9.2-10
ii  gcc-6 [c-compiler]  6.3.0-18+deb9u1
ii  gcc-8 [c-compiler]  8.3.0-6
ii  libc6-dev [libc-dev]2.28-10

Versions of packages libtool recommends:
ii  libltdl-dev  2.4.6-9

Versions of packages libtool suggests:
ii  autoconf 2.69-11
ii  automake [automaken] 1:1.16.1-4
ii  automake1.11 [automaken] 1:1.11.6-5
pn  gcj-jdk  
ii  gfortran 4:8.3.0-1
ii  gfortran-8 [fortran95-compiler]  8.3.0-6
ii  libtool-doc  2.4.6-9

-- no debconf information



Bug#929350: RFS: libt3highlight/0.4.8-1

2019-05-22 Thread Adam Borowski
On Wed, May 22, 2019 at 09:14:11AM +0200, Gertjan Halkes wrote:
> * Package name: libt3highlight
>   Version : 0.4.8-1

> Changes since the last upload:
> 
>   * New upstream release.

Hi!
This upload is targetted at unstable, yet doesn't look like something fit
for a late-freeze update.  It is somewhat controversial whether this matters
much for a near-leaf package, but it makes the life of the Release Team
busier, and some people have strong opinions about the issue.

Thus, I'd propose either:
1. pausing until Buster is released, or
2. uploading to experimental instead, or
3. if you consider it important, isolating just the bad free fix, and
   applying it as a patch to 0.4.6 (I don't know how severe the bug is)


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ Latin:   meow 4 characters, 4 columns,  4 bytes
⣾⠁⢠⠒⠀⣿⡁ Greek:   μεου 4 characters, 4 columns,  8 bytes
⢿⡄⠘⠷⠚⠋  Runes:   ᛗᛖᛟᚹ 4 characters, 4 columns, 12 bytes
⠈⠳⣄ Chinese: 喵   1 character,  2 columns,  3 bytes <-- best!



Bug#929268: Pending fixed packages

2019-05-22 Thread Mathieu Parent
Hi rollopack,

Please test the packages from:
https://salsa.debian.org/samba-team/samba/-/jobs/179622/artifacts/browse/debian/output/

They should fix the segfaults.

@carnil: Once the package is confirmed fixing this bug, can I upload
to security-master? It has only 3 changes:
  * Update Salsa Pipeline
  * Backport stability fixes:
- Bug 13315: Samba segfault with NT1 connections in smbXsrv_session_create()
  (Closes: #929268)
- Bug 13454: No Backtrace given by Samba's AD DC by default"
  (Closes: #929303)



Regards
-- 
Mathieu Parent



Bug#929398: jasperreports: Should jasperreports be removed from unstable?

2019-05-22 Thread Salvatore Bonaccorso
Source: jasperreports
Version: 6.3.1-2
Severity: serious
Justification: unfit for a Debian release

Hi

Given the discussion around https://bugs.debian.org/880467#10 and the
fact that removing jasperreports from unstable will cause no issues
with reverse (build) dependencies anymore:

> $ dak rm --suite=sid -n -R jasperreports
> Will remove the following packages from sid:
> 
> jasperreports |6.3.1-2 | source
> libjasperreports-java |6.3.1-2 | all
> 
> Maintainer: Debian Java Maintainers 
> 
> 
> --- Reason ---
> 
> --
> 
> Checking reverse dependencies...
> No dependency problem found.

Should jasperreports now be removed from the archive?

Regards,
Salvatore



Bug#929404: debian-security-support: [INTL:pt] Updated Portuguese translation

2019-05-22 Thread Américo Monteiro
Package: debian-security-support
Version: 2019.05.15
Tags: l10n, patch
Severity: wishlist

Updated Portuguese translation for  debian-security-support messages
Translator: Américo Monteiro 
Feel free to use it.

For translation updates please contact 'Last Translator' 

-- 
Melhores cumprimentos/Best regards,

Américo Monteiro

-


debian-security-support_2019.05.15_pt.po.gz
Description: application/gzip


Bug#929063: init: delegate selinux operation to separate binary

2019-05-22 Thread Jesse Smith
On Wed, 22 May 2019 13:28:39 +0200 (CEST) Thorsten Glaser wrote:
>
> (I’m not quite convinced the effort is worth it, but given that
> this would be changed upstream, and that there are likely other
> users of the same upstream code who’re _not_ using SELinux, this
> would be very welcomed by those, so I’m okay with it.)

I'd like to point out that init already has compile-time defines in the
code which check for the existence of SELinux (using the variable
WITH_SELINUX). If WITH_SELINUX is not defined at compile time, then the
SELinux code isn't built into init. So other projects, perhaps Debian
Hurd or FreeBSD, can already build init without SELinux features.


Bug#928809: lintian: suggest adding gitlab-ci file

2019-05-22 Thread Chris Lamb
Dmitry Bogatov wrote:

> > [..]  I just think that lintian should be less pro-active at adding
> > checks for things that are far from accepted.
> 
> That is why I propose introducing concept of "controversial" checks.

I think we are all violently agreeing here. 

> Having Lintian plainly reject such proposals would mean need in creation
> of something like "lintian-unofficial"

(Personally, I doubt someone would fork Lintian, more likely its
output would become less and less "trusted". But both outcomes suck.)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org  chris-lamb.co.uk
   `-



Bug#929405: ITP: pveclib -- power vector library

2019-05-22 Thread Gabriel F. T. Gomes
Package: wnpp
Severity: normal

I will start working on the packaging for pveclib
(https://github.com/open-power-sdk/pveclib).

Cheers,
Gabriel



<    1   2