Bug#835394: [pkg-gnupg-maint] Bug#835394: Bug#835394: Same issue here

[Daniel Kahn Gillmor]

On Sun 2018-10-07 19:46:38 +0200, Sofus Rose wrote:
> 0. systemd is set to a text startup target.
> 1. I login to a tty text console.
> 2. I run startx

I use this same workflow to start X11, and i don't have the problems
described.

> It may be worth noting that after my DE (Budgie) has started, I'm usually
> prompted to enter my password to unlock the login keychain.

what version of pinentry are you using?  do you have dbus-user-session
installed?

Regards,

--dkg

Bug#910560: [choose-mirror] fails to build when parallel build is activated

[Holger Wansing]

Package: choose-mirror
Severity: serious
Version: 2.92

Since version 2.92, choose-mirror fails to build with
"dpkg-buildpackage -j", the debian/iso_3166.tab file seems to be removed by 
error:

(can also be seen at jenkins:
https://jenkins.debian.net/view/d-i_packages/job/d-i_build_choose-mirror/ 
where I found it initially)


holgerw@t520:~/uploading-d-i/d-i/packages/choose-mirror$ dpkg-buildpackage -j
dpkg-buildpackage: info: source package choose-mirror
dpkg-buildpackage: info: source version 2.94
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Holger Wansing 
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build choose-mirror
 fakeroot debian/rules clean
dh clean
   dh_testdir
   debian/rules override_dh_auto_clean
make[1]: Entering directory 
'/home/holgerw/uploading-d-i/d-i/packages/choose-mirror'
rm -rf debian/locales debian/sort-tmp
/usr/bin/make clean check-masterlist
make[2]: Entering directory 
'/home/holgerw/uploading-d-i/d-i/packages/choose-mirror'
rm -f choose-mirror choose-mirror.o *~ mirrors_*.h
rm -f debian/templates-countries debian/httplist-countries 
debian/httpslist-countries debian/ftplist-countries
rm -f demo demo.templates
rm -rf debian/iso-codes/ debian/pobuild*/
rm -f debian/iso_3166.tab


*** WARNING: Mirrors.masterlist was last committed more
*** than 2 weeks ago, maybe it needs an update?

You can try the following command to run a sync, and use git diff/git commit:
   make Mirrors.masterlist
make[2]: Leaving directory 
'/home/holgerw/uploading-d-i/d-i/packages/choose-mirror'
make[1]: Leaving directory 
'/home/holgerw/uploading-d-i/d-i/packages/choose-mirror'
   dh_clean
 dpkg-source -b choose-mirror
dpkg-source: info: using source format '3.0 (native)'
dpkg-source: info: building choose-mirror in choose-mirror_2.94.tar.xz
dpkg-source: info: building choose-mirror in choose-mirror_2.94.dsc
dpkg-source: warning: missing information for output field Standards-Version
 debian/rules build
dh build
   dh_testdir
   dh_update_autotools_config
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory 
'/home/holgerw/uploading-d-i/d-i/packages/choose-mirror'
# Don't try to sync the mirror masterlist during the build:
/usr/bin/make small  ONLINE=n
make[2]: Entering directory 
'/home/holgerw/uploading-d-i/d-i/packages/choose-mirror'
rm -f choose-mirror choose-mirror.o *~ mirrors_*.h
if [ "$ONLINE" != n ]; then \
if wget -nv 
'https://salsa.debian.org/mirror-team/masterlist/raw/master/Mirrors.masterlist' 
-O - > Mirrors.masterlist.new && \
   test -s Mirrors.masterlist.new; then \
mv Mirrors.masterlist.new Mirrors.masterlist; \
else \
rm -f Mirrors.masterlist.new; \
fi; \
fi
isoquery -c | cut -f 1,4 | sort >debian/iso_3166.tab
rm -f debian/templates-countries debian/httplist-countries 
debian/httpslist-countries debian/ftplist-countries
rm -f demo demo.templates
rm -rf debian/iso-codes/ debian/pobuild*/
rm -f debian/iso_3166.tab
if [ "$USE_HTTP" ]; then ./mirrorlist http Mirrors.masterlist 
debian/iso_3166.tab; fi
if [ "$USE_HTTPS" ]; then ./mirrorlist https Mirrors.masterlist 
debian/iso_3166.tab; fi
if [ "$USE_FTP" ]; then ./mirrorlist ftp Mirrors.masterlist 
debian/iso_3166.tab; fi
./mirrorlist httplist Mirrors.masterlist debian/iso_3166.tab
./mirrorlist httpslist Mirrors.masterlist debian/iso_3166.tab
./mirrorlist ftplist Mirrors.masterlist debian/iso_3166.tab
Unable to read debian/iso_3166.tab at ./mirrorlist line 23.
Unable to read debian/iso_3166.tab at ./mirrorlist line 23.
Unable to read debian/iso_3166.tab at ./mirrorlist line 23.
Makefile:81: recipe for target 'debian/httplist-countries' failed
make[2]: *** [debian/httplist-countries] Error 2
make[2]: *** Waiting for unfinished jobs
Makefile:99: recipe for target 'mirrors_https.h' failed
make[2]: *** [mirrors_https.h] Error 2
Makefile:84: recipe for target 'debian/httpslist-countries' failed
make[2]: *** [debian/httpslist-countries] Error 2
Unable to read debian/iso_3166.tab at ./mirrorlist line 23.
Makefile:87: recipe for target 'debian/ftplist-countries' failed
make[2]: *** [debian/ftplist-countries] Error 2
Unable to read debian/iso_3166.tab at ./mirrorlist line 23.
Makefile:96: recipe for target 'mirrors_http.h' failed
make[2]: *** [mirrors_http.h] Error 2
make[2]: Leaving directory 
'/home/holgerw/uploading-d-i/d-i/packages/choose-mirror'
debian/rules:15: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory 
'/home/holgerw/uploading-d-i/d-i/packages/choose-mirror'
debian/rules:3: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2



-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

Bug#907917: RM: qmapshack [armel mips mips64el ppc64el s390x] -- ROM; qtwebengine-opensource-src dependency not available

[Sebastiaan Couwenberg]

Can you please RM qmapshack, it's blocking testing migration.

Kind Regards,

Bas

Bug#910444: Filesystems listed in /etc/fstab are no more automatically mounted since switching to OpenRC

[Benda Xu]

Hi Axel,

Adam Borowski  writes:

> On Sat, Oct 06, 2018 at 02:40:22PM +0200, Axel Beckert wrote:
>> Package: openrc
>> Version: 0.34-3
>> Severity: grave
>> Justification: renders package unusable
>
>> I just installed Debian Buster/Sid from scratch on a GPD Pocket 1 and
>> then switched from systemd to OpenRC.

Thank you for raising this up.  Are you using openrc with sysvinit-core?

>> Since then, /home (on LVM on LUKS), /boot and /boot/efi (i.e. anything
>> from /etc/fstab except the root file system) are no more mounted
>> automatically despite they're listed in /etc/fstab and "mount -a"
>> mounts them without issues.
>
> It works for continously upgraded systems.  I can't check a fresh one anytime
> soon (explanation below), but it appears that installing a new daemon[1]
> doesn't properly register it for requested runlevels (you can still run
> update-rc.d to fix that).  Not sure if this is the cause, would need to look
> more.  Too bad, init-system-helpers didn't have an update in almost two
> months so the culprit might be something else.
>
> Benda: could you please take a look?  The package being unusable on new
> systems sounds pretty urgent...

@Adam, acknowledged.  I do need to look more closely into OpenRC, to get
it well prepared for buster.

>> Swap hasn't been activated by "mount -a", though. (Probably expected,
>> just wanted to mention it.)
>
> Sounds consistent with init scripts not having been registered.

@Axel, what is the output of `rc-update` of the said system?
/etc/init.d/mountall.sh from initscripts is called by OpenRC by default
to handle /etc/fstab.

Confirmation check: if you execute `invoke-rc.d mountall.sh start`
instead of `mount -a`, does it work as well?

Yours,
Benda

Bug#910065: stretch-pu: package libmail-deliverystatus-bounceparser-perl/1.542-1

[Xavier]

Le 06/10/2018 à 18:43, Adam D. Barratt a écrit :
> Control: tags -1 + moreinfo
> 
> On Tue, 2018-10-02 at 11:10 +0200, Xavier Guimard wrote:
>> libmail-deliverystatus-bounceparser-perl contains some viruses in its
>> tests files (#864800). This update proposes to clean sources.
>>
>> Since debdiff contains virus signatures, it can not be embedded here
>> (rejected by SMTP server). I put it on qa.debian.org server:
>> /home/yadd/libmail-deliverystatus-bounceparser-perl_1.542-1.debdiff
> 
> +libmail-deliverystatus-bounceparser-perl (1.542+deb9u1-1) stable-
> proposed-updates; urgency=medium
> 
> The version there is odd. Normally it would be 1.5242-1+deb9u1. Is this
> an attempt to indicate that the source tarball has changed, i.e. a  new
> "upstream" version? If so, I'd prefer 1.542+repacked-1~deb9u1, as a
> backport from unstable, with the changes that don't immediately look
> appropriate reverted:
> 
>    * Declare compliance with policy 4.2.1
>    * Remove dependency to libtest-simple-perl (>= 0.94)
>    * Bump debhelper compatibility to 10
> 
> As an additional note, the preferred changelog distribution is simply
> "stretch".
> 
> Regards,
> 
> Adam

Hello,

thanks. New version uploaded to qa.debian.org:
/home/yadd/libmail-deliverystatus-bounceparser-perl_1.542-1.debdiff

previous moved to /home/yadd/archive

Regards,
Xavier

Bug#910237: Bug

[Steve Robbins]

Control: severity -1 normal

On Fri, 5 Oct 2018 15:40:46 +0200 Paul Gevers  wrote:

> Anyways, mathicgb now FTBFS on the reproducibility infrastructure with
> the same message (or at least one close to it), hence raising severity.

This level seems a bit extreme, to me, considering the guidelines in https://
www.debian.org/Bugs/Developer

Moreover, it's not clear that the bug lies with googletest.

-Steve

Bug#903656: stretch-pu: package publicsuffix/20180523.2326-0+deb9u1

[Daniel Kahn Gillmor]

On Sat 2018-10-06 18:13:12 +0100, Adam D. Barratt wrote:
> On Thu, 2018-07-12 at 12:27 -0400, Daniel Kahn Gillmor wrote:
>> I've tried multiple times now to attach the debdiff to this bug
>> report,
>> and it continues to be rejected as spam by bugs.debian.org with this
>> message:
>> 
>>  <903...@bugs.debian.org>: host buxtehude.debian.org[209.87.16.39]
>> said: 550
>>  malware detected: Sanesecurity.Jurlbl.db3039.UNOFFICIAL: message
>> rejected
>>  (in reply to end of DATA command)
>
> I'd be interested to know if that's still the case. Does changing the
> compression format help?

It appears to have been fixed, without having to change the compression format.

> Please go ahead.

done, thanks.  however, i note that since the original report, there
have been more updates on publicsuffix upstream (the state of the DNS
continues to change).  I've uploaded those changes to unstable as
20181003.1334-1, but those changes should probably also be ported to
stretch.

i'll soon submit another bug report asking for that update as well on
top of 20180523.2326-0+deb9u1, unless you want me to reuse this current
bug report.

regards,

--dkg



signature.asc
Description: PGP signature

Bug#903656: stretch-pu: package publicsuffix/20180523.2326-0+deb9u1

[Daniel Kahn Gillmor]

On Sat 2018-10-06 18:13:12 +0100, Adam D. Barratt wrote:
> On Thu, 2018-07-12 at 12:27 -0400, Daniel Kahn Gillmor wrote:
>> I've tried multiple times now to attach the debdiff to this bug
>> report,
>> and it continues to be rejected as spam by bugs.debian.org with this
>> message:
>> 
>>  <903...@bugs.debian.org>: host buxtehude.debian.org[209.87.16.39]
>> said: 550
>>  malware detected: Sanesecurity.Jurlbl.db3039.UNOFFICIAL: message
>> rejected
>>  (in reply to end of DATA command)
>
> I'd be interested to know if that's still the case.

i'll try it again here.

regards,

--dkg



publicsuffix_20180218.2049-0+deb9u1_20180523.2326-0+deb9u1.debdiff.gz
Description: debdiff for #903656

Bug#910242: samba-libs: missing Breaks+Replaces: libndr-standard0

[Steve Langasek]

Control: severity -1 important

On Wed, Oct 03, 2018 at 09:05:31PM +0200, Andreas Beckmann wrote:
> Package: samba-libs
> Version: 2:4.8.5+dfsg-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts

> during a test with piuparts I noticed your package fails to upgrade from
> 'wheezy' to 'jessie' to 'stretch' to 'buster'.
> Its successor installed fine in 'wheezy', and upgraded to 'jessie' and 
> 'stretch'
> successfully,
> but then the upgrade to 'buster' failed,
> 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...):

>   Selecting previously unselected package samba-libs:amd64.
>   Preparing to unpack .../29-samba-libs_2%3a4.8.5+dfsg-1_amd64.deb ...
>   Unpacking samba-libs:amd64 (2:4.8.5+dfsg-1) ...
>   dpkg: error processing archive 
> /tmp/apt-dpkg-install-sgTROH/29-samba-libs_2%3a4.8.5+dfsg-1_amd64.deb 
> (--unpack):
>trying to overwrite '/usr/lib/x86_64-linux-gnu/libndr-krb5pac.so.0.0.1', 
> which is also in package libndr-standard0:amd64 4.0.0~beta2+dfsg1-3.2+deb7u2
>   dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)

> libndr-standard0 was last seen in oldoldstable.

I don't think this warrants a serious severity, because the samba-libs
package as of oldstable already shipped libndr-krb5pac.so.0.0.1 and if the
only way anyone has filed a bug report about it is after doing a piuparts
test across 4 releases, then the missing Breaks doesn't seem to have had
much practical impact despite the fact that samba4 was entirely obsoleted by
samba version 4.2 (and therefore by samba-libs) in oldstable.

-- 
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#910522: r-cran-pracma: Incomplete debian/copyright?

[Andreas Tille]

Hi Oliver,

please always write to the bug or to the team address if you have
questions about packaging.  Thank you.

On Sun, Oct 07, 2018 at 02:38:48PM -0300, Oliver Dechant wrote:
> 
> With regards to this bug comment. I double checked the archive on CRAN
> and the only attribution I see is for Hans W. Borchers. Which we have
> included properly in debian/copyright on salsa.
> 
> I'll reply to Chris with the same shortly after digging around a bit
> longer unless there is something I'm missing you may suggest.

What did you do for "digging"?

$ grep -R "Jonas Lundgren" 
man/quadgr.Rd:  Copyright (c) 2009 Jonas Lundgren for the Matlab function 
\code{quadgr}
man/fractalcurve.Rd:  Copyright (c) 2011 Jonas Lundgren for the Matlab toolbox 
\code{fractal 
$ grep -R "Greg von Winckel"
R/barycentric.R:ydist[ydist == 0] <- eps  # Thanks to Greg von Winckel for 
this trick !
man/triquad.Rd:  Copyright (c) 2005 Greg von Winckel Matlab code based on the 
publication
man/cotes.Rd:  Copyright (c) 2005 Greg von Winckel of nicely vectorized Matlab 
code,
man/barylag2d.Rd:  Copyright (c) 2004 Greg von Winckel of a Matlab function 
under BSD license;
$ grep -R "Paul Godfrey"
man/rationalfit.Rd:  Copyright (c) 2006 by Paul Godfrey for a Matlab version 
available from the
man/eta.Rd:  Copyright (c) 2001 Paul Godfrey for a Matlab version available on
man/gammaz.Rd:  Copyright (c) 2001 Paul Godfrey for a Matlab version available 
on
man/zeta.Rd:  Copyright (c) 2001 Paul Godfrey for a Matlab version available on

So Chris is obviously right.  You should not rely on the DESCRIPTION file
but have a look into the code.  Just mention those files in debian/copyright
and check for further missing names (may be by grepping for "Copyright").
 
Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#909941: [Pkg-erlang-devel] erlang 21.1+dfsg-1 causes rabbitmq-server to fail to start/install

[Sergei Golovan]

Hi Paul,

On Sun, Oct 7, 2018 at 9:56 PM Paul Gevers  wrote:
>
> On 07-10-18 19:26, Paul Gevers wrote:
> > On Sun, 30 Sep 2018 12:54:10 +0100 Jose Antonio Ortega Ruiz
> >  wrote:
> >> This version of the server fails to start using systemd:
> >
> > Yes, but until recently it worked. So this is a regression caused by
> > some other package.

According to [1] rabbitmq-server doesn't work with Erlang 21 prior to
version 3.7.7,
so I guess I can't do much with this bug except probably adding the
'breaks' header
to debian/control.

It's just time to update rabbitmq-server.

Cheers!
-- 
Sergei Golovan

Bug#910559: cli-common-dev: dh_makeclilibs explicitly uses "chown", which means we cannot use Rules-Requires-Root: no

[Daniel Kahn Gillmor]

Package: cli-common-dev
Version: 0.9+nmu1
Severity: normal
Control: affects -1 src:gmime2.6

I'm trying to rebuild gmime2.6 with Rules-Requires-Root: no (see
/usr/share/doc/dpkg-dev/rootless-builds.txt.gz for more details).
When I do that, though, it yields the following error:


   dh_makeclilibs
chown: changing ownership of 'debian/libgmime2.6-cil/DEBIAN/clilibs': Operation 
not permitted
dh_makeclilibs: chown 0:0 debian/libgmime2.6-cil/DEBIAN/clilibs returned exit 
code 1
make: *** [debian/rules:40: binary] Error 1


It's not clear to me that this is either necessary or good.  i'd much
prefer to just build the package without needing fakeroot.
dh_makeclilibs should facilitate that instead of blocking it.

   --dkg

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

Kernel: Linux 4.18.0-1-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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cli-common-dev depends on:
ii  debhelper  11.3.5
ii  libxml-dom-perl1.44-2
ii  mono-devel [strong-name-tool]  4.6.2.7+dfsg-1
ii  mono-utils [cil-disassembler]  4.6.2.7+dfsg-1
ii  perl   5.26.2-7

cli-common-dev recommends no packages.

cli-common-dev suggests no packages.

-- no debconf information

Bug#910558: Insufficient privileges on trustedkeys.gpg

[martin f krafft]

Package: flatpak
Version: 1.0.3-1
Severity: minor

While running

  # flatpak -vv remote-add --if-not-exists flathub 
https://flathub.org/repo/flathub.flatpakrepo

the file /var/lib/flatpak/repo/flathub.trustedkeys.gpg was created
with permissions 0640, which means that regular users weren't able
to interact with flatpak until I added o+r.

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

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

Versions of packages flatpak depends on:
ii  bubblewrap 0.3.1-2
ii  libappstream-glib8 0.7.12-1
ii  libarchive13   3.2.2-5
ii  libc6  2.27-6
ii  libglib2.0-0   2.58.1-2
ii  libgpgme11 1.11.1-1
ii  libjson-glib-1.0-0 1.4.2-4
ii  libostree-1-1  2018.8-2
ii  libpolkit-gobject-1-0  0.105-21
ii  libseccomp22.3.3-3
ii  libsoup2.4-1   2.64.1-1
ii  libxau61:1.0.8-1+b2
ii  libxml22.9.4+dfsg1-7+b1
ii  xdg-desktop-portal 1.0.2-1

Versions of packages flatpak recommends:
ii  desktop-file-utils   0.23-3
ii  gtk-update-icon-cache3.24.1-2
ii  hicolor-icon-theme   0.17-2
ii  libpam-systemd   239-10
ii  p11-kit  0.23.14-2
ii  policykit-1  0.105-21
ii  shared-mime-info 1.10-1
pn  xdg-desktop-portal-gtk | xdg-desktop-portal-backend  

Versions of packages flatpak suggests:
pn  avahi-daemon  

-- no debconf information


-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#910544: tzdata: Brazil 2018-2019 DST changed

[Aurelien Jarno]

On 2018-10-07 18:49, Antonio Terceiro wrote:
> Package: tzdata
> Version: 2018e-1
> Severity: important
> Tags: upstream
> 
> Hi,
> 
> Recently it was decided that this year DST will start in Brazil on
> November 18th instead of November 4th. The corresponding thread on the
> upstream mailing list starts at:
> https://mm.icann.org/pipermail/tz/2018-October/026917.html
> 
> The maintainer said he will wait for the official decree for making a
> release, but the required changes were already made in the git
> repository.

Do you know how long it usually take for a presidential decree to be
sign? We do not want to propagate the wrong changes to users.

> Given the very short window to update every system in the country, it
> would be nice if we could have a release as soon as possible.

There are still four week before the change, we have seen much shorter
timeframe in the order of a few days, so we should not rush it too much
either.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Bug#910557: ITP: python-pykwalify -- Python YAML/JSON schema validation library

[Johan Fleury]

Package: wnpp
Severity: wishlist
Owner: Johan Fleury 

* Package name: python-pykwalify
  Version : 1.7.0
  Upstream Author : Johan Andersson 
* URL : http://github.com/grokzen/pykwalify
* License : MIT
  Programming Lang: Python
  Description : Python YAML/JSON schema validation library

PyKwalify is a open source port of the kwalify lib and specification.

Bug#901858: nheko segfault on login

[Hubert Chathi]

A much more recent version of nheko is available, which has many
changes.  Can you retry with the latest version (0.6.1) and see if it
still happens?  Maybe also try with the latest version of liblmdb0.

Thanks

On Tue, 19 Jun 2018 05:44:27 -0700, Red Omen  said:

> Package: nheko Version: 0.4.2-1 Severity: normal

> Dear Maintainer, When connecting to matrix.org nheko segfaults
> immediately after clicking login.  Removing ~/.cache/nheko and
> ~/.config/nheko allows me to re-enter my info but it still segfaults
> on login.

> Here is a backtrace from gdb:

> Starting program: /usr/bin/nheko [Thread debugging using libthread_db
> enabled] Using host libthread_db library
> "/lib/x86_64-linux-gnu/libthread_db.so.1".  [New Thread 0x7fffe9338700
> (LWP 18233)] [New Thread 0x7fffde0ca700 (LWP 18234)] [New Thread
> 0x7fffdd688700 (LWP 18235)] [New Thread 0x7fffd56ee700 (LWP 18236)]
> [New Thread 0x7fffd4eed700 (LWP 18237)] [New Thread 0x7fffcbfff700
> (LWP 18238)]

> Thread 1 "nheko" received signal SIGSEGV, Segmentation fault.
> 0x77774935 in mdb_dbi_open () from
> /usr/lib/x86_64-linux-gnu/liblmdb.so.0 (gdb) bt #0 0x77774935
> in mdb_dbi_open () at /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #1
> 0x55691906 in
> Cache::getRoomInfo(std::vector std::char_traits, std::allocator >,
> std::allocator std::char_traits, std::allocator > > > const&) () #2
> 0x556c39c8 in ChatPage::changeTopRoomInfo(QString const&) ()
> #3 0x75c9c2af in QMetaObject::activate(QObject*, int, int,
> void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4
> 0x557276e2 in RoomList::roomChanged(QString const&) () #5
> 0x556f4fec in RoomList::initialize(QMap
> const&) () #6 0x75c9cd02 in QObject::event(QEvent*) () at
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x76d98a83 in
> QWidget::event(QEvent*) () at
> /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x76d596cc in
> QApplicationPrivate::notify_helper(QObject*, QEvent*) () at
> /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x76d60e84 in
> QApplication::notify(QObject*, QEvent*) () at
> /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x75c6c938 in
> QCoreApplication::notifyInternal2(QObject*, QEvent*) () at
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x75c6f4cd in
> QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*)
> () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x75cc7b73
> in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13
> 0x72d44287 in g_main_context_dispatch () at
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x72d444c0 in
> () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #15
> 0x72d4454c in g_main_context_iteration () at
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x75cc719f in
> QEventDispatcherGlib::processEvents(QFlags)
> () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7fffebbbc2c1
> in () at /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #18
> 0x75c6ab6a in
> QEventLoop::exec(QFlags) () at
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x75c73ed4 in
> QCoreApplication::exec() () at
> /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x5562ea43 in
> main ()

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

> Kernel: Linux 4.15.7a (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_US,
> LC_CTYPE=en_US (charmap=ISO-8859-1), LANGUAGE=en_US
> (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/dash Init: systemd
> (via /run/systemd/system)

> Versions of packages nheko depends on: ii libc6 2.27-3 ii libgcc1
> 1:8.1.0-5 ii liblmdb0 0.9.21-1 ii libqt5concurrent5 5.10.1+dfsg-7 ii
> libqt5core5a 5.10.1+dfsg-7 ii libqt5gui5 5.10.1+dfsg-7 ii
> libqt5multimedia5 5.10.1-2 ii libqt5network5 5.10.1+dfsg-7 ii
> libqt5svg5 5.10.1-2 ii libqt5widgets5 5.10.1+dfsg-7 ii libstdc++6
> 8.1.0-5

> Versions of packages nheko recommends: ii ca-certificates 20170717

> nheko suggests no packages.

> -- no debconf information

-- 
Hubert Chathi  -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368

Bug#910556: Close file right away after reading

[積丹尼 Dan Jacobson]

X-Debbugs-Cc: Kim Saunders , Peter Åstrand 

Package: xclip
Version: 0.12+svn84-4+b1

Can't the file please be closed right away, and not left hanging open?

$ xclip < /some/file
$ jobs
$ lsof|grep /some/file
xclip 3674   jidanni0r  REG   8,66 1401 
 66892 /some/file

Bug#910405: nheko: empty device name causes issue in e2ee chat room

[Hubert Chathi]

package nheko
forwarded 910405 https://github.com/mujx/nheko/issues/458
thanks

Hi Ghost.

Thanks for the report.  It does look like an upstream issue, so I have
forwarded it upstream.

Hubert

On Sat, 06 Oct 2018 01:34:10 +, ghost  said:

> Package: nheko Version: 0.6.1-1 Severity: normal

> Dear Maintainer,

>* What led up to the situation?  If the device name is empty in the
> login process (which does not warn anything when the field is left as
> is), the nheko session will not show up in other clients (riot.im in
> my case). Messages sent to chat rooms with e2ee enabled either don't
> get encrypted for existing rooms, or get encrypted but appear as
> unknown in other clients for rooms created by the nheko session.

>Since the device name is needed for the session to be recognised by
> other clients, I would expect it either - a. be a required field in
> the login process.  b. has a default value to be used when not
> specified.

>I believe this will need to be forwarded upstream, but since Debian
> discourages directly filing bugs to upstream, here I am...

> Cheers.

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

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

> Versions of packages nheko depends on: ii libboost-atomic1.67.0
> 1.67.0-7 ii libboost-chrono1.67.0 1.67.0-7 ii libboost-date-time1.67.0
> 1.67.0-7 ii libboost-iostreams1.67.0 1.67.0-7 ii libboost-random1.67.0
> 1.67.0-7 ii libboost-regex1.67.0 1.67.0-7 ii libboost-system1.67.0
> 1.67.0-7 ii libboost-thread1.67.0 1.67.0-7 ii libc6 2.27-6 ii
> libcmark0 0.28.3-1 ii libgcc1 1:8.2.0-7 ii liblmdb0 0.9.22-1 ii
> libolm2 2.2.2+git20170526.0fd768e+dfsg-1 ii libqt5concurrent5
> 5.11.1+dfsg-9 ii libqt5core5a 5.11.1+dfsg-9 ii libqt5dbus5
> 5.11.1+dfsg-9 ii libqt5gui5 5.11.1+dfsg-9 ii libqt5multimedia5
> 5.11.1-2 ii libqt5network5 5.11.1+dfsg-9 ii libqt5svg5 5.11.1-2 ii
> libqt5widgets5 5.11.1+dfsg-9 ii libsodium23 1.0.16-2 ii libssl1.1
> 1.1.0h-4 ii libstdc++6 8.2.0-7 ii zlib1g 1:1.2.11.dfsg-1

> Versions of packages nheko recommends: ii ca-certificates 20170717

> nheko suggests no packages.

> -- no debconf information

-- 
Hubert Chathi  -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368

Bug#910555: libkf5notifications5: KStatusNotifierItem No Icon set infinite loop

[David Fries]

Package: libkf5notifications5
Version: 5.28.0-1
Severity: normal

Dear Maintainer,

I started X with fvwm and stalonetray.

If I run korgac with the following theme,
export QT_QPA_PLATFORMTHEME=kde

I get the following repeated over and over, while it is eating up the
CPU.
QSystemTrayIcon::setVisible: No Icon set

It looks like it is in an infinite recursion and it will eventually
crash.

#57045 0x7fffd5fdcb57 in ?? ()
   from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/KDEPlasmaPlatformTheme.so
#57046 0x73b63a54 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#57047 0x73b8217e in ?? ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#57048 0x73b636cd in QSystemTrayIcon::setVisible(bool) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#57049 0x7645d5f6 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#57050 0x7645f2de in ?? ()
   from /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#57051 0x764607c3 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#57052 0x76460cce in KStatusNotifierItem::KStatusNotifierItem(QObject*)
() from /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#57053 0x7fffd5fdcb57 in ?? ()
   from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platformthemes/KDEPlasmaPlatformTheme.so
#57054 0x73b63a54 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#57055 0x73b8217e in ?? ()
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#57056 0x73b636cd in QSystemTrayIcon::setVisible(bool) ()
---Type  to continue, or q  to quit---
   from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#57057 0x7645d5f6 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#57058 0x7645f2de in ?? ()
   from /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#57059 0x764607c3 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#57060 0x76460cce in KStatusNotifierItem::KStatusNotifierItem(QObject*)
() from /usr/lib/x86_64-linux-gnu/libKF5Notifications.so.5
#57061 0x55576d04 in ?? ()
#57062 0x55569d35 in ?? ()
#57063 0x555663af in ?? ()
#57064 0x723942e1 in __libc_start_main (main=0x55565ee0, argc=1, 
argv=0x7fffe8c8, init=, fini=, 
rtld_fini=, stack_end=0x7fffe8b8)
at ../csu/libc-start.c:291
#57065 0x555665da in _start ()

If I don't set the theme it will run, but other KDE based applications
fail to find icons.  I would expect if it can't find an icon that it
would use a substitute, solid color, or something that will allow the
application to run properly rather than eat up the CPU, ram, and
eventually crash.

I've looked at the korgac source and don't see it can do anything,
should it be KDEPlasmaPlatformTheme.so instead?

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

Kernel: Linux 4.18.0+ (SMP w/4 CPU cores)
Locale: LANG=, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15), LANGUAGE= 
(charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libkf5notifications5 depends on:
ii  libc6 2.24-11+deb9u3
ii  libdbusmenu-qt5-2 0.9.3+16.04.20160218-1
ii  libkf5codecs5 5.28.0-1+b2
ii  libkf5configcore5 5.28.0-2
ii  libkf5coreaddons5 5.28.0-2
ii  libkf5notifications-data  5.28.0-1
ii  libkf5windowsystem5   5.28.0-2
ii  libphonon4qt5-4   4:4.9.0-4
ii  libqt5core5a  5.7.1+dfsg-3+b1
ii  libqt5dbus5   5.7.1+dfsg-3+b1
ii  libqt5gui55.7.1+dfsg-3+b1
ii  libqt5widgets55.7.1+dfsg-3+b1
ii  libqt5x11extras5  5.7.1~20161021-2
ii  libstdc++66.3.0-18+deb9u1
ii  phonon4qt54:4.9.0-4

libkf5notifications5 recommends no packages.

libkf5notifications5 suggests no packages.

-- no debconf information

Bug#890819: packagekit: Update while booting always fails

[Joel Cross]

>  > Output of the command `pkcon offline-status` is as follows:
>  > Status: Failed
>  > ErrorCode:failed-initialization
> [...]
> 
> Could you please retry again? Is this fixed? I tried today and it was 
> working for me with the current version in unstable (1.1.10-1)
> 
This hasn't been a problem for me for some time. Hopefully this means it has 
already been fixed upstream!

Bug#910554: RM: libayatana-ido3-0.4-dev -- RoQA; NBS, now a virtual package.

[peter green]

Package: ftp.debian.org

libayatana-ido3-0.4-dev is no longer built by ayatana-ido, when I look at the 
cruft report to see why it isn't being cleaned up I see


* source package ayatana-ido version 0.4.4-1 no longer builds
   binary package(s): libayatana-ido3-0.4-dev
   on 
amd64,arm64,armel,armhf,hurd-i386,i386,kfreebsd-amd64,kfreebsd-i386,mips,mips64el,mipsel,ppc64el,s390x
   - suggested command:
 dak rm -m "[auto-cruft] NBS (no longer built by ayatana-ido)" -s unstable 
-a 
amd64,arm64,armel,armhf,hurd-i386,i386,kfreebsd-amd64,kfreebsd-i386,mips,mips64el,mipsel,ppc64el,s390x
 -p -R -b libayatana-ido3-0.4-dev
   - broken Build-Depends:
 cairo-dock-plug-ins: libayatana-ido3-0.4-dev
 mate-indicator-applet: libayatana-ido3-0.4-dev

When I look those two packages up on packages.debian.org I see that 
libayatana-ido3-0.4-dev is now a virtual package provided by 
libayatana-ido3-dev, so removing it will not actually break the 
build-dependencies.

Can you remove libayatana-ido3-0.4-dev from unstable so that ayatana-ido can 
migrate to testing?

Bug#910553: nautilus-dropbox: FTBFS in sid: Package 'gl', required by 'epoxy', not found

[Andreas Beckmann]

Source: nautilus-dropbox
Version: 2015.10.28-1
Severity: serious
Tags: sid buster
Justification: fails to build from source (but built successfully in the past)

Hi,

nautilus-dropbox cannot be built any longer in a current sid pbuilder
environment:

...
checking for NAUTILUS... no
configure: error: Package requirements (libnautilus-extension >= 2.16.0) were 
not met:

Package 'gl', required by 'epoxy', not found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables NAUTILUS_CFLAGS
and NAUTILUS_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.


Cheers,

Andreas


nautilus-dropbox_2015.10.28-1.log.gz
Description: application/gzip

Bug#910552: gnome-shell fails to see my GPU

[Pierre-Elliott Bécue]

Le lundi 08 octobre 2018 à 01:42:29+0200, Pierre-Elliott Bécue a écrit :
> Source: gnome-shell
> Version: 3.30.0-3
> Severity: important
> 
> Hi,
> 
> Since my upgrade to gnome-shell 3.30.0-3, gdm3 is no longer starting
> properly.
> 
> My computer is under testing, and runs a 4.18.0-1 kernel with
> nvidia-kernel-dkms 390.87-2.
> 
> The issue seems to reside in these specific lines:
> Oct  8 01:18:06 jaatynyt gnome-shell[7822]: meta_kms_resources_init
> failed: Calling drmModeGetResources(
> Oct  8 01:18:06 jaatynyt gnome-shell[7822]: Failed to create backend: No
> GPUs with outputs found
>
> [snip]

Apparently, these log lines appeared in my syslog for quite some time, even
before the current issue I'm meeting.

To describe it, after the end of the boot process, I get a blank screen with
only a blinking cursor at the top-left part of the screen. No debug, no way
to get any intel.

lightdm starts properly, same for xdm.

I believe it's connected to the gpu, I'll run some tests.

Cheers.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#885638: Patch

[Yavor Doganov]

tags 885638 + patch
thanks

Here is a minimalistic patch that fixes this bug.

The GNOME people have ditched several documentation systems in the
past years; I'm not really sure what is the current one.  Probably
yelp-tools or yelp-something.

Switching to another system is likely to require changes in the manual
itself as well as the installation location.  The approach I suggest,
while suboptimal, will work as long as Yelp is able to display URIs
with the "ghelp:" prefix.

P.S.  The gnome-common B-D seems unnecessary so removed as well.
>From 6e72731f5cc684d2a50c76e0483bbcf373fd03d0 Mon Sep 17 00:00:00 2001
From: Yavor Doganov 
Date: Mon, 8 Oct 2018 02:14:05 +0300
Subject: [PATCH 3/3] Get rid of rarian-compat B-D (#885638)

---
 debian/control  |  2 +-
 debian/gbonds-data.install  |  1 -
 debian/patches/no-rarian-compat | 19 +++
 debian/patches/series   |  1 +
 4 files changed, 21 insertions(+), 2 deletions(-)
 create mode 100644 debian/patches/no-rarian-compat

diff --git a/debian/control b/debian/control
index 6b7f3e5..194ec8c 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: gnome
 Priority: optional
 Maintainer: Richard Laager 
 Uploaders: tony mancill 
-Build-Depends: debhelper (>= 10), dpkg-dev (>= 1.16.1), libgtk-3-dev, 
libxml2-dev (>= 2.4.23), libtool, intltool, gnome-common, rarian-compat
+Build-Depends: debhelper (>= 10), dpkg-dev (>= 1.16.1), libgtk-3-dev, 
libxml2-dev (>= 2.4.23), libtool, intltool
 Standards-Version: 4.1.3
 Vcs-Browser: https://github.com/rlaager/gbonds-pkg
 Vcs-Git: https://github.com/rlaager/gbonds-pkg.git
diff --git a/debian/gbonds-data.install b/debian/gbonds-data.install
index 7975c59..40f61f4 100644
--- a/debian/gbonds-data.install
+++ b/debian/gbonds-data.install
@@ -6,4 +6,3 @@ usr/share/gnome
 usr/share/mime
 usr/share/mime-info
 usr/share/pixmaps
-usr/share/omf
diff --git a/debian/patches/no-rarian-compat b/debian/patches/no-rarian-compat
new file mode 100644
index 000..c3f886e
--- /dev/null
+++ b/debian/patches/no-rarian-compat
@@ -0,0 +1,19 @@
+Description: Do not install the .omf file.
+ This makes it possible to remove rarian-compat as build-dependency.
+Bug-Debian: https://bugs.debian.org/885638
+Author: Yavor Doganov 
+Forwarded: no
+Last-Update: 2018-10-08
+---
+
+--- gbonds-pkg.orig/help/C/Makefile.am
 gbonds-pkg/help/C/Makefile.am
+@@ -1,7 +1,7 @@
+ figdir = figures
+ docname = gbonds
+ lang = C
+-omffile = gbonds-C.omf
++omffile =
+ entities =
+ 
+ include $(top_srcdir)/xmldocs.make
diff --git a/debian/patches/series b/debian/patches/series
index 14d39ff..532b776 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -16,3 +16,4 @@ desktop-file-keywords
 replace-g_strcasecmp
 gtk3-port
 gsettings-port
+no-rarian-compat
-- 
2.19.1

Bug#910538: RFS: vitetris/0.57.2-1 [ITP]

[Pierre-Elliott Bécue]

Le lundi 08 octobre 2018 à 01:08:00+0200, Baptiste BEAUPLAT a écrit :
> Hello Pierre-Elliott,
> 
> > Dear Baptiste,
> >
> > I get a weird error when I try to download your GPG key to check the package
> > you made.
> >
> > `---> gpg --search-keys 2DE24895313C5DA7F089E14E17494B10795DD733
> > gpg: data source: https://[2a02:c205:3001:3626::1]:443
> > (1) lyknode 
> > Baptiste BEAUPLAT 
> >   256 bit EDDSA key 1EDBAA3C6926AF92, créé : 2017-08-05, expire : 
> > 2019-08-05
> > Keys 1-1 of 1 for "2DE24895313C5DA7F089E14E17494B10795DD733".  Entrez le ou 
> > les nombres, (S)uivant, ou (Q)uitter > 1
> > gpg: key 1EDBAA3C6926AF92: no user ID for key signature packet of class 13
> > gpg:   Quantité totale traitée : 1
> >
> > Is your GPG key actually properly uploaded?
> 
> The key is fine but gpg 2.1.18 seems to have difficulties with some ECC
> keys. There is a fix for testing and stable-bpo.
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906545
> 
> I've tried with a more recent version and it works.
> >  - The install part of the makefile seem to install
> >usr/share/doc/vitetris/licence.txt, which should not happen. You can 
> > either
> >alter debian/rules to remove this file or ignore this suggestion.
> Got a info warning from lintian for that as well. I'll remove the file
> and re-upload the package.
> 
> Thanks a lot for your comments.

Ack, I'll review & upload tomorrow if I find nothing more.

Cheers!

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#910551: RFS: lebiniou/3.25-1 -- displays images that evolve with sound

[Olivier Girondel]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: lebiniou
   Version : 3.25-1
   Upstream Author : Olivier Girondel 
 * URL : https://biniou.net
 * License : GPL-2+
   Section : graphics

It builds those binary packages:

  lebiniou - displays images that evolve with sound

The package appears to be lintian-clean.

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

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

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

  dget -x
https://mentors.debian.net/debian/pool/main/l/lebiniou/lebiniou_3.25-1.dsc

Changes since the last upload:

  * New upstream release 3.25.
  * debian/compat: Upgrade to 10.
  * debian/control: Standards-Version: 4.2.1.
  * debian/control: Update Homepage.
  * debian/control: Priority: optional.
  * debian/control: Vcs-Browser: https://gitlab.com/lebiniou/lebiniou.
  * debian/control: Vcs-Git: https://gitlab.com/lebiniou/lebiniou.git.
  * debian/control: Build-Depends: Remove autotools-dev.
  * debian/control: Testsuite: autopkgtest.
  * debian/copyright: Update copyright years.
  * debian/copyright: Update Source URL.
  * debian/copyright: Use secure copyright format URI.
  * debian/rules: Remove --parallel.
  * debian/rules: Remove --with autotools_dev.
  * debian/tests/control: Added.
  * debian/watch: version=4.
  * debian/watch: opts="pgpmode=none".
  * debian/watch: Use secure URI.

Regards,
  Olivier Girondel

Bug#886080: Port to GSettings

[Yavor Doganov]

tags 886080 + patch
thanks

Attached is a patch fixing this bug.

If you wonder about Recommends: gconf2, see the discussion at #907826
[1].  It can be dropped during the bullseye development cycle along
with the migration code.

[1] https://bugs.debian.org/907826
>From 587c8718f1e73ebf604b2cafede578dd5c6eeb59 Mon Sep 17 00:00:00 2001
From: Yavor Doganov 
Date: Mon, 8 Oct 2018 01:18:22 +0300
Subject: [PATCH 2/3] Port to GSettings (#886080)

---
 debian/control|   3 +-
 debian/gbonds-data.install|   2 +
 debian/patches/gsettings-port | 635 ++
 debian/patches/series |   1 +
 4 files changed, 640 insertions(+), 1 deletion(-)
 create mode 100644 debian/patches/gsettings-port

diff --git a/debian/control b/debian/control
index e75016d..6b7f3e5 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,7 @@ Section: gnome
 Priority: optional
 Maintainer: Richard Laager 
 Uploaders: tony mancill 
-Build-Depends: debhelper (>= 10), dpkg-dev (>= 1.16.1), libgtk-3-dev, 
libgconf2-dev, libxml2-dev (>= 2.4.23), libtool, intltool, gnome-common, 
rarian-compat
+Build-Depends: debhelper (>= 10), dpkg-dev (>= 1.16.1), libgtk-3-dev, 
libxml2-dev (>= 2.4.23), libtool, intltool, gnome-common, rarian-compat
 Standards-Version: 4.1.3
 Vcs-Browser: https://github.com/rlaager/gbonds-pkg
 Vcs-Git: https://github.com/rlaager/gbonds-pkg.git
@@ -12,6 +12,7 @@ Homepage: http://gbonds.sourceforge.net
 Package: gbonds
 Architecture: any
 Depends: gbonds-data (>= ${source:Upstream-Version}), gbonds-data (<< 
${source:Upstream-Version}-z), ${shlibs:Depends}, ${misc:Depends}
+Recommends: gconf2
 Description: U.S. Savings Bond inventory program for GNOME
  GBonds is a Savings Bond inventory program for the GNOME desktop environment.
  It allows you to track the current redemption value and performance of your
diff --git a/debian/gbonds-data.install b/debian/gbonds-data.install
index 40a73a6..7975c59 100644
--- a/debian/gbonds-data.install
+++ b/debian/gbonds-data.install
@@ -1,5 +1,7 @@
 usr/share/application-registry
+usr/share/GConf
 usr/share/gbonds
+usr/share/glib-2.0
 usr/share/gnome
 usr/share/mime
 usr/share/mime-info
diff --git a/debian/patches/gsettings-port b/debian/patches/gsettings-port
new file mode 100644
index 000..ad9c0a6
--- /dev/null
+++ b/debian/patches/gsettings-port
@@ -0,0 +1,635 @@
+Description: Port to GSettings.
+Bug-Debian: https://bugs.debian.org/886080
+Author: Yavor Doganov 
+Forwarded: no
+Last-Update: 2018-10-08
+---
+
+
+--- gbonds-pkg.orig/configure.in
 gbonds-pkg/configure.in
+@@ -30,7 +30,6 @@
+ LIBGNOMEPRINTUI_REQUIRED=2.2.0
+
+ PKG_CHECK_MODULES(GBONDS, gtk+-3.0 >= $GTK_REQUIRED \
+-gconf-2.0 \
+ libxml-2.0 >= $LIBXML_REQUIRED \
+ )
+ 
+@@ -55,6 +54,8 @@
+ AC_SUBST(GETTEXT_PACKAGE)
+ AC_DEFINE_UNQUOTED(GETTEXT_PACKAGE, "$GETTEXT_PACKAGE", [Gettext package])
+ 
++GLIB_GSETTINGS
++
+ dnl Add the languages which your application supports here.
+ ALL_LINGUAS=""
+ AM_GLIB_GNU_GETTEXT
+--- gbonds-pkg.orig/src/ui.c
 gbonds-pkg/src/ui.c
+@@ -21,8 +21,6 @@
+  */
+ #include 
+ 
+-#include 
+-
+ #include "ui.h"
+ #include "commands.h"
+ #include "recent.h" 
+@@ -427,10 +425,10 @@
+ static void
+ set_app_main_toolbar_style (GtkBuilder *ui_component)
+ {
+-  GConfClient *client;
++  GtkSettings *settings;
+   GtkWidget   *widget;
+   GtkCheckMenuItem *item;
+-  gboolean labels;
++  GtkToolbarStyle   style;
+ 
+   gb_debug (DEBUG_UI, "START");
+ 
+@@ -457,35 +455,18 @@
+   {
+   case GB_TOOLBAR_SYSTEM:
+   
+-  client = gconf_client_get_default ();
+-  if (client == NULL) 
++  settings = gtk_settings_get_default ();
++  if (!settings)
+   return;
+ 
+-  labels = gconf_client_get_bool (client, 
+-  
"/desktop/gnome/interface/toolbar-labels", NULL);
+-
+-  g_object_unref (G_OBJECT (client));
++  g_object_get (settings, "gtk-toolbar-style",
++&style, NULL);
+   item = GTK_CHECK_MENU_ITEM (gtk_builder_get_object
+   (ui_component,
+"MainToolbarSystem"));
+-  
+-  if (labels)
+-  {   
+-  gtk_toolbar_set_style (GTK_TOOLBAR (widget),
+- GTK_TOOLBAR_BOTH);
+-  if (!gtk_check_menu_item_get_active (item))
+-  gtk_check_menu_item_set_active (item,
+-  TRUE);
+-  
+-  }
+

Bug#910550: RFS: lebiniou-data-3.25-1 -- datafiles for Le Biniou

[Olivier Girondel]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "lebiniou-data":

 * Package name: lebiniou-data
   Version : 3.25-1
   Upstream Author : Olivier Girondel 
 * URL : https://biniou.net
 * License : GPL-2+
   Section : graphics

It builds those binary packages:

lebiniou-data - datafiles for Le Biniou

The package appears to be lintian-clean.

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

  https://mentors.debian.net/package/lebiniou-data


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

  dget -x
https://mentors.debian.net/debian/pool/main/l/lebiniou-data/lebiniou-data_3.25-1.dsc

Changes since the last upload:

  * New upstream release 3.25.
  * debian/compat: Upgrade to 10.
  * debian/control: Standards-Version: 4.2.1.
  * debian/control: Update Homepage.
  * debian/control: Priority: optional.
  * debian/control: Build-Depends: debhelper-compat (= 10).
  * debian/control: Vcs-Browser: https://gitlab.com/lebiniou/lebiniou-data.
  * debian/control: Vcs-Git: https://gitlab.com/lebiniou/lebiniou-data.git.
  * debian/control: Multi-Arch: foreign.
  * debian/copyright: Update copyright years.
  * debian/copyright: Update Source URL.
  * debian/copyright: Use secure copyright format URI.
  * debian/watch: version=4.
  * debian/watch: opts="pgpmode=none".
  * debian/watch: Use secure URI.

Regards,
  Olivier Girondel

Bug#910538: RFS: vitetris/0.57.2-1 [ITP]

[Baptiste BEAUPLAT]

Hello Pierre-Elliott,

> Dear Baptiste,
>
> I get a weird error when I try to download your GPG key to check the package
> you made.
>
> `---> gpg --search-keys 2DE24895313C5DA7F089E14E17494B10795DD733
> gpg: data source: https://[2a02:c205:3001:3626::1]:443
> (1)   lyknode 
>   Baptiste BEAUPLAT 
> 256 bit EDDSA key 1EDBAA3C6926AF92, créé : 2017-08-05, expire : 
> 2019-08-05
> Keys 1-1 of 1 for "2DE24895313C5DA7F089E14E17494B10795DD733".  Entrez le ou 
> les nombres, (S)uivant, ou (Q)uitter > 1
> gpg: key 1EDBAA3C6926AF92: no user ID for key signature packet of class 13
> gpg:   Quantité totale traitée : 1
>
> Is your GPG key actually properly uploaded?

The key is fine but gpg 2.1.18 seems to have difficulties with some ECC
keys. There is a fix for testing and stable-bpo.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906545

I've tried with a more recent version and it works.
>  - The install part of the makefile seem to install
>usr/share/doc/vitetris/licence.txt, which should not happen. You can either
>alter debian/rules to remove this file or ignore this suggestion.
Got a info warning from lintian for that as well. I'll remove the file
and re-upload the package.

Thanks a lot for your comments.

-- 
Baptiste BEAUPLAT - lyknode




signature.asc
Description: OpenPGP digital signature

Bug#907725: Fwd: Appropriate Section for PCF Fonts

[Paul Hardy]

Russ,

On Sun, Oct 7, 2018 at 3:59 PM Russ Allbery  wrote:
>
> Paul Hardy  writes:
>
> > Thank you for dealing with bug #907725 ("xfonts packages are not using
> > the x11 section in practice").  I was told that it was up to the FTP
> > Masters, so I wrote the below email to them in July.  I have not yet
> > received a response, but looking at the NEW queue it is obvious how
> > swamped they are so I wasn't expecting a rapid response.
>
> Just in case you weren't already aware of this little-known corner of how
> the Debian archive works: the section of every package currently in the
> archive is set via the overrides maintained by ftp-master, not by the
> section specified in the packaging files.  This is for somewhat esoteric
> and historical reasons, but the package metadata is basically just a hint.
>
> Therefore, even though you didn't get a reply, ftp-master has in a sense
> already made their decision clear: the fonts currently in the archive are
> in the fonts section.  If ftp-master had wanted them in a different
> section, that's entirely under their control, and they could have just
> made that change.

Thanks for taking the time to explain this.  I was aware of the FTP
package mapping in principle, but do not know the actual mechanics of
it.  The lintian message seemed like it might signal some upcoming
change in placing those files, and I wanted to do the right thing
before the freeze.

Take care,


Paul Hardy

Bug#910543: bfs 1.2.4-1 fstype test fails on Hurd

[Samuel Thibault]

Samuel Thibault, le lun. 08 oct. 2018 00:02:03 +0200, a ecrit:
> Chris Lamb, le dim. 07 oct. 2018 22:40:08 +0100, a ecrit:
> >  
> > https://github.com/tavianator/bfs/commit/85caf29cfd2f40ef10ed76d425bb89a5f8f45a1a
> > 
> > .. but that was in 1.2.2-2.
> > 
> > debian-hurd@, any input here? Any reason why /proc/mounts might not
> > exist, or...?
> 
> I have seen /proc not getting mounted for yet-unknow reasons, thus
> making some builds fail. I have given back bfs.

Yep, worked fine now.

Samuel

Bug#910549: nmu: xapian-core_1.4.7-2

[Olly Betts]

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

Upstream xapian-core 1.4.6 added C++11 move constructors and move
assignment operators when code using the xapian API is built with a
C++11 or newer compiler, which GCC in unstable is by default.

The compiler will very likely find places to use the move versions
implicitly, so a package built against libxapian-dev >= 1.4.6-1 is
unlikely to work with libxapian30 << 1.4.6.1 due to missing symbols.
We'll often get away with this because the packages will generally
be upgraded together, so that's probably why there's not been a flood
of reports.  This breakage was reported by a user who tried to
perform a large upgrade by separately upgrading aptitude first:

https://bugs.debian.org/910110

1.4.7-4 adds the appropriate dependency to libxapian30.shlibs, so any
packages built against libxapian-dev 1.4.6-1 to 1.4.7-3 inclusive should
be rebuilt so they automatically depend on libxapian30 (>= 1.4.6-1~)
instead of just libxapian30.

I've extracted a list of such packages based on the buildinfo files on
mirror.ftp-master.d.o (thanks to pabs for suggesting this):

nmu pinot_1.05-2 . ANY . -m 'Rebuild against libxapian30 with dependency in 
shlibs'
dw pinot_1.05-2 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu zeitgeist_1.0.1-0.2 . ANY . -m 'Rebuild against libxapian30 with dependency 
in shlibs'
dw zeitgeist_1.0.1-0.2 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu maildir-utils_1.0-6 . ANY . -m 'Rebuild against libxapian30 with dependency 
in shlibs'
dw maildir-utils_1.0-6 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu baloo-kf5_5.49.0-1 . ANY . -m 'Rebuild against libxapian30 with dependency 
in shlibs'
dw baloo-kf5_5.49.0-1 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu recoll_1.24.1-3 . ANY . -m 'Rebuild against libxapian30 with dependency in 
shlibs'
dw recoll_1.24.1-3 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu plasma-desktop_5.13.5-1 . ANY . -m 'Rebuild against libxapian30 with 
dependency in shlibs'
dw plasma-desktop_5.13.5-1 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu plasma-workspace_5.13.5-1 . ANY . -m 'Rebuild against libxapian30 with 
dependency in shlibs'
dw plasma-workspace_5.13.5-1 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu aptitude_0.8.11-3 . ANY . -m 'Rebuild against libxapian30 with dependency 
in shlibs'
dw aptitude_0.8.11-3 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu packagesearch_2.7.9 . ANY . -m 'Rebuild against libxapian30 with dependency 
in shlibs'
dw packagesearch_2.7.9 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu cyrus-imapd_2.5.11-1 . ANY . -m 'Rebuild against libxapian30 with 
dependency in shlibs'
dw cyrus-imapd_2.5.11-1 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu akonadiconsole_18.08.1-1 . ANY . -m 'Rebuild against libxapian30 with 
dependency in shlibs'
dw akonadiconsole_18.08.1-1 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu akonadi-search_18.08.1-1 . ANY . -m 'Rebuild against libxapian30 with 
dependency in shlibs'
dw akonadi-search_18.08.1-1 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu notmuch_0.28~rc0-1 . ANY . -m 'Rebuild against libxapian30 with dependency 
in shlibs'
dw notmuch_0.28~rc0-1 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'
nmu libsearch-xapian-perl_1.2.25.2-1 . ANY . -m 'Rebuild against libxapian30 
with dependency in shlibs'
dw libsearch-xapian-perl_1.2.25.2-1 . ANY . -m 'libxapian-dev (>= 1.4.7-4)'

The new xapian-core was uploaded close to two days ago and has
now built everywhere except kfreebsd-*.  I'll recheck in a week in
case there any further binary uploads built against the old xapian-core,
and follow-up with another request if necessary.

Cheers,
Olly


signature.asc
Description: PGP signature

Bug#910548: base-files - please consider adding /usr/share/common-licenses/Unicode-Data

[Paul Hardy]

Package: base-files
Severity: wishlist
Tags: patch

Hello,

I recently formatted the Unicode Data license for the d/copyright file
of a Debian package that I created.  I thought I would offer it to
Debian if you are interested.  You probably do not want the Copyright
stanza, and you might not want the Comment stanza, but I erred on the
side of too much rather than too little.

Unicode data files are used in a number of free software packages,
such as linux-libc-dev and the Linux kernel itself.  Use of Unicode
data in software is likely to continue growing over time.  Thus you
might find this useful.

Thank you,


Paul Hardy


Unicode-Data.sig
Description: PGP signature


Unicode-Data
Description: Binary data

Bug#909238: mailman3 breaks mailman-hyperkitty autopkgtest

[Jonas Meurer]

Hi Paul,

Am 20.09.2018 um 09:34 schrieb Paul Gevers:
> With a recent upload of mailman3 the autopkgtest of mailman-hyperkitty
> fails in testing when that autopkgtest is run with the binary packages
> of mailman3 from unstable. It passes when run with only packages from
> testing. It fails in unstable (with mailman-hyperkitty 1.1.0-8). In
> tabular form:
> pass   pass   fail   fail
> mailman3testingtesting3.2.0-13.2.0-1
> mailman-hyperkitty  testing1.1.0-8testing1.1.0-8
> all others  testingtestingtestingunstable
> 
> I copied some of the output at the bottom of this report.
> 
> Currently this regression is contributing to the delay of the migration
> of mailman3 to testing [1]. Due to the nature of this issue, I filed
> this bug report against both packages. Can you please investigate the
> situation and reassign the bug to the right package? If needed, please
> change the bug's severity.

Thanks for the report and in general thanks a ton for all the great
autopkgtest related work!

With the latest uploads of mailman3 and mailman-hyperkitty, this bug
should be fixed now.

Cheers
 jonas



signature.asc
Description: OpenPGP digital signature

Bug#891937: [Pkg-mailman-hackers] Bug#891937: mailman3-full install issues

[Jonas Meurer]

Hey Markus,

On Wed, 18 Apr 2018 15:33:11 +0200 Markus Gschwendt
 wrote:
> On Wed, 2018-04-18 at 12:06 +0200, Jonas Meurer wrote:
> > do you still encounter this problem?
> 
> Yes. At least with mailman3 3.1.1-8

Sorry to poke you again. Can you still reproduce it with latest mailman3
3.2 packages from Debian unstable? Did you try to do a fresh
installation of mailman3 in the meantime?

> 
> >  I bet there's something wrong on
> > your side. Mailman3 works fine with Exim4 and if you configured it
> > correctly, it certainly doesn't run the Postfix postmap command.
> 
> It's an install of the mailman3-Debian-Sid packages. Nothing else is on
> that machine.
> 
> exim4: 4.90.1-5
> nginx-light: 1.13.12-1
> mailman3: 3.1.1-9
> 
> I just did upgrade from 3.1.1-8 to 3.1.1-9 and get this on restarting
> mailman:
> 
> service mailman3 stopTraceback (most recent call last):
>   File "/usr/lib/mailman3/bin/master", line 11, in 
> load_entry_point('mailman==3.1.1', 'console_scripts', 'master')()
>   File "/usr/lib/python3/dist-packages/mailman/bin/master.py", line
> 528, in main
> with open(config.PID_FILE, 'w') as fp:
> PermissionError: [Errno 13] Permission denied:
> '/run/mailman3/master.pid'

This permission error smells suspcious to me. /run/mailman/ should be
owned by 'list'list' and the mailman3 daemon should put the pid file
into it with same ownership.

Maybe something got screwed during installation/configuration/debugging
of the packages in early state. We indeed had some nasty permission bugs
in the first releases of mailman3 packages. The latest packages should
have fixed them (at least the ones we know of).

If you don't discover this bug anymore or are unable to reproduce, I'd
like to close the bugreport.

Cheers
 jonas



signature.asc
Description: OpenPGP digital signature

Bug#908329: lightdm: LightDM shuts down the screen on lock and won't turn it on

[beatstream]

Package: lightdm
Version: 1.26.0-2
Followup-For: Bug #908329

I can confirm that bug on my laptop, but not only after screen lock.

After closing and then opening the lid screen is turning on, but nothing is
displayed except mouse pointer. If I switch virt console to text and back to
gui (i.e. tty1 -> tty7) all displaying correctly.

In mate-power-manager (using mate 1.20.3) "When laptop lid is closed" I was
selected "Blank screen", but
when I select "Do nothing", problem disappears.



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 4.18.0-1-686-pae (SMP w/2 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 lightdm depends on:
ii  adduser3.118
ii  dbus   1.12.10-1
ii  debconf [debconf-2.0]  1.5.69
ii  libaudit1  1:2.8.4-2
ii  libc6  2.27-6
ii  libgcrypt201.8.3-1
ii  libglib2.0-0   2.58.1-2
ii  libpam-systemd 239-10
ii  libpam0g   1.1.8-3.8
ii  libxcb11.13-3
ii  libxdmcp6  1:1.1.2-3
ii  lightdm-gtk-greeter [lightdm-greeter]  2.0.5-1
ii  lsb-base   9.20170808

Versions of packages lightdm recommends:
ii  xserver-xorg  1:7.7+19

Versions of packages lightdm suggests:
ii  accountsservice  0.6.45-1
ii  upower   0.99.8-2
pn  xserver-xephyr   

-- debconf information:
  lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm

Bug#907725: Fwd: Appropriate Section for PCF Fonts

[Russ Allbery]

Paul Hardy  writes:

> Thank you for dealing with bug #907725 ("xfonts packages are not using
> the x11 section in practice").  I was told that it was up to the FTP
> Masters, so I wrote the below email to them in July.  I have not yet
> received a response, but looking at the NEW queue it is obvious how
> swamped they are so I wasn't expecting a rapid response.

Just in case you weren't already aware of this little-known corner of how
the Debian archive works: the section of every package currently in the
archive is set via the overrides maintained by ftp-master, not by the
section specified in the packaging files.  This is for somewhat esoteric
and historical reasons, but the package metadata is basically just a hint.

Therefore, even though you didn't get a reply, ftp-master has in a sense
already made their decision clear: the fonts currently in the archive are
in the fonts section.  If ftp-master had wanted them in a different
section, that's entirely under their control, and they could have just
made that change.

-- 
Russ Allbery (r...@debian.org)   

Bug#894256: [Pkg-mailman-hackers] Bug#894256: Bug#894256: mailman3 wants to take away mailman.cfg from mailman3-core

[Jonas Meurer]

Am 17.09.2018 um 12:51 schrieb Jonas Meurer:
> Hi Björn,
> 
> Am 14.08.2018 um 00:08 schrieb Pierre-Elliott Bécue:
>> Le jeudi 07 juin 2018 à 21:51:01+0200, Bjoern Franke a écrit :
>>> Hi Pierre,
>>>
>>>
 Indeed, the file is owned by both packages and as they conflict, the latter
 wants to get rid of the one from the former. I'm not sure there's anything
 we can do to smoothen the transition.

 I'll ask out for some adivce in case I missed something, but it's possible
 that all people having installed -core will have to handle manually the
 transition and its side effects.
>>>
>>> Any news on this issue?
>>
>> Actually, yes.
>>
>> I think I have a solution, but it'll require some testing.
> 
> Since this bugreport is about the binary package rename mailman3-core ->
> mailman3, which was a one-time change and won't affect any new users, I
> wonder whether you fixed the issue on your system in the meantime.
> 
> I'd like to close the bugreport as mailman3-core is no longer available
> anywhere in the archives.

Doing so now.

Cheers
 jonas




signature.asc
Description: OpenPGP digital signature

Bug#910541: diffoscope: filing bugs on diffoscope is cumbersome for non-Debian contributors

[Marek Marczykowski-Górecki]

On Sun, 07 Oct 2018 22:33:49 +0100 Chris Lamb  
wrote:
> > - the project on salsa has issues disabled (but would require a login on
> >   salsa anyway), still filing bugs in a webbrowser is something many
> >   people want to do today, so I think maybe we should enable issues?
> 
> No strong objection to the principle except that we would then have
> some duplication between the two trackers.

Filling bugs in web browser is indeed something many people expect. But
having two issue trackers introduce a lot of problems. Add to your list
ambiguity of issue numbers.

What about providing appropriate "mailto" link to open new issue on BTS,
including all the magic headers, bug template etc?
Like the "reply" one existing already on BTS (I'm using it right now, I
even get quoted message I reply to!).

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?


signature.asc
Description: PGP signature

Bug#910547: gutenprint: make distclean deletes doc/gutenprint{,ui2}/* which is not regenerated

[Andreas Beckmann]

Source: gutenprint
Version: 5.3.1-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

gutenprint FTBFS twice in a row. The first build succeeds, but the
subsequent debian/rules clean causes doc/gutenprint/*,
doc/gutenprintui2/* (and possibly more relevant files) to be deleted,
which are not regenerated during the second build.

>From the attached logfile:

[first build succeeded]

[from debian/rules clean after the first build]

...
Making distclean in doc
make[2]: Entering directory '/build/gutenprint-5.3.1/doc'
Making distclean in developer
make[3]: Entering directory '/build/gutenprint-5.3.1/doc/developer'
rm -rf .libs _libs
if test . = "." -a false = false ; then \
  echo "clean-local: Not removing reference-html" ; \
  echo 'clean-local: Not removing gutenprint.pdf' ; \
  echo 'clean-local: Not removing gutenprint.ps' ; \
else \
  rm -f gutenprint.pdf gutenprint.ps; rm -rf *html-stamp reference-html ; \
fi
rm -f *.lo
clean-local: Not removing reference-html
clean-local: Not removing gutenprint.pdf
clean-local: Not removing gutenprint.ps
if test . = "." ; then \
  : ; \
else \
  rm -f copying.xml dither.xml escp2.xml gutenprint.xml gpl-appendix.xml 
introduction.xml new-printer.xml problems.xml using.xml weave.xml ; \
fi
test -z "" || rm -f 
rm -rf *.tex *.log *.aux *.dvi *.gz *.out *.junk *.out *.fot
test . = "." || test -z "" || rm -f 
rm -rf db2html* DB2HTML* CATALOG.local
rm -f Makefile
make[3]: Leaving directory '/build/gutenprint-5.3.1/doc/developer'
make[3]: Entering directory '/build/gutenprint-5.3.1/doc'
rm -rf .libs _libs
rm -f *.lo
test -z "gutenprint.dox gutenprintui2.dox" || rm -f gutenprint.dox 
gutenprintui2.dox
rm -rf gutenprint
rm -f TAGS ID GTAGS GRTAGS GSYMS GPATH tags
test . = "." || test -z "" || rm -f 
test -z "gutenprint-stamp gutenprintui2-stamp" || rm -f gutenprint-stamp 
gutenprintui2-stamp
rm -rf gutenprintui2
make[3]: Leaving directory '/build/gutenprint-5.3.1/doc'
rm -f Makefile
make[2]: Leaving directory '/build/gutenprint-5.3.1/doc'
...

[building the source package after the first build+clean causes dpkg-source to 
report many deleted files]

...
dpkg-source: warning: ignoring deletion of file doc/gutenprintui2-stamp, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file doc/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file doc/gutenprint-stamp, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file doc/developer/Makefile.in, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of directory doc/gutenprintui2
dpkg-source: warning: ignoring deletion of file 
doc/gutenprintui2/gutenprintui2.tag, use --include-removal to override
dpkg-source: warning: ignoring deletion of directory doc/gutenprintui2/html
dpkg-source: warning: ignoring deletion of file 
doc/gutenprintui2/html/index.html, use --include-removal to override
dpkg-source: warning: ignoring deletion of file 
doc/gutenprintui2/html/bc_s.png, use --include-removal to override
dpkg-source: warning: ignoring deletion of file 
doc/gutenprintui2/html/folderopen.png, use --include-removal to override
dpkg-source: warning: ignoring deletion of file 
doc/gutenprintui2/html/sync_off.png, use --include-removal to override
...
dpkg-source: warning: ignoring deletion of file 
doc/gutenprintui2/html/bdwn.png, use --include-removal to override
dpkg-source: warning: ignoring deletion of file 
doc/gutenprintui2/html/splitbar.png, use --include-removal to override
dpkg-source: warning: ignoring deletion of file 
doc/gutenprintui2/html/functions_vars.html, use --include-removal to override
dpkg-source: warning: ignoring deletion of file doc/gutenprintui2/html/doc.png, 
use --include-removal to override
dpkg-source: warning: ignoring deletion of directory doc/gutenprint
dpkg-source: warning: ignoring deletion of file doc/gutenprint/gutenprint.tag, 
use --include-removal to override
dpkg-source: warning: ignoring deletion of directory doc/gutenprint/html
dpkg-source: warning: ignoring deletion of file 
doc/gutenprint/html/group__printer.html, use --include-removal to override
dpkg-source: warning: ignoring deletion of file doc/gutenprint/html/index.html, 
use --include-removal to override
dpkg-source: warning: ignoring deletion of file doc/gutenprint/html/bc_s.png, 
use --include-removal to override
dpkg-source: warning: ignoring deletion of file 
doc/gutenprint/html/structstp__shade.html, use --include-removal to override
...
dpkg-source: warning: ignoring deletion of file 
doc/gutenprint/html/globals_d.html, use --include-removal to override
dpkg-source: warning: ignoring deletion of file 
doc/gutenprint/html/util_8h.html, use --include-removal to override
dpkg-source: warning: ignoring deletion of file 
doc/gutenprint/html/string-list_8h.html, use --include-removal to override
dpkg-source: warning: ignoring deletion of file 
doc/gutenprint/html/array_8h.html

Bug#910546: firefox-esr: emoji rendered oversized when fonts-noto-color-emoji is istalled

[nfb]

Package: firefox-esr
Version: 52.9.0esr-1
Severity: minor

Dear Maintainer,

when fonts-noto-color-emoji is installed, (some?) emojis are shown
oversized in various parts of firefox, including web pages and UI.
This means they are much bigger than the font size of their
surrounding regular text, and they overlap other lines creating a very
weird and unlegible effect.

As example see the two attached screenshots showing the issue in:
1.  the firefox UI: see how icons on first/last page buttons are
rendered in the 'Print' dialog. I guees those are some sort of
backward/forward icons;
2.  web content: I managed to find a youtube video [0] affected by this
behaviour (wasn't hard honestly, just searched for 'emoji title'
:)). Here you can see the issue at its worst. I don't remember
right now if i had problems on other websites, but I usually don't
browse webpages with lots of emojis in general...

Now I don't know whether the problem is in firefox or in
fonts-noto-color-emoji (or some sort of GTK fonts precedence maybe?).
I can only say i just use plain default themes and fonts, so idk.

Thanks, let me know if you need more details.
Best regards.


[0] https://www.youtube.com/watch?v=NPjDrN2ovME




-- Package-specific info:

-- Extensions information
Name: Application Update Service Helper
Location: ${PROFILE_EXTENSIONS}/aushel...@mozilla.org.xpi
Status: enabled

Name: Default theme
Location: 
/usr/lib/firefox-esr/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
Package: firefox-esr
Status: enabled

Name: Linen Light theme
Status: user-disabled

Name: Multi-process staged rollout
Location: ${PROFILE_EXTENSIONS}/e10sroll...@mozilla.org.xpi
Status: enabled

Name: Pocket
Location: ${PROFILE_EXTENSIONS}/fire...@getpocket.com.xpi
Status: enabled

Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: enabled

Name: Web Compat
Location: ${PROFILE_EXTENSIONS}/webcom...@mozilla.org.xpi
Status: enabled

-- Plugins information

-- Addons package information
ii  firefox-esr52.9.0esr-1  amd64Mozilla Firefox web browser - Ext

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

Kernel: Linux 4.18.0-1-amd64 (SMP w/8 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)
LSM: AppArmor: enabled

Versions of packages firefox-esr depends on:
ii  debianutils   4.8.6
ii  fontconfig2.13.1-1
ii  libasound21.1.6-1
ii  libatk1.0-0   2.30.0-1
ii  libc6 2.27-6
ii  libcairo-gobject2 1.15.12-1
ii  libcairo2 1.15.12-1
ii  libdbus-1-3   1.12.10-1
ii  libdbus-glib-1-2  0.110-3
ii  libevent-2.1-62.1.8-stable-4
ii  libffi6   3.2.1-8
ii  libfontconfig12.13.1-1
ii  libfreetype6  2.8.1-2
ii  libgcc1   1:8.2.0-7
ii  libgdk-pixbuf2.0-02.38.0+dfsg-6
ii  libglib2.0-0  2.58.1-2
ii  libgtk-3-03.24.1-2
ii  libgtk2.0-0   2.24.32-3
ii  libhunspell-1.6-0 1.6.2-1+b1
ii  libjsoncpp1   1.7.4-3
ii  libnspr4  2:4.20-1
ii  libnss3   2:3.39-1
ii  libpango-1.0-01.42.4-3
ii  libsqlite3-0  3.25.2-1
ii  libstartup-notification0  0.12-5
ii  libstdc++68.2.0-7
ii  libvpx5   1.7.0-3
ii  libx11-6  2:1.6.6-1
ii  libx11-xcb1   2:1.6.6-1
ii  libxcb-shm0   1.13-3
ii  libxcb1   1.13-3
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxrender1   1:0.9.10-1
ii  libxt61:1.1.5-1
ii  procps2:3.3.15-2
ii  zlib1g1:1.2.11.dfsg-1

firefox-esr recommends no packages.

Versions of packages firefox-esr suggests:
pn  fonts-lmodern  
pn  fonts-stix | otf-stix  
ii  libcanberra0   0.30-6
ii  libgssapi-krb5-2   1.16-2
pn  mozplugger 

-- no debconf information

Bug#910537: reportbug: using GUI editor in reportbug seems to need canberra-gtk-module but it isn't in suggests or anywhere

[shirish शिरीष]

On 08/10/2018, Adam D. Barratt  wrote:
> Control: tags -1 + moreinfo
>
> On Mon, 2018-10-08 at 01:34 +0530, shirish शिरीष wrote:
>> Whenever I use leafpad to use reportbug I get the following -
>>
>> Please select tags: (one at a time) [none]
>> Gathering additional data, this may take a while...
>> Spawning leafpad...
>> Gtk-Message: 01:27:29.888: Failed to load module "canberra-gtk-
>> module"
>>
>> I guess this needs/needed libcanberra-gtk-module but for some reason
>> isn't in suggests ? Maybe using leafpad as an editor is an oddity ? I
>> dunno whether the severity should be in normal or a wishlist.
>
> It's really unlikely that this has anything to do with reportbug at
> all. I'd imagine you get the same message if you run leafpad from a
> terminal - or basically any Gtk-using application, in fact.
>
> A few minutes searching suggests that this is due to partial removal of
> the canberra libraries. Please "dpkg -l | grep canberra" and provide
> the result.
>
> Regards,
>
> Adam
>

Dear Adam,

You are right. It seems the issue lies with leafpad and not reportbug.

 leafpad
Gtk-Message: 03:37:32.665: Failed to load module "canberra-gtk-module"

FWIW, the following is the output of what you asked -

 dpkg -l | grep canberra
ii  libcanberra-gtk3-0:amd64  0.30-6
amd64GTK+ 3.0 helper for playing widget event sounds
with libcanberra
ii  libcanberra-gtk3-module:amd64 0.30-6
amd64translates GTK3 widgets signals to event sounds
ii  libcanberra0:amd640.30-6
amd64simple abstract interface for playing event
sounds

Hope the issue can be moved to leafpad or whereever it is more appropriate.

Thank you for followint-up so quickly.

-- 
  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
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#907725: Fwd: Appropriate Section for PCF Fonts

[Paul Hardy]

Chris,

Thank you for dealing with bug #907725 ("xfonts packages are not using
the x11 section in practice").  I was told that it was up to the FTP
Masters, so I wrote the below email to them in July.  I have not yet
received a response, but looking at the NEW queue it is obvious how
swamped they are so I wasn't expecting a rapid response.

Sincerely,


Paul Hardy

-- Forwarded message -
From: Paul Hardy 
Date: Mon, Jul 30, 2018 at 6:40 AM
Subject: Appropriate Section for PCF Fonts
To: 


Dear FTP Masters,

I am preparing a new upload of my Unifont package, which includes a
PCF font.  I get a lintian warning that the PCF font is not in the "X
Window System" section.  The sid section page
(https://packages.debian.org/sid/) mentions fonts as one thing
appropriate for that section.

There is also a "fonts" section of course, and that is where all of
the Unifont fonts are now (and have been for over 10 years).

There are a lot of PCF fonts in the fonts section, and it looks like
almost none in the "X Window" section.  Any font today can be used by
more than the X Window System, so my inclination is to keep PCF fonts
in the "fonts" section.

To clarify things with font maintainers, can you either have a mass
bug filing against all PCF fonts that are in the fonts section, or
remove "fonts" from the list of package types suitable for the "X
Window" section.  And if you remove fonts from the "X Window" section
list, the current lintian warning (when a PCF font is in the "fonts"
section) should be removed.

If you want to file a mass bug report, this would probably be a good
time, as it would give font package maintainers time to upload new
versions before the buster freeze.

Thank you,


Paul Hardy

Bug#910543: bfs 1.2.4-1 fstype test fails on Hurd

[Samuel Thibault]

Hello,

Chris Lamb, le dim. 07 oct. 2018 22:40:08 +0100, a ecrit:
>  
> https://github.com/tavianator/bfs/commit/85caf29cfd2f40ef10ed76d425bb89a5f8f45a1a
> 
> .. but that was in 1.2.2-2.
> 
> debian-hurd@, any input here? Any reason why /proc/mounts might not
> exist, or...?

I have seen /proc not getting mounted for yet-unknow reasons, thus
making some builds fail. I have given back bfs.

Samuel

Bug#910545: node-fast-deep-equal: updated version

[Jeffrey Cliff]

Package: node-fast-deep-equal
Version: 1.0.0-1
Severity: normal
Tags: patch

Dear Maintainer,

Before upstream was taken over by NSA/Microsoft, there was a newer version
of node-fast-deep-equal available upstream.  The following patch patches
node-fast-deep-equal to that newer version (2.0.1).  This newer
functionality is depended on by other projects(such as similarly
modified/updated versions of node-ajv, which in turn is a possible
prerequisite of solving #743404).   It seems to pass both lintian and its
own tests.

(It is unfortunately not a quilt patch, since it's not a matter of patching
from an upstream version, since imho you're effectively upstream, now).

Changes include bug fixes, performance updates, updated dependencies, and
updated tests.  See commit log for details:
https://notabug.org/themusicgod1/fast-deep-equal/commits/master )

(I've taken liberty to bump the compat while I was at this.)

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

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

Versions of packages node-fast-deep-equal depends on:
ii  nodejs  8.11.2~dfsg-1

node-fast-deep-equal recommends no packages.

node-fast-deep-equal suggests no packages.

-- no debconf information
Only in node-fast-deep-equal-1.0.0/benchmark: .eslintrc.yml
diff -r node-fast-deep-equal-1.0.0/benchmark/index.js node-fast-deep-equal-2.0.1/benchmark/index.js
20c20,21
<   }
---
>   },
>   'ramda.equals': require('ramda').equals
diff -r node-fast-deep-equal-1.0.0/debian/changelog node-fast-deep-equal-2.0.1/debian/changelog
0a1,6
> node-fast-deep-equal (2.0.1-1) UNRELEASED; urgency=medium
> 
>   * New version
> 
>  -- Jeff Cliff   Sun, 07 Oct 2018 17:18:00 +0500
> 
diff -r node-fast-deep-equal-1.0.0/debian/compat node-fast-deep-equal-2.0.1/debian/compat
1c1
< 9
---
> 10
diff -r node-fast-deep-equal-1.0.0/debian/control node-fast-deep-equal-2.0.1/debian/control
9c9
<  , nodejs
---
>  , nodejs (>= 0.10)
Only in node-fast-deep-equal-2.0.1/debian: .debhelper
Only in node-fast-deep-equal-2.0.1/debian: debhelper-build-stamp
Only in node-fast-deep-equal-2.0.1/debian: files
Only in node-fast-deep-equal-2.0.1/debian: node-fast-deep-equal
Only in node-fast-deep-equal-2.0.1/debian: node-fast-deep-equal.substvars
Only in node-fast-deep-equal-1.0.0/: .eslintrc.yml
Only in node-fast-deep-equal-2.0.1/: .git
diff -r node-fast-deep-equal-1.0.0/.gitignore node-fast-deep-equal-2.0.1/.gitignore
56a57,60
> # Lock files
> package-lock.json
> yarn.lock
> 
Only in node-fast-deep-equal-2.0.1/: index.d.ts
diff -r node-fast-deep-equal-1.0.0/index.js node-fast-deep-equal-2.0.1/index.js
2a3,6
> var isArray = Array.isArray;
> var keyList = Object.keys;
> var hasProp = Object.prototype.hasOwnProperty;
> 
6,15c10,23
<   var arrA = Array.isArray(a)
< , arrB = Array.isArray(b)
< , i;
< 
<   if (arrA && arrB) {
< if (a.length != b.length) return false;
< for (i = 0; i < a.length; i++)
<   if (!equal(a[i], b[i])) return false;
< return true;
<   }
---
>   if (a && b && typeof a == 'object' && typeof b == 'object') {
> var arrA = isArray(a)
>   , arrB = isArray(b)
>   , i
>   , length
>   , key;
> 
> if (arrA && arrB) {
>   length = a.length;
>   if (length != b.length) return false;
>   for (i = length; i-- !== 0;)
> if (!equal(a[i], b[i])) return false;
>   return true;
> }
17,21c25
<   if (arrA != arrB) return false;
< 
<   if (a && b && typeof a === 'object' && typeof b === 'object') {
< var keys = Object.keys(a);
< if (keys.length !== Object.keys(b).length) return false;
---
> if (arrA != arrB) return false;
25d28
< if (dateA && dateB) return a.getTime() == b.getTime();
26a30
> if (dateA && dateB) return a.getTime() == b.getTime();
30d33
< if (regexpA && regexpB) return a.toString() == b.toString();
31a35,41
> if (regexpA && regexpB) return a.toString() == b.toString();
> 
> var keys = keyList(a);
> length = keys.length;
> 
> if (length !== keyList(b).length)
>   return false;
33,34c43,44
< for (i = 0; i < keys.length; i++)
<   if (!Object.prototype.hasOwnProperty.call(b, keys[i])) return false;
---
> for (i = length; i-- !== 0;)
>   if (!hasProp.call(b, keys[i])) return false;
36,37c46,49
< for (i = 0; i < keys.length; i++)
<   if(!equal(a[keys[i]], b[keys[i]])) return false;
---
> for (i = length; i-- !== 0;) {
>   key = keys[i];
>   if (!equal(a[key], b[key])) return false;
> }
42c54
<   return false;
---
>   return a!==a && b!==b;
diff -r node-fast-deep-equal-1.0.0/package.json node-fast-deep-equal-2.0.1/package.json
3c3
<   "version": "1.0.0",
---
>   "version": "2.0.1",
10c10,11
< "test": "npm run eslin

Bug#908796: udev (with sysvinit) fails to find devices at boot

[Trek]

On Sun, 7 Oct 2018 01:57:31 +0200
Michael Biebl  wrote:

> > - We tweak the LSB headers to make sure the udev init script is
> > called before sendsigs on shutdown. This is important!
> 
> I have to add, that this change has the potential to significantly
> change the shutdown order or cause a conflicting ordering, in case
> there are other init scripts which declare an explicit shutdown
> dependency.

yes, this would create a circular dependency

before the 791944 patch, the shutdown sequence was:
K03sendsigs (before umountnfs)
K05umountnfs(before umountfs)
K07umountfs (before umountroot)
K08cryptdisks   (after umountfs, before umountroot udev)
K10umountroot

if udev is stopped before sendsigs:
- cryptdisks should be stopped before udev
- umountfs should be stopped before cryptdisks
- umountnfs should be stopped before umountfs
- but sendsigs cannot be stopped after umountnfs

it can be easily resolved removing the udev entry in the Should-Stop
header of cryptdisks (and cryptdisks-early)


> Looking at https://codesearch.debian.net/ and searching for packages
> which declare a Should-Stop or Required-Stop on udev and checking if
> any late shutdown services are involved.

wow! I didn't know this site

with this simple search "Stop(|-After):.*udev", it returned these
packages that could be affected: multipath-tools, pcsc-lite,
network-manager, mouseemu, pulseaudio, cryptsetup, nut

it seems to me none of these packages would break (except cryptsetup)

this change should be mentioned in the NEWS.Debian file, as it could
break any script that depends on udev on shutdown and that is not
distributed by debian (open/closed source packages and system
administrator scripts)

the patches attached are tested on a system with swaps and filesystems
encrypted in plain mode (no luks, no cryptroot)

ciao!>From b8f8bcfa1c447bc0839a84c4f64a551278a33dec Mon Sep 17 00:00:00 2001
From: Trek 
Date: Sun, 7 Oct 2018 17:59:25 +0200
Subject: [PATCH] Stop udev before sendsigs to fix a regression of #791944

The start-stop-daemon command with the --background argument returns
immediately, too soon to trigger events on some systems. The #791944
patch is partly reverted and a dependency to sendsigs is added in the
SysV init script at shutdown.

Closes: #908796
---
 debian/udev.init | 19 +--
 1 file changed, 5 insertions(+), 14 deletions(-)

diff --git a/debian/udev.init b/debian/udev.init
index 9c394bb..794373d 100644
--- a/debian/udev.init
+++ b/debian/udev.init
@@ -3,6 +3,7 @@
 # Provides:  udev
 # Required-Start:mountkernfs
 # Required-Stop: umountroot
+# Should-Stop:   sendsigs
 # Default-Start: S
 # Default-Stop:  0 6
 # Short-Description: Start systemd-udevd, populate /dev and load drivers.
@@ -12,9 +13,7 @@ PATH="/sbin:/bin"
 NAME="systemd-udevd"
 DAEMON="/lib/systemd/systemd-udevd"
 DESC="hotplug events dispatcher"
-PIDFILE="/run/udev.pid"
 CTRLFILE="/run/udev/control"
-OMITDIR="/run/sendsigs.omit.d"
 
 # we need to unmount /dev/pts/ and remount it later over the devtmpfs
 unmount_devpts() {
@@ -165,11 +164,7 @@ case "$1" in
 [ -x /sbin/restorecon ] && /sbin/restorecon -R /dev
 
 log_daemon_msg "Starting $DESC" "$NAME"
-if start-stop-daemon --start --name $NAME --user root --quiet \
---pidfile $PIDFILE --exec $DAEMON --background --make-pidfile; then
-# prevents udevd to be killed by sendsigs (see #791944)
-mkdir -p $OMITDIR
-ln -sf $PIDFILE $OMITDIR/$NAME
+if $DAEMON --daemon; then
 log_end_msg $?
 else
 log_warning_msg $?
@@ -198,7 +193,7 @@ case "$1" in
 stop)
 log_daemon_msg "Stopping $DESC" "$NAME"
 if start-stop-daemon --stop --name $NAME --user root --quiet \
---pidfile $PIDFILE --remove-pidfile --oknodo --retry 5; then
+--oknodo --retry 5; then
 # prevents cryptsetup/dmsetup hangs (see #791944)
 rm -f $CTRLFILE
 log_end_msg $?
@@ -210,7 +205,7 @@ case "$1" in
 restart)
 log_daemon_msg "Stopping $DESC" "$NAME"
 if start-stop-daemon --stop --name $NAME --user root --quiet \
---pidfile $PIDFILE --remove-pidfile --oknodo --retry 5; then
+--oknodo --retry 5; then
 # prevents cryptsetup/dmsetup hangs (see #791944)
 rm -f $CTRLFILE
 log_end_msg $?
@@ -219,11 +214,7 @@ case "$1" in
 fi
 
 log_daemon_msg "Starting $DESC" "$NAME"
-if start-stop-daemon --start --name $NAME --user root --quiet \
---pidfile $PIDFILE --exec $DAEMON --background --make-pidfile; then
-# prevents udevd to be killed by sendsigs (see #791944)
-mkdir -p $OMITDIR
-ln -sf $PIDFILE $OMITDIR/$NAME
+if $DAEMON --daemon; then
 log_end_msg $?
 else
 log_end_msg $?
-- 
2.1.4

>From 46ef94eb04ea03b7ef53b156439eef22e3c0a054 Mon Sep 17 00:00:00 2001
From: Trek 
Date: Sun, 7 Oct 2018 17:57:54 +0200
Subject: [PATCH] Remove the shutdown dependency on udev to fix a regression of

Bug#910544: tzdata: Brazil 2018-2019 DST changed

[Antonio Terceiro]

Package: tzdata
Version: 2018e-1
Severity: important
Tags: upstream

Hi,

Recently it was decided that this year DST will start in Brazil on
November 18th instead of November 4th. The corresponding thread on the
upstream mailing list starts at:
https://mm.icann.org/pipermail/tz/2018-October/026917.html

The maintainer said he will wait for the official decree for making a
release, but the required changes were already made in the git
repository.

Given the very short window to update every system in the country, it
would be nice if we could have a release as soon as possible.

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

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

Versions of packages tzdata depends on:
ii  debconf [debconf-2.0]  1.5.69

tzdata recommends no packages.

tzdata suggests no packages.

-- debconf information excluded


signature.asc
Description: PGP signature

Bug#910542: better support for OCaml object files via ocamlobjinfo

[Chris Lamb]

retitle 910542 better support for OCaml object files via ocamlobjinfo
severity 910542 wishlist
thanks

Hi Thomas,

> It would be nice to show more structured information instead; a subset 
> of this information could already be dumped with `ocamlobjinfo` command 

Ooh, thanks for the pointer; retitling to match.


Best wishes,

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

Bug#873493: reportbug: confused with python-astroid

[Nis Martensen]

> Reportbug uses the ftp-master madison cgi to identify available
> package versions.
This was not correct. Reportbug uses the qa madison url, not the
ftp-master one. It should switch to the latter, as a bug in the qa cgi
contributes to the problem.

To fully solve the problem, reportbug will need to query differently
depending on whether we are looking for the versions of a binary package
or of a source package.

Bug#910543: bfs 1.2.4-1 fstype test fails on Hurd

[Chris Lamb]

tags 910543 + moreinfo
thanks

[ adding debian-h...@lists.debian.org to CC ]

Dear Tavian et al.,

> > test_fstype
> > error: Couldn't parse the mount table: No such file or directory
> > error: Couldn't parse the mount table: No such file or directory
> 
> which is presumably an error opening /proc/mounts (bfs tries /etc/mtab 
> first and falls back to /proc/mounts).
> 
> It worked fine for 1.2.3:
> https://buildd.debian.org/status/fetch.php?pkg=bfs&arch=hurd-i386&ver=1.2.3-1&stamp=1532143385&raw=0

That's very odd. I mean, we re-enabled the fstype tests here:

 
https://github.com/tavianator/bfs/commit/85caf29cfd2f40ef10ed76d425bb89a5f8f45a1a

.. but that was in 1.2.2-2.

debian-hurd@, any input here? Any reason why /proc/mounts might not
exist, or...?  Maybe that's not the reason and we are being confused by
the the strerror?


Regards,

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

Bug#910543: bfs 1.2.4-1 fstype test fails on Hurd

[Adam D. Barratt]

Control: severity -1 important

On Sun, 2018-10-07 at 21:28 +, Tavian Barnes wrote:
> Package: bfs
> Version: 1.2.4-1
> Severity: serious
> Justification: fails to build from source (but built successfully in
> the past)
> 
> Dear Maintainer,
> 
> bfs recently failed to build on Hurd:
> https://buildd.debian.org/status/fetch.php?pkg=bfs&arch=hurd-i386&ver
> =1.2.4-1&stamp=1538407170&raw=0

Build failures on non-release architectures aren't RC (rather by
definition); downgrading.

Regards,

Adam

Bug#910541: diffoscope: filing bugs on diffoscope is cumbersome for non-Debian contributors

[Chris Lamb]

severity 910541 normal
thanks

Dear Holger,
 
> I just gave a small presentation about diffoscope at the mirage.io
> hackretreat (which was well received) which resulted in people
> wanting to file bugs against diffoscope, which turned out to be "complicated"

Completely, 100%, agree.

(Adjusting severity only because important severity bugs are treated
somewhat different in some interfaces, but agree this is more
severe than "just another" wishlist entry.)

> - the project on salsa has issues disabled (but would require a login on
>   salsa anyway), still filing bugs in a webbrowser is something many
>   people want to do today, so I think maybe we should enable issues?

No strong objection to the principle except that we would then have
some duplication between the two trackers.

I'm thinking specifically of those times when I'd like to pick up on a
previous issue, but then would need to "mentally merge" two lists of
bugs, filtering any potential duplicates, etc.

Do we have any ideas to limit this? One rather brutal way of doing this
would be to insist that diffoscope-on-the-BTS only had Debian-specific
issues and salsa has everything else, forcing people to refile? Or that
salsa is a superset of the BTS & just try and remember to file
everything that arrives in the BTS to.. etc.

Anyone have experience elsewhere that can help?

> - the link "Bugs and feature requests" on https://diffoscope.org just
>   points to https://bugs.debian.org/src:diffoscope

(Let's fix that when this issue is fixed; it would just need updating
and/or expanding)

> - there is still https://github.com/ReproducibleBuilds but thats empty, 
>   so noone could file issues there.

Well, this one is easily "fixed":

  https://i.imgur.com/vXbuKYU.png


Best wishes,

-- 
O
  // \\ Chris Lamb
 O Oreproducible-builds.org
  \\ //
O

Bug#910540: backtrace when using diffoscope on macOS (brew)

[Chris Lamb]

tags 910540 + pending
thanks

Thanks for the report Thomas. Fixed in Git, pending upload:

  
https://salsa.debian.org/reproducible-builds/diffoscope/commit/56f8215cc1ebba04b6ca1e6430dc1420a8974750

  diffoscope/comparators/macho.py | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)


Regards,

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

Bug#910543: bfs 1.2.4-1 fstype test fails on Hurd

[Tavian Barnes]

Package: bfs
Version: 1.2.4-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

bfs recently failed to build on Hurd:
https://buildd.debian.org/status/fetch.php?pkg=bfs&arch=hurd-i386&ver=1.2.4-1&stamp=1538407170&raw=0

due to

> test_fstype
> error: Couldn't parse the mount table: No such file or directory
> error: Couldn't parse the mount table: No such file or directory

which is presumably an error opening /proc/mounts (bfs tries /etc/mtab first 
and falls back to /proc/mounts).

It worked fine for 1.2.3:
https://buildd.debian.org/status/fetch.php?pkg=bfs&arch=hurd-i386&ver=1.2.3-1&stamp=1532143385&raw=0

and I can't see any relevant changes between the two versions.


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

Kernel: Linux 4.18.11-arch1-1-ARCH (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Bug#899979: keyboard-configuration: the caron dead-key of the czech keyboard on the console does not work as expected

[Samuel Thibault]

Samuel Thibault, le mer. 06 juin 2018 15:19:07 +0200, a ecrit:
> Samuel Thibault, le ven. 01 juin 2018 16:28:23 +0200, a ecrit:
> > Anton Zinoviev, le ven. 01 juin 2018 17:22:06 +0300, a ecrit:
> > > On Fri, Jun 01, 2018 at 04:10:36PM +0200, Samuel Thibault wrote:
> > > > U+015A would be what you'd expect for a latin1 language (^ + S), and I
> > > > guess due to rule ordering, the existing rule doesn't get overrident by
> > > > the rule you introduced, so we need to explicitly remove the existing
> > > > rule.
> > > 
> > > And what should the future console-setup do with compose+^+S when the 
> > > encoding is UTF-8?  How is this problem solved in X?
> > 
> > Well, in X XK_dead_caron is separate from XK_dead_circumflex.  The issue
> > with Linux is that it only has a few dead keys. Maybe we should just go
> > and define all X11 deadkeys in Linux (there are like 55 of them, that
> > will fit), to be done with the issue.
> 
> FTR in the bug report, I have submitted a patch to the LKML on Sun, 3
> Jun ("kbd: complete dead keys definitions").

FTR, it is currently in v4.19-rc7, so it will extremely likely be in
4.19.

Samuel

Bug#910542: better support for OCaml object files

[Thomas Gazagnaire]

Package: diffoscope

The OCaml compiler generates a bunch of binary files (cmi, cmi, cmt, cmti, cmx, 
cmxa). Currently diffoscope seems to only prints  binary diffs:

https://tests.reproducible-builds.org/archlinux/extra/ocaml-result/ocaml-result-1.3-1-x86_64.pkg.tar.xz.html

It would be nice to show more structured information instead; a subset of this 
information could already be dumped with `ocamlobjinfo` command which might be 
enough in most cases.

Thomas

Bug#910541: diffoscope: filing bugs on diffoscope is cumbersome for non-Debian contributors

[Holger Levsen]

Package: diffoscope
Severity: important

Hi,

I just gave a small presentation about diffoscope at the mirage.io
hackretreat (which was well received) which resulted in people
wanting to file bugs against diffoscope, which turned out to be "complicated":

- the project on salsa has issues disabled (but would require a login on
  salsa anyway), still filing bugs in a webbrowser is something many
  people want to do today, so I think maybe we should enable issues?
- the link "Bugs and feature requests" on https://diffoscope.org just
  points to https://bugs.debian.org/src:diffoscope - this is helpful for
  Debian developers but hardly for anyone else.
- there is still https://github.com/ReproducibleBuilds but thats empty, 
  so noone could file issues there.

I've got no good idea how to fix this best, but I wanted to at least
document this so we can come up with something better. It's unfortunate
to say 'please file bugs' and then...


-- 
cheers,
Holger

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


signature.asc
Description: PGP signature

Bug#910540: backtrace when using diffoscope on macOS (brew)

[Thomas Gazagnaire]

Package: diffoscope

I am trying to use diffoscope on brew but the binary that I got after "brew 
install diffoscope" doesn't seem to be working correctly.

```
$ diffoscope --version
diffoscope 102
$ diffoscope foo _build/main.native
Traceback (most recent call last):
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/diff.py",
 line 327, in diff
return run_diff(fifo1_path, fifo2_path, fifo1.end_nl_q, fifo2.end_nl_q)
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/diff.py",
 line 220, in __exit__
self.join()
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/diff.py",
 line 253, in join
raise self._exception
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/diff.py",
 line 244, in run
end_nl = self.feeder(fifo)
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/feeders.py",
 line 88, in feeder
end_nl = feeder(out_file)
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/feeders.py",
 line 47, in feeder
out = buf if filter is None else filter(buf)
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/comparators/macho.py",
 line 47, in filter
if line.decode('utf-8', 'ignore').index(prefix) == 0:
ValueError: substring not found

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/main.py",
 line 470, in main
sys.exit(run_diffoscope(parsed_args))
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/main.py",
 line 442, in run_diffoscope
difference = compare_root_paths(path1, path2)
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/comparators/utils/compare.py",
 line 68, in compare_root_paths
difference = compare_files(file1, file2)
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/comparators/utils/compare.py",
 line 118, in compare_files
return file1.compare(file2, source)
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/comparators/utils/file.py",
 line 366, in compare
difference = self._compare_using_details(other, source)
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/comparators/utils/file.py",
 line 304, in _compare_using_details
details.extend(self.compare_details(other, source))
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/comparators/macho.py",
 line 102, in compare_details
comment="Mach-O headers for architecture %s" % common_arch))
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/difference.py",
 line 233, in from_command
return Difference.from_command_exc(klass, path1, path2, *args, **kwargs)[0]
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/difference.py",
 line 270, in from_command_exc
**kwargs
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/difference.py",
 line 186, in from_feeder
unified_diff = diff(feeder1, feeder2)
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/diff.py",
 line 327, in diff
return run_diff(fifo1_path, fifo2_path, fifo1.end_nl_q, fifo2.end_nl_q)
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/diff.py",
 line 220, in __exit__
self.join()
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/diff.py",
 line 253, in join
raise self._exception
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/diff.py",
 line 244, in run
end_nl = self.feeder(fifo)
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/feeders.py",
 line 88, in feeder
end_nl = feeder(out_file)
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/feeders.py",
 line 47, in feeder
out = buf if filter is None else filter(buf)
  File 
"/usr/local/Cellar/diffoscope/102/libexec/lib/python3.7/site-packages/diffoscope/comparators/macho.py",
 line 47, in filter
if line.decode('utf-8', 'ignore').index(prefix) == 0:
ValueError: substring not found
```

Bug#908153: gnome-shell: [regression] frequent crashes on g-s 3.30

[Andreas Kloeckner]

Andreas Kloeckner  writes:

> Just tried again with more up-to-date packages, but unfortunately no
> dice--the bug persists. I did notice that the bug does not seem to
> affect Wayland sessions -- though those aren't viable for me yet because
> of another bug [1].

This is the same as

https://gitlab.gnome.org/GNOME/mutter/issues/294 (has patch)

and

https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1788483

Andreas



signature.asc
Description: PGP signature

Bug#910538: RFS: vitetris/0.57.2-1 [ITP]

[Pierre-Elliott Bécue]

Le dimanche 07 octobre 2018 à 22:10:42+0200, Baptiste BEAUPLAT a écrit :
> Package: sponsorship-requests
> Severity: normal
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Dear mentors,
> 
> I am looking for a sponsor for my package "vitetris"
> 
>  Package name: vitetris
>  Version : 0.57.2-1
>  Upstream Author : Victor Geraldsson
>  URL : http://www.victornils.net/tetris/
>  License : BSD-2-Clause
>  Section : games
> 
> It builds those binary packages:
> 
>   vitetris   - Virtual terminal *tris clone
> 
> To access further information about this package, please visit the following 
> URL:
> 
> https://mentors.debian.net/package/vitetris
> 
> 
> Alternatively, one can download the package with dget using this command:
> 
>   dget -x 
> https://mentors.debian.net/debian/pool/main/v/vitetris/vitetris_0.57.2-1.dsc
> 
> More information about vitetris can be obtained from 
> http://www.victornils.net/tetris/.
> Changes since the last upload:
> 
>   * Initial release (Closes: #909968)
> 
> Best Regards,

Dear Baptiste,

I get a weird error when I try to download your GPG key to check the package
you made.

`---> gpg --search-keys 2DE24895313C5DA7F089E14E17494B10795DD733
gpg: data source: https://[2a02:c205:3001:3626::1]:443
(1) lyknode 
Baptiste BEAUPLAT 
  256 bit EDDSA key 1EDBAA3C6926AF92, créé : 2017-08-05, expire : 
2019-08-05
Keys 1-1 of 1 for "2DE24895313C5DA7F089E14E17494B10795DD733".  Entrez le ou les 
nombres, (S)uivant, ou (Q)uitter > 1
gpg: key 1EDBAA3C6926AF92: no user ID for key signature packet of class 13
gpg:   Quantité totale traitée : 1

Is your GPG key actually properly uploaded?

You should mention your salsa repo when you ask for sponsorship. I found this:
https://salsa.debian.org/lyknode-guest/vitetris

Your package seems in a good shape. Some remarks and suggestions:

 - d/control: The description should start with something more general than the
   way the features of the game should look.
 - The install part of the makefile seem to install
   usr/share/doc/vitetris/licence.txt, which should not happen. You can either
   alter debian/rules to remove this file or ignore this suggestion.

Cheers!

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#573747: We noticed

[Victoria Cleland]

I am contacting you because my office noticed you have an unclaimed Inheritance
contact me immediately for further details.

Bug#910539: kmail: Kmail regulary crash

[Lombardo Davide]

Package: kmail
Version: 4:17.12.3-1
Severity: important

Kmail crash few second after the start with this output:
org.kde.pim.messagelist: Saved theme loading failed
org.kde.pim.messagelist: Saved theme loading failed
org.kde.pim.messagelist: Saved theme loading failed
No text-to-speech plug-ins were found.
[11801:11834:1007/223950.883856:ERROR:nss_util.cc(727)] After loading Root
Certs, loaded==false: NSS error code: -8018
qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 3223, resource
id: 88080449, major code: 130 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 3226, resource
id: 88080449, major code: 130 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 3229, resource
id: 88080449, major code: 130 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 3305, resource
id: 88080449, major code: 130 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 3326, resource
id: 88080449, major code: 130 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 3330, resource
id: 88080449, major code: 130 (Unknown), minor code: 3
qt.qpa.xcb: QXcbConnection: XCB error: 8 (BadMatch), sequence: 3344, resource
id: 88080449, major code: 130 (Unknown), minor code: 3
nouveau: kernel rejected pushbuf: No such file or directory
nouveau: ch13: krec 0 pushes 0 bufs 1 relocs 0
nouveau: ch13: buf  0002 0004 0004 
Received signal 11 SEGV_ACCERR 7fc36806a0a0
#0 0x7fc40178a76e 
#1 0x7fc40178a880 
#2 0x7fc40178aeb7 
#3 0x7fc40e665fc0 
#4 0x7fc36806a0a0 
  r8:   r9:  r10: 7fc385ff9e60 r11:
7fc3680254f0
 r12: 7fc3680e26c0 r13: 7fc368021320 r14:  r15:
7fc385ff9fc0
  di: 84f7  si: 7fc385ff9fc0  bp: 0002  bx:
7fc3680f98f0
  dx:   ax: 7fc3680e26c0  cx:   sp:
7fc385ff9f68
  ip: 7fc36806a0a0 efl: 00010283 cgf: 002b0033 erf:
0015
 trp: 000e msk:  cr2: 7fc36806a0a0
[end of stack trace]
Calling _exit(1). Core file will not be generated.

I cannot use the application on my machine.





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

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

Versions of packages kmail depends on:
ii  akonadi-server   4:17.12.3-3
ii  kdepim-runtime   4:17.12.3-2
ii  kio  5.49.0-1
ii  libc62.27-6
ii  libgcc1  1:8.2.0-7
ii  libgpgmepp6  1.11.1-1
ii  libkf5akonadiagentbase5  4:17.12.3-3
ii  libkf5akonadicontact54:17.12.3-2
ii  libkf5akonadicore5abi1   4:17.12.3-3
ii  libkf5akonadimime5   4:17.12.3-1
ii  libkf5akonadisearch-bin  4:17.12.3-1
ii  libkf5akonadisearch-plugins  4:17.12.3-1
ii  libkf5akonadisearchdebug54:17.12.3-1
ii  libkf5akonadisearchpim5  4:17.12.3-1
ii  libkf5akonadiwidgets5abi14:17.12.3-3
ii  libkf5bookmarks5 5.49.0-1
ii  libkf5calendarcore5abi1  4:17.12.3-1
ii  libkf5calendarutils5 4:17.12.3-1
ii  libkf5codecs55.49.0-1
ii  libkf5completion55.49.0-1
ii  libkf5configcore55.49.0-1
ii  libkf5configgui5 5.49.0-1
ii  libkf5configwidgets5 5.49.0-1
ii  libkf5contacts5  4:18.08.1-1
ii  libkf5coreaddons55.49.0-1
ii  libkf5crash5 5.49.0-1
ii  libkf5dbusaddons55.49.0-1
ii  libkf5followupreminder5  4:17.12.3-1
ii  libkf5grantleetheme-plugins  17.12.3-1
ii  libkf5gravatar5abi1  4:17.12.3-1
ii  libkf5guiaddons5 5.49.0-1
ii  libkf5i18n5  5.49.0-1
ii  libkf5iconthemes55.49.0-1
ii  libkf5identitymanagement517.12.3-1
ii  libkf5itemmodels55.49.0-1
ii  libkf5itemviews5 5.49.0-1
ii  libkf5jobwidgets55.49.0-1
ii  libkf5kcmutils5  5.49.0-1
ii  libkf5kiocore5   5.49.0-1
ii  libkf5kiofilewidgets55.49.0-1
ii  libkf5kiowidgets55.49.0-1
ii  libkf5kontactinterface5  17.12.3-1
ii  libkf5ksieveui5  4:17.12.3-1
ii  libkf5libkdepim-plugins  4:17.12.3-1
ii  libkf5libkdepim5 4:17.12.3-1
ii  libkf5libkdepimakonadi5  4:17.12.3-1
ii  libkf5libkleo5   4:17.12.3-2
ii  libkf5mailcommon5abi14:17.12.3-1
ii  libkf5mailtransport5 17.12.3-1
ii  libkf5mailtransportakonadi5  17.12.3-1
ii  libkf5messagecomposer5   4:17.12.3-3
ii  libkf5messagecore5   4:17

Bug#910537: reportbug: using GUI editor in reportbug seems to need canberra-gtk-module but it isn't in suggests or anywhere

[Adam D. Barratt]

Control: tags -1 + moreinfo

On Mon, 2018-10-08 at 01:34 +0530, shirish शिरीष wrote:
> Whenever I use leafpad to use reportbug I get the following -
> 
> Please select tags: (one at a time) [none]
> Gathering additional data, this may take a while...
> Spawning leafpad...
> Gtk-Message: 01:27:29.888: Failed to load module "canberra-gtk-
> module"
> 
> I guess this needs/needed libcanberra-gtk-module but for some reason
> isn't in suggests ? Maybe using leafpad as an editor is an oddity ? I
> dunno whether the severity should be in normal or a wishlist.

It's really unlikely that this has anything to do with reportbug at
all. I'd imagine you get the same message if you run leafpad from a
terminal - or basically any Gtk-using application, in fact.

A few minutes searching suggests that this is due to partial removal of
the canberra libraries. Please "dpkg -l | grep canberra" and provide
the result.

Regards,

Adam

Bug#910538: RFS: vitetris/0.57.2-1 [ITP]

[Baptiste BEAUPLAT]

Package: sponsorship-requests
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear mentors,

I am looking for a sponsor for my package "vitetris"

 Package name: vitetris
 Version : 0.57.2-1
 Upstream Author : Victor Geraldsson
 URL : http://www.victornils.net/tetris/
 License : BSD-2-Clause
 Section : games

It builds those binary packages:

  vitetris   - Virtual terminal *tris clone

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

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


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

  dget -x 
https://mentors.debian.net/debian/pool/main/v/vitetris/vitetris_0.57.2-1.dsc

More information about vitetris can be obtained from 
http://www.victornils.net/tetris/.
Changes since the last upload:

  * Initial release (Closes: #909968)

Best Regards,

- --
Baptiste BEAUPLAT - lyknode

-BEGIN PGP SIGNATURE-

iIcEARYIAC8WIQQt4kiVMTxdp/CJ4U4XSUsQeV3XMwUCW7poQhEcbHlrbm9kZUBj
aWxnLm9yZwAKCRAXSUsQeV3XM9vkAQDQedW+9NAusU3/m9Fz7G9yiBl0FmMbPYyZ
ooLMrVJrGAD/Z2rk8NRHz1nDPOwcnCVnoL08u8zxBkqJQTApxDhUigw=
=cAAC
-END PGP SIGNATURE-

Bug#910537: reportbug: using GUI editor in reportbug seems to need canberra-gtk-module but it isn't in suggests or anywhere

[shirish शिरीष]

Package: reportbug
Version: 7.5.0
Severity: normal

Dear Maintainer,
Whenever I use leafpad to use reportbug I get the following -

Please select tags: (one at a time) [none]
Gathering additional data, this may take a while...
Spawning leafpad...
Gtk-Message: 01:27:29.888: Failed to load module "canberra-gtk-module"

I guess this needs/needed libcanberra-gtk-module but for some reason
isn't in suggests ? Maybe using leafpad as an editor is an oddity ? I
dunno whether the severity should be in normal or a wishlist.

-- Package-specific info:
** Environment settings:
INTERFACE="text"

** /home/shirish/.reportbugrc:
reportbug_version "7.1.10"
expert
mode standard
ui text
realname "shirish"
email "shirisha...@.xxx"
no-cc
header "X-Debbugs-CC: shirisha...@.xxx"
smtphost reportbug.debian.org
editor "leafpad"

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

Kernel: Linux 4.18.0-1-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 reportbug depends on:
ii  apt1.7.0~rc2
ii  python33.6.6-1
ii  python3-reportbug  7.5.0
ii  sensible-utils 0.0.12

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail 
ii  debconf-utils  1.5.69
ii  debsums2.2.3
ii  dlocate1.07+nmu1
pn  emacs24-bin-common | emacs25-bin-common
ii  exim4-daemon-light [mail-transport-agent]  4.91-8
ii  file   1:5.34-2
ii  gnupg  2.2.10-2
pn  python3-urwid  
pn  reportbug-gtk  
ii  xdg-utils  1.1.3-1

Versions of packages python3-reportbug depends on:
ii  apt1.7.0~rc2
ii  file   1:5.34-2
ii  python33.6.6-1
ii  python3-apt1.7.0~rc1
ii  python3-debian 0.1.33
ii  python3-debianbts  2.7.2
ii  python3-requests   2.18.4-2

python3-reportbug 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
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#910453: lintian: false positive for package-does-not-use-debhelper-or-cdbs when using blends-dev

[Holger Levsen]

On Sun, Oct 07, 2018 at 09:02:30PM +0100, Chris Lamb wrote:
> Fixed in Git, pending upload:
 
\o/

thank you!


-- 
cheers,
Holger

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


signature.asc
Description: PGP signature

Bug#910453: lintian: false positive for package-does-not-use-debhelper-or-cdbs when using blends-dev

[Chris Lamb]

tags 910453 + pending
thanks

Fixed in Git, pending upload:

  
https://salsa.debian.org/lintian/lintian/commit/3d2a2e08d6da449f434c85eee0d6cfe55c8cb073

  checks/debhelper.pm | 1 +
  debian/changelog| 4 
  2 files changed, 5 insertions(+)


Regards,

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

Bug#910536: guake: getting runtime error checks in .xsession-errors file

[shirish]

Package: guake
Version: 3.3.0-1
Severity: normal

Dear Maintainer,

I have been getting the following errors in my .xsession-errors file . 

(guake:1960): Vte-WARNING **: 01:09:20.388: (../../src/vtegtk.cc:1964):int 
vte_terminal_match_add_regex(VteTerminal*, VteRegex*, guint32): runtime check 
failed: (_vte_regex_get_compile_flags(regex) & PCRE2_MULTILINE)

(guake:1960): Vte-WARNING **: 01:09:20.389: (../../src/vtegtk.cc:1964):int 
vte_terminal_match_add_regex(VteTerminal*, VteRegex*, guint32): runtime check 
failed: (_vte_regex_get_compile_flags(regex) & PCRE2_MULTILINE)

(guake:1960): Vte-WARNING **: 01:09:20.389: (../../src/vtegtk.cc:1964):int 
vte_terminal_match_add_regex(VteTerminal*, VteRegex*, guint32): runtime check 
failed: (_vte_regex_get_compile_flags(regex) & PCRE2_MULTILINE)

(guake:1960): Vte-WARNING **: 01:09:20.389: (../../src/vtegtk.cc:1964):int 
vte_terminal_match_add_regex(VteTerminal*, VteRegex*, guint32): runtime check 
failed: (_vte_regex_get_compile_flags(regex) & PCRE2_MULTILINE)

(guake:1960): Vte-WARNING **: 01:09:20.389: (../../src/vtegtk.cc:1964):int 
vte_terminal_match_add_regex(VteTerminal*, VteRegex*, guint32): runtime check 
failed: (_vte_regex_get_compile_flags(regex) & PCRE2_MULTILINE)

(guake:1960): Vte-WARNING **: 01:09:20.389: (../../src/vtegtk.cc:1964):int 
vte_terminal_match_add_regex(VteTerminal*, VteRegex*, guint32): runtime check 
failed: (_vte_regex_get_compile_flags(regex) & PCRE2_MULTILINE)

please fix the above. 


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

Kernel: Linux 4.18.0-1-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 guake depends on:
ii  gir1.2-glib-2.0   1.58.0-1
ii  gir1.2-gtk-3.03.24.1-2
ii  gir1.2-keybinder-3.0  0.3.2-1
ii  gir1.2-notify-0.7 0.7.7-3
ii  gir1.2-pango-1.0  1.42.4-3
ii  gir1.2-vte-2.91   0.54.0-1
ii  libglib2.0-bin2.58.1-2
ii  python3   3.6.6-1
ii  python3-cairo 1.16.2-1+b1
ii  python3-dbus  1.2.8-2+b1
ii  python3-gi3.30.1-1
ii  python3-pbr   4.2.0-4

guake recommends no packages.

Versions of packages guake suggests:
ii  libutempter0 1.1.6-3
pn  numix-gtk-theme  

-- no debconf information

Bug#910535: guake: getting runtime error checks in .xsession-errors file

[shirish शिरीष]

Package: guake
Version: 3.3.0-1
Severity: normal

Dear Maintainer,

I have been getting the following errors in my .xsession-errors file .

(guake:1960): Vte-WARNING **: 01:09:20.388:
(../../src/vtegtk.cc:1964):int
vte_terminal_match_add_regex(VteTerminal*, VteRegex*, guint32):
runtime check failed: (_vte_regex_get_compile_flags(regex) &
PCRE2_MULTILINE)

(guake:1960): Vte-WARNING **: 01:09:20.389:
(../../src/vtegtk.cc:1964):int
vte_terminal_match_add_regex(VteTerminal*, VteRegex*, guint32):
runtime check failed: (_vte_regex_get_compile_flags(regex) &
PCRE2_MULTILINE)

(guake:1960): Vte-WARNING **: 01:09:20.389:
(../../src/vtegtk.cc:1964):int
vte_terminal_match_add_regex(VteTerminal*, VteRegex*, guint32):
runtime check failed: (_vte_regex_get_compile_flags(regex) &
PCRE2_MULTILINE)

(guake:1960): Vte-WARNING **: 01:09:20.389:
(../../src/vtegtk.cc:1964):int
vte_terminal_match_add_regex(VteTerminal*, VteRegex*, guint32):
runtime check failed: (_vte_regex_get_compile_flags(regex) &
PCRE2_MULTILINE)

(guake:1960): Vte-WARNING **: 01:09:20.389:
(../../src/vtegtk.cc:1964):int
vte_terminal_match_add_regex(VteTerminal*, VteRegex*, guint32):
runtime check failed: (_vte_regex_get_compile_flags(regex) &
PCRE2_MULTILINE)

(guake:1960): Vte-WARNING **: 01:09:20.389:
(../../src/vtegtk.cc:1964):int
vte_terminal_match_add_regex(VteTerminal*, VteRegex*, guint32):
runtime check failed: (_vte_regex_get_compile_flags(regex) &
PCRE2_MULTILINE)

please fix the above.

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

Kernel: Linux 4.18.0-1-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 guake depends on:
ii  gir1.2-glib-2.0   1.58.0-1
ii  gir1.2-gtk-3.03.24.1-2
ii  gir1.2-keybinder-3.0  0.3.2-1
ii  gir1.2-notify-0.7 0.7.7-3
ii  gir1.2-pango-1.0  1.42.4-3
ii  gir1.2-vte-2.91   0.54.0-1
ii  libglib2.0-bin2.58.1-2
ii  python3   3.6.6-1
ii  python3-cairo 1.16.2-1+b1
ii  python3-dbus  1.2.8-2+b1
ii  python3-gi3.30.1-1
ii  python3-pbr   4.2.0-4

guake recommends no packages.

Versions of packages guake suggests:
ii  libutempter0 1.1.6-3
pn  numix-gtk-theme  

-- 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
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#910447: Wrong package

[Thomas Goirand]

Hi Helmut,

Thanks for your bug report, however 2 things:

1/ The issue really lives in python-taskflow, in its definition of
StrEnum, which is a class that inherits from both Python strings and
Python Enum.

2/ Do you really think I need *ALL* of your build log here? I really
need only what was after the "Failures during discovery" thing... Next
time, it's much better to *attach* your build log, and just copy/past
the end of the log.

FYI, I do have a fix for taskflow which should fix everything, which in
fact consists of removing the bad calls that it shouldn't do.

Cheers,

Thomas Goirand (zigo)

Bug#910511: [Pkg-utopia-maintainers] Bug#910511: Bug#910511: network-manager-openvpn: openvpn 2.4 in stable supports tls-crypt, but nm-openvpn 1.2.8 in stable doesn't

[Michael Biebl]

Am 07.10.18 um 17:30 schrieb Gijs Molenaar:
> Hi Michael,
> 
> 
> Op zo 7 okt. 2018 om 16:36 schreef Michael Biebl  >:
> 
> Am 07.10.18 um 16:15 schrieb Michael Biebl:
> > That said, 1.2.10 could be provided via stretch-backports:
> > https://backports.debian.org/
> 
> Fwiw, if we go the stretch-backports route, then it would probably make
> sense to use the current version from testing, i.e. 1.8.4-1
> 
> 
> Having a backport would already help a lot, so yes please! And yes, any
> version greater than 1.2.10 is enough for us but it probably makes sense
> to use the latest testing. 

Ok, let's go this way then.
I've just uploaded network-manager_1.12.4-1~bpo9+1 to stretch-backports.
Once that is accepted, I'll upload network-manager-openvpn_1.8.4-1 as well.




-- 
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#910534: adplug: CVE-2018-17825: several double-free vulnerabilities in the CEmuopl class in emuopl.cpp

[Salvatore Bonaccorso]

Source: adplug
Version: 2.2.1+dfsg3-0.4
Severity: important
Tags: patch security upstream
Forwarded: https://github.com/adplug/adplug/issues/67

Hi,

The following vulnerability was published for adplug.

CVE-2018-17825[0]:
| An issue was discovered in AdPlug 2.3.1. There are several double-free
| vulnerabilities in the CEmuopl class in emuopl.cpp because of a
| destructor's two OPLDestroy calls, each of which frees TL_TABLE,
| SIN_TABLE, AMS_TABLE, and VIB_TABLE.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-17825
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-17825

Regards,
Salvatore

Bug#672704: [blop] LADSPA plugins shouldn't call setlocale()

[trebmuh]

Hi all,

I can confirm that the bug is still present in the 0.2.8-6 package on
Debian Stretch.

The way I encountered it is that I (manually by compilation since
there
is no package in Debian for it) installed cinelerra (both CV and GG
version), then when launching it, its GUI is in English. Then, I've
removed the blop package (with synaptic) and relaunched cinelerra and
now, the GUI is displayed in French (my locale).

I've seen that there is a patch attached, but it seems from the
comment
above that it's not safe to apply it so I didn't try.

What would you people would recommend to move forward from here?
It could be great to have this one fixed for the next buster release.

Cheers,
Olivier

PS : note that this bug is affecting mhWaveEdit as well.

Steps to reproduce with mhWaveEdit:
1) open mhwaveedit with a French locale
2) go to Fichier -> Ouvrir... (file -> open...) and open an audio file
3) cut (ctrl-x) a part of it
4) go to Fichier -> Quitter (file -> quit)
the pop up window asking if you want to save the changes is in French.

All good.

Then (with the blop package installed):
5) open mhwaveedit with a French locale
6) go to Fichier -> Ouvrir... (file -> open...) and open an audio file
7) got to Effets -> boite à effets...
see that a part of this new window is in English
8) push the "Fermer" button ("close")
9) cut (ctrl-x) a part of the audio file
10) go to Fichier -> Quitter (file -> quit)
the pop up window asking if you want to save the changes is now in
English. Something is wrong here.

Then, uninstall the blop package:
11) open mhwaveedit with a French locale
12) go to Fichier -> Ouvrir... (file -> open...) and open an audio
file
13) got to Effets -> boite à effets...
see that a the window is now fully in French
8) push the "Fermer" button ("close")
9) cut (ctrl-x) a part of the audio file
10) go to Fichier -> Quitter (file -> quit)
now, the pop up window asking if you want to save the changes is in
French. All good.

PS-2: copying debian multimedia maintainer to this report



Wouldn't the most clean approach be to configure the package with
'--disable-nls' and be done with it?

 - Fabian


Hi Fabian,
it might work, but it would means then loosed the translations.
There is currently a german translation included in the sources.

Since I wrote this earlier email today, a friend of mine, who is 
programmer, undertook to write a proper patch for blop. We'll add it to 
this report when done.


Olivier

Bug#910533: RFP: golang-notabug-themusicgod1-ratelimit -- Simple, thread-safe Go rate-limiter

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: golang-notabug-themusicgod1-ratelimit
  Version : 4a38dca83e
  Upstream Author : Dimitrij Denissenko 
* URL : https://notabug.org/themusicgod1/ratelimit
* License : MIT
  Programming Lang: go
  Description : Simple, thread-safe Go rate-limiter

Not to be confused with the go ratelimit that 
is golang-github-jacobsa-ratelimit-dev or golang-github-juju-ratelimit-dev
Inspired by Antti Huima's algorithm.

Instances are thread safe.

Depended on by redis.v4 ( #910530 ).

Bug#908615: Issue with Python3.7

[Jérôme Kieffer]

Hi,

I am the main developper of pyFAI and we are aware there are issues
with python 3.7.0 (we have issues opened on github about that). We will
re-enable CI on python-3.7 as soon as 3.7.1 is out and our code can run
on it.

Would it be possible to get an extra month to setup a new release
supporting python 3.7 as today our code cannot run due to missing
dependencies.

Thanks for your patience.

Cheers,

Jerome

Bug#910532: src:haskell-enumerator: unlikely to be worth the maintenance burden

[Clint Adams]

Package: src:haskell-enumerator
Version: 0.4.20-7
Severity: serious

If there is a good reason to keep this package, please close the bug.

Bug#909941: erlang 21.1+dfsg-1 causes rabbitmq-server to fail to start/install

[Paul Gevers]

reassign -1 src:erlang 1:21.1+dfsg-1
severity -1 serious
affects -1 src:rabbitmq-server
thanks

On 07-10-18 19:26, Paul Gevers wrote:
> On Sun, 30 Sep 2018 12:54:10 +0100 Jose Antonio Ortega Ruiz
>  wrote:
>> This version of the server fails to start using systemd:
> 
> Yes, but until recently it worked. So this is a regression caused by
> some other package.
> 
> Also the autopkgtest of debci in unstable [1] is showing this since
> 2018-09-27. I'll try to figure out which package update caused this and
> reassign. I'm suspecting one of the erlang packages.

> [1] https://ci.debian.net/packages/d/debci/unstable/amd64/

I triggered the debci autopkgtest in testing with binary packages from
src:openssl from unstable [2]. The test passes. I also triggered the
debci autopkgtest in testing with binary packages from src:openssl and
src:erlang from unstable [3]. The test fails with rabbitmq-server
failing to install in the same way as reported in this bug.

Because of all the version locks between the erlang binary packages I
don't know which package from src:erlang is really causing this issue.

Paul

[2]
https://ci.debian.net/data/autopkgtest/testing/amd64/d/debci/1106446/log.gz
[3]
https://ci.debian.net/data/autopkgtest/testing/amd64/d/debci/1106437/log.gz



signature.asc
Description: OpenPGP digital signature

Bug#672704: [blop] LADSPA plugins shouldn't call setlocale()

[fabian]

Wouldn't the most clean approach be to configure the package with 
'--disable-nls' and be done with it? 
 - Fabian 
 Ursprüngliche Nachricht Von: treb...@tuxfamily.org Datum: 
07.10.18  15:15  (GMT+01:00) An: 672...@bugs.debian.org Betreff: [blop] LADSPA 
plugins shouldn't call setlocale() 
Hi all,

I can confirm that the bug is still present in the 0.2.8-6 package on 
Debian Stretch.

The way I encountered it is that I (manually by compilation since there 
is no package in Debian for it) installed cinelerra (both CV and GG 
version), then when launching it, its GUI is in English. Then, I've 
removed the blop package (with synaptic) and relaunched cinelerra and 
now, the GUI is displayed in French (my locale).

I've seen that there is a patch attached, but it seems from the comment 
above that it's not safe to apply it so I didn't try.

What would you people would recommend to move forward from here?
It could be great to have this one fixed for the next buster release.

Cheers,
Olivier

PS : note that this bug is affecting mhWaveEdit as well.

Steps to reproduce with mhWaveEdit:
1) open mhwaveedit with a French locale
2) go to Fichier -> Ouvrir... (file -> open...) and open an audio file
3) cut (ctrl-x) a part of it
4) go to Fichier -> Quitter (file -> quit)
the pop up window asking if you want to save the changes is in French. 
All good.

Then (with the blop package installed):
5) open mhwaveedit with a French locale
6) go to Fichier -> Ouvrir... (file -> open...) and open an audio file
7) got to Effets -> boite à effets...
see that a part of this new window is in English
8) push the "Fermer" button ("close")
9) cut (ctrl-x) a part of the audio file
10) go to Fichier -> Quitter (file -> quit)
the pop up window asking if you want to save the changes is now in 
English. Something is wrong here.

Then, uninstall the blop package:
11) open mhwaveedit with a French locale
12) go to Fichier -> Ouvrir... (file -> open...) and open an audio file
13) got to Effets -> boite à effets...
see that a the window is now fully in French
8) push the "Fermer" button ("close")
9) cut (ctrl-x) a part of the audio file
10) go to Fichier -> Quitter (file -> quit)
now, the pop up window asking if you want to save the changes is in 
French. All good.


PS-2: copying debian multimedia maintainer to this report

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintain...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#909813: rr FTBFS with kernel 4.18 headers

[Stephen Kitt]

Control: reassign -1 src:linux
Control: found -1 4.18.8-1
Control: fixed -1 4.18.11-1
Control: affects -1 src:rr

On Sat, 29 Sep 2018 07:40:45 +0300, Adrian Bunk  wrote:
> /build/1st/rr-5.2.0/src/test/keyctl.c: In function 'main':
> /build/1st/rr-5.2.0/src/test/keyctl.c:44:38: error: 'struct
> keyctl_dh_params' has no member named 'private'; did you mean 'dh_private'?
> struct keyctl_dh_params params = {.private = private_key, ^~~
>   dh_private
> /usr/bin/cc -g -O2 -ffile-prefix-map=/build/1st/rr-5.2.0=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -msse2 -D__MMX__ -D__SSE__ -D__SSE2__
> -D__USE_LARGEFILE64 -pthread -g3 -Wstrict-prototypes -std=gnu11
> -Wl,-z,relro -Wl,-z,now CMakeFiles/kcmp.dir/src/test/kcmp.c.o  -o bin/kcmp
> -lrt -ldl make[3]: *** [CMakeFiles/keyctl.dir/build.make:66:
> CMakeFiles/keyctl.dir/src/test/keyctl.c.o] Error 1

This is a kernel regression in 4.18.8, fixed in 4.18.11:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=31426b5

Regards,

Stephen


pgp7YElOAepWP.pgp
Description: OpenPGP digital signature

Bug#910506: split package into architecture dependent and independent ones

[W. Martin Borgert]

On 2018-10-07 20:14, Victor Seva wrote:
> Sorry but I think the slip has no real benefit. I'm with Boris here.

Two against one, how mean! :~)
OK, reverting then.
Thanks for your PoV to both of you!

Bug#910135: xserver-dorg-core: Xserver crashes after update to 1.20.1-4

[Davide Prina]

Hi,

I have reported a similar problem with the bug #907655, I have 
mistakenly open the bug to the xserver-xorg-video-mga (I have a gma not 
mga video card) and not the xserver-xorg-core (I have ask to move here 
the bug here... if someone can do that...).


Also for me the last version that start X is the 2:1.19.6-1, as you can 
see from the bug #907655 I have try to install all the version after 
that that are present on the snapshot.debian.org site.


Each time I have to upgrade my system I do:
# apt -f install
# apt update; apt -u upgrade; apt -u dist-upgrade
# dpkg -i xserver-xog-core-2%3a1.19.6-1_i386.deb

elsewhere the X don't start.

Tell me if I can do some test or you need more info.

Ciao
Davide

Bug#906643: transition: php7.3

[Ondřej Surý]

Dammit, I completely forgot the phpapi change between the beta and the RC :(.  
Sorry about that.

The good should be: 20180731

The bad should be: 20180606 and 20170718

e.g. those binNMUs were wasted time :( and they will need to be triggered 
again.  Sorry for that.

Thanks,
Ondrej
-- 
Ondřej Surý 

On Sun, Oct 7, 2018, at 12:08, Emilio Pozuelo Monfort wrote:
> On 02/10/2018 21:00, Emilio Pozuelo Monfort wrote:
> > Control: tags -1 confirmed
> > Control: forwarded -1 
> > https://release.debian.org/transitions/html/php7.3.html
> > 
> > On 19/08/2018 08:49, Ondřej Surý wrote:
> >> Package: release.debian.org
> >> Severity: normal
> >> User: release.debian@packages.debian.org
> >> Usertags: transition
> >>
> >> Hi,
> >>
> >> with PHP 7.3.0~beta2, I would like to start a transition from PHP 7.2
> >> to PHP 7.3, so we have the latest PHP version in Debian buster, so the
> >> security support can be provided by upstream as longest as possible.
> > 
> > Since the transition has started, let's mark it as such.
> > 
> >> title = "php7.3";
> >> is_affected = .depends ~ "phpapi-20170718" | .depends ~ "phpapi-20180606";
> >> is_good = .depends ~ "phpapi-20180606";
> >> is_bad = .depends ~ "phpapi-20170718";
> > 
> > I have added & ! .depends ~ "phpapi-20180606" to is_bad, so that packages 
> > that
> > depend on both are marked as good and not as "partial" (both good and bad). 
> > Once
> > we have things rebuilt and 7.2 support is dropped from -defaults, we can 
> > change
> > the tracker and rebuild things again to lose 7.2 dependencies. If things 
> > don't
> > take long (i.e. any ftbfs or other bugs are fixed promptly) I think we can
> > finish this before the transition freeze.
> 
> Should we add phpapi-20180731 to is_good? Packages are getting that now, 
> see e.g.:
> 
> https://buildd.debian.org/status/fetch.php?pkg=php-propro&arch=mipsel&ver=2.1.0%2B1.0.2-1%2Bb1&stamp=1538764097&raw=0
> 
> Emilio

Bug#910506: split package into architecture dependent and independent ones

[Victor Seva]

Hi,

On Sun, Oct 7, 2018, 20:09 W. Martin Borgert  wrote:

> On 2018-10-07 18:05, Boris Pek wrote:
> > I would suggest you to reconsider all pros and cons of this decision.
>
> Sorry for already uploading my change. I should have waited for
> comments, esp. after asking! I'm absolutely open to revert the
> change, if we would agree, that it were a bad idea. It is only
> one commit. So far, I still think, the split is a good idea,
> but I do not care too much about it. Any comment from the
> prosody uploaders?
>

Sorry but I think the slip has no real benefit. I'm with Boris here.

Cheers,
Victor

Bug#910506: split package into architecture dependent and independent ones

[W. Martin Borgert]

On 2018-10-07 18:05, Boris Pek wrote:
> At first let's look at package size:
> https://packages.debian.org/experimental/prosody
> It is about 282.4 KB. And this is very small size.

It is true, that this is not a huge package. But you need to
multiple by number of architectures (= 21). This is 280 x 21
vs 270 x 1 + 30 x 21, or 5.7 MB vs 0.9 MB.

> Next, let's remember that each separate package increases size of list
> of packages in Debian archive:
> https://cdn-aws.deb.debian.org/debian/dists/unstable/main/
> which will be downloaded by all Debian users even is they do not use
> this package.

This is a general problem in Debian, yes. However, this split
increases the number of packages by only 0.0012 percent.

(Debian must solve the Packages growth problem anyway. We add
new packages every day, which is good. But the global, huge list
becomes a burden. My embedded systems cannot use official
mirrors since 6.0/squeeze because of that. I'm not aware of any
possible solution, unfortunately. I use private mirrors with
only some hundreds of packages.)

> Thus you offer to increase complexity of source package (split on few
> packages with declaration of relationships between them), possibly

It is only some lines in debian/control and an extra install
file of one line, more or less. Added complexity, but very,
very moderate.

> increase work of ftp-masters (think about changing of SOVERSIONs in the
> future, etc.) and increase of size of lists of packages just for
> decreasing size of binary packages to about tens of kilobytes?

I'm not sure, but is SOVERSIONs a problem when no other package
uses the modules? I'm pretty sure, that there is no such
complexity involved, because it is just a one-to-one
relationship between prosody and prosody-libs. There is no
libprosody nor libprosody-dev...

> I would suggest you to reconsider all pros and cons of this decision.

Sorry for already uploading my change. I should have waited for
comments, esp. after asking! I'm absolutely open to revert the
change, if we would agree, that it were a bad idea. It is only
one commit. So far, I still think, the split is a good idea,
but I do not care too much about it. Any comment from the
prosody uploaders?

Cheers

Bug#910493: Handle transition from MAT to MAT2

[Jonas Meurer]

Hi intrigeri,

Am 07.10.2018 um 10:31 schrieb intrigeri:
> let's discuss how we'll be handling the transition from MAT to MAT2
> in Buster. My goal here is to avoid users keeping using the
> deprecated, unmaintained MAT v1, and to nicely transition them to the
> new MAT2 implementation.

Full ack. Thanks for bringing this up.

> As I wrote on the ITP (trimming down ideas that don't make sense
> anymore):
> 
> intrigeri:
>> What matters to me is the users' perspective. I think we should
>> provide a clear, unambiguous transition path and avoid leaking
>> technical details to users. So once MAT2 reaches feature parity with
>> MAT (I think the only real blocker is the lack of a Nautilus
>> extension; MAT v1's seems to be broken on sid currently but it has
>> a GUI which mitigates that problem) I think we should:
> 
>>  - Have mat2 conflicts+replaces mat, remove mat from testing+sid,
>>and ship a transitional package called mat that pulls mat2 in.
> 
> IMO we should do that as soon as mat2 installs the Nautilus extension
> (#910491).
> 
> Does this make sense to you? Is there a better way to handle this?

The main advantage of mat over mat2 I know of is the GUI. But since mat
is broken and should no longer be used for security reasons, my
suggestion would be to ignore this advantage and go ahead with the
transition exactly the way you described it.

Cheers
 jonas



signature.asc
Description: OpenPGP digital signature

Bug#835394: [pkg-gnupg-maint] Bug#835394: Same issue here

[Sofus Rose]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Cheers,

I've been having the same issue, where I'm getting this error when ssh'ing
into just about anything:

sign_and_send_pubkey: signing failed: agent refused operation

I do indeed startup my graphical session in a non-standard way (for
unrelated reasons):

0. systemd is set to a text startup target.
1. I login to a tty text console.
2. I run startx

It may be worth noting that after my DE (Budgie) has started, I'm usually
prompted to enter my password to unlock the login keychain.

Like others in this thread have mentioned, running the following command
seems to fix everything until I shut down:

$ gpg-connect-agent updatestartuptty /bye

Some system info:
$ uname -a
Linux dawnrose 4.18.0-1-amd64 #1 SMP Debian 4.18.8-1 (2018-09-18) x86_64
GNU/Linux

Hope this can help!

Regards,
Sofus Rose
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE47NF7/9bOZS8HRJgPQG+lfPv/rkFAlu6Rl8ACgkQPQG+lfPv
/rkC5Q//W+wDqyxH5E3K/qQJVU75FFl7wZmXurqMdNZ/bGcBwxNUvtu2XhBGiMpD
8Tjf3GZaljaExI7vy4q9Cl3lWgnT8LZfoxcFKV6JQllYg1Zq8l5fFeKZ3Y1SERAy
PjO/mKGsgeuMBvqkoqQxndk+VJOPWiYtaiSlzvMg9cizj8H2Bqi/idTwLaN8pOkP
rh4dbzIxlq+xUjwSGZTeYBsZW+kYWygd5p/oQcPPnCvZwik8auVkTWDu+esosw9P
DfMmCRE13kGHzPgJ5Kth2El+EUKVozlEL5d2oN6DLMoKQ7bVQbKsSquhDfm6WXac
tML+LdwrNUBufInmk5D3YCwZpknZnUy3aBGW/u6ccM62XBItU5UhWHNLG+VzGyOu
Hio3olrL+NLQnkUZwrYsRF47RBbpA2WA8z082nWN5/e2xlnE2uQH46BKrDKmwy6g
j465OPZJ2m4ioLGuXhvZtGYVHIf8Ny4w4ACbRRtO5UldLpPbq/DqQWLZmytBqTzV
OMcHQcP9iEOXSOWjvzC1HwPKh8CmRHjASZrldv0qjSSrmNW2sb8Puk7NzJ9JwyP0
jJBss8g+tJDzc/n9tbT8haU1lCb1oqv8s5AVfINtZuXtXD6lZfKnqIHorXgcptOT
hz34NBMaTw5O3bHR8kxMv3oL/UDiwpe91EY/uuG7f8sGdqYBuLI=
=uLKB
-END PGP SIGNATURE-

Bug#910531: kdepim-runtime: Authenticating to gmail using "Gmail" authentication type (oauth, kgapi?) leads to segfault

[Juha Jäykkä]

Package: kdepim-runtime
Version: 4:18.08.1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

The "Gmail" authentication type [1] no longer works. Using it for existing 
akonadi gmail accounts
or creating a new one, always results in a sigsegv (backtrace can be found at 
http://paste.debian.net/1046257/).

This renders all gmail accounts with proper security unusable.

There is a workaround, which reduces security: Allowing unsecure access and 
then creating
an application password for akonadi, allows login and continued access to 
emails, but with
significantly reduced security. Not sure if this is "grave": without the 
workaround I would
imagine this warrants grave due to the ubiquitousness of gmail and with the 
workaround this
causes a nasty decrease in security.

[1] This is the authentication method listed in "Advanced" options in the 
account config. I am
not sure what it actually is, but I suppose it uses libsasl2-modules-kdexoauth2.

Cheers,
Juha

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

Kernel: Linux 4.18.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_GB.UTF-8), LANGUAGE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kdepim-runtime depends on:
ii  akonadi-server   4:18.08.1-1
ii  kio  5.49.0-1
ii  kio-ldap 18.08.1-1
ii  kio-sieve4:18.08.1-1
ii  libc62.27-6
ii  libgcc1  1:8.2.0-7
ii  libkf5akonadiagentbase5  4:18.08.1-1
ii  libkf5akonadicalendar5abi1   4:18.08.1-1
ii  libkf5akonadicontact54:18.08.1-1
ii  libkf5akonadicore5abi2   4:18.08.1-1
ii  libkf5akonadimime5   4:18.08.1-2
ii  libkf5akonadinotes5  4:18.08.1-1
ii  libkf5akonadiwidgets5abi14:18.08.1-1
ii  libkf5alarmcalendar5abi1 4:18.08.1-1
ii  libkf5calendarcore5abi2  4:18.08.1-1
ii  libkf5codecs55.49.0-1
ii  libkf5completion55.49.0-1
ii  libkf5configcore55.49.0-1
ii  libkf5configgui5 5.49.0-1
ii  libkf5configwidgets5 5.49.0-1
ii  libkf5contacts5  4:18.08.1-1
ii  libkf5coreaddons55.49.0-1
ii  libkf5dbusaddons55.49.0-1
ii  libkf5i18n5  5.49.0-1
ii  libkf5identitymanagement518.08.1-1
ii  libkf5imap5  18.08.1-1
ii  libkf5itemmodels55.49.0-1
ii  libkf5jobwidgets55.49.0-1
ii  libkf5kdelibs4support5   5.49.0-1
ii  libkf5kiocore5   5.49.0-1
ii  libkf5kiowidgets55.49.0-1
ii  libkf5mailtransport5 18.08.1-1
ii  libkf5mailtransportakonadi5  18.08.1-1
ii  libkf5mbox5  18.08.1-1
ii  libkf5mime5abi1  18.08.1-1
ii  libkf5notifications5 5.49.0-1
ii  libkf5notifyconfig5  5.49.0-1
ii  libkf5service-bin5.49.0-1
ii  libkf5service5   5.49.0-1
ii  libkf5textwidgets5   5.49.0-1
ii  libkf5wallet-bin 5.49.0-1
ii  libkf5wallet55.49.0-1
ii  libkf5widgetsaddons5 5.49.0-1
ii  libkf5windowsystem5  5.49.0-1
ii  libkf5xmlgui55.49.0-1
ii  libkolabxml1v5   1.1.6-3+b1
ii  libkpimgapicalendar5 18.08.1-1
ii  libkpimgapicontacts5 18.08.1-1
ii  libkpimgapicore5abi1 18.08.1-1
ii  libkpimgapitasks518.08.1-1
ii  libkpimkdav5abi2 18.08.1-1
ii  libqt5core5a 5.11.1+dfsg-9
ii  libqt5dbus5  5.11.1+dfsg-9
ii  libqt5gui5   5.11.1+dfsg-9
ii  libqt5network5   5.11.1+dfsg-9
ii  libqt5texttospeech5  5.11.1-2
ii  libqt5webenginecore5 5.11.1+dfsg-5
ii  libqt5webenginewidgets5  5.11.1+dfsg-5
ii  libqt5widgets5   5.11.1+dfsg-9
ii  libqt5xml5   5.11.1+dfsg-9
ii  libsasl2-2   2.1.27~rc8-1
ii  libsasl2-modules-kdexoauth2  18.08.1-1
ii  libstdc++6   8.2.0-7

kdepim-runtime recommends no packages.

kdepim-runtime suggests no packages.

-- no debconf information

Bug#910530: RFP: notabug-themusicgod1-redis.v4-dev -- Redis client for Golang

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: notabug-themusicgod1-redis.v4-dev
  Version : v4.2.4
  Upstream Author : The Redis Go Client Authors
* URL : https://notabug.org/themusicgod1/redis/src/newv4
* License : BSD-2.0
  Programming Lang: go
  Description : Redis client for Golang

This package provides Redis client for Golang.
There already exists a golang-gopkg-redis.v2-dev in debian
but higher version'd redis servers/clients exist - in particular v4 
which is required by, among other things, goarista #858722

(as of 2018, v6 also currently exists)

Bug#909488: There is a possible fix an the recent upstream version

[kinky_nekoboi]

Please build and push

Bug#910529: courier-webadmin: wrong permissions in /etc/courier/webadmin

[Jean Louis]

Package: courier-webadmin
Version: 0.76.3-5
Severity: important

Dear Maintainer,

All permissions shall be courier:courier for /etc/courier/webadmin

Otherwise settings don't work.

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

Kernel: Linux 4.9.0-7-amd64 (SMP w/1 CPU core)
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 courier-webadmin depends on:
ii  apache2 [httpd]2.4.25-3+deb9u5
ii  courier-base   0.76.3-5
ii  debconf [debconf-2.0]  1.5.61
ii  libc6  2.24-11+deb9u3

courier-webadmin recommends no packages.

Versions of packages courier-webadmin suggests:
pn  courier-doc  

-- debconf information:
* courier-webadmin/install-cgi: true

Bug#909941: rabbitmq-server: Fails to start

[Paul Gevers]

user debian...@lists.debian.org
usertags 909941 regression
affects 909941 src:debci
thanks

On Sun, 30 Sep 2018 12:54:10 +0100 Jose Antonio Ortega Ruiz
 wrote:
> This version of the server fails to start using systemd:

Yes, but until recently it worked. So this is a regression caused by
some other package.

Also the autopkgtest of debci in unstable [1] is showing this since
2018-09-27. I'll try to figure out which package update caused this and
reassign. I'm suspecting one of the erlang packages.

Paul

[1] https://ci.debian.net/packages/d/debci/unstable/amd64/



signature.asc
Description: OpenPGP digital signature

Bug#910528: gmime: unneeded configure flag arguments

[Jeremy Bicha]

Source: gmime
Version: 3.2.0-2
Severity: minor

I looked at the debian/rules for gmime and I think there are 2
unnecessary lines:

Shouldn't this be the default for dh_auto_configure already?
$(shell dpkg-buildflags --export=configure) \

Nothing sets this variable now:
$(CONFIGURE_MONO_FLAGS)

Thanks,
Jeremy Bicha

Bug#910527: courier-webadmin, password file with wrong permissions

[Jean Louis]

Package: courier-webadmin
Version: 0.76.3-5
Severity: important

Dear Maintainer,

   * What led up to the situation?

After installation the password file is installed with wrong permissions:

1) It is group readable, courierwebadmin script fails to use such, it has to be 
only owner/group readable

2) It has permission root:courier, but it should be courier:courier

Then it works.


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

Kernel: Linux 4.9.0-7-amd64 (SMP w/1 CPU core)
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 courier-webadmin depends on:
ii  apache2 [httpd]2.4.25-3+deb9u5
ii  courier-base   0.76.3-5
ii  debconf [debconf-2.0]  1.5.61
ii  libc6  2.24-11+deb9u3

courier-webadmin recommends no packages.

Versions of packages courier-webadmin suggests:
pn  courier-doc  

-- debconf information:
* courier-webadmin/install-cgi: true

Bug#909119: stretch-pu: package vagrant/1.9.1+dfsg-1+deb9u1

[Antonio Terceiro]

On Sat, Oct 06, 2018 at 05:50:33PM +0100, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Tue, 2018-09-18 at 10:22 -0700, Antonio Terceiro wrote:
> > vagrant from stretch currently refuses to work with VirtualBox 5.2
> > from
> > stretch-backports. This update just backports the few changes needed
> > to
> > make it work. The changes are pretty trivial.
> > 
> > VirtualBox is not in stretch, so users are getting it either from
> > stretch-backports or from upstream's .deb package; without this
> > update
> > vagrant will most likely be broken for most VirtualBox users. It
> > would
> > be nice if we can release this update.
> > 
> 
> Please go ahead.

Just uploaded, thanks.


signature.asc
Description: PGP signature

Bug#910526: dkms_autoinstaller fails if run with zsh in sh compatibility mode

[Tino Calancha]

Package: dkms
Version: 2.3-2
Severity: important
Tags: patch upstream

Dear Maintainer,

When the system '/bin/sh' points to zsh shell, dkms_autoinstaller is run
with zsh in sh compatibility mode; this requires functions end
Fix syntactic error when the system shell is zsh

When the system '/bin/sh' points to the zsh shell,
then the script is run with zsh in sh compatibility mode; in that case
functions must end with either a semicolon or a newline.
(https://github.com/dell/dkms/issues/62)
* dkms_autoinstaller (log_end_msg):
Terminate the function with a semicolon.
Add missing white space in comment.

with either a semicolon or a newline.
In that case, this script fails with a parse error in function log_end_msg.

Bug reported upstream here:
--8<-cut here---start->8---
commit 9b44ee67e4a7fc4a215561c8a788a7ea66544ffb
diff --git a/dkms_autoinstaller b/dkms_autoinstaller
index 0e7f070..7fbe8f3 100755
--- a/dkms_autoinstaller
+++ b/dkms_autoinstaller
@@ -22,11 +22,11 @@ elif [ -f /etc/rc.d/init.d/functions ]; then
 . /etc/rc.d/init.d/functions
 fi
 
-#We only have these functions on debian/ubuntu
+# We only have these functions on debian/ubuntu
 # so on other distros just stub them out
 if [ ! -f /etc/debian_version ]; then
 alias log_daemon_msg=/bin/echo
-log_end_msg() { if [ "$1" = "0" ]; then echo " Done. "; else echo " 
Failed. "; fi }
+log_end_msg() { if [ "$1" = "0" ]; then echo " Done. "; else echo " 
Failed. "; fi; }
 alias log_action_begin_msg=log_daemon_msg
 alias log_action_end_msg=log_end_msg
 fi

--8<-cut here---end--->8---


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

Kernel: Linux 4.9.0-7-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 /bin/zsh
Init: systemd (via /run/systemd/system)

Versions of packages dkms depends on:
ii  build-essential  12.3
ii  coreutils8.26-3
ii  dpkg-dev 1.18.25
ii  gcc  4:6.3.0-4
ii  kmod 23-2
ii  make 4.1-9.1
ii  patch2.7.5-1+deb9u1

Versions of packages dkms recommends:
ii  fakeroot 1.21-3.1
ii  linux-headers-amd64  4.9+80+deb9u6
ii  lsb-release  9.20161125
ii  sudo 1.8.19p1-2.1

Versions of packages dkms suggests:
pn  menu
pn  python3-apport  

-- no debconf information

Bug#910525: courier-webadmin is dependent on CGI.pm

[Jean Louis]

Package: courier-webadmin
Version: 0.76.3-5
Severity: important

Dear Maintainer,

   * What led up to the situation?

courier-webadmin will not work if CGI.pm is not installed.




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

Kernel: Linux 4.9.0-7-amd64 (SMP w/1 CPU core)
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 courier-webadmin depends on:
ii  apache2 [httpd]2.4.25-3+deb9u5
ii  courier-base   0.76.3-5
ii  debconf [debconf-2.0]  1.5.61
ii  libc6  2.24-11+deb9u3

courier-webadmin recommends no packages.

Versions of packages courier-webadmin suggests:
pn  courier-doc  

-- debconf information:
* courier-webadmin/install-cgi: true

Bug#910522: r-cran-pracma: Incomplete debian/copyright?

[Chris Lamb]

Source: r-cran-pracma
Version: 2.1.5-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Oliver Dechant , ftpmas...@debian.org

Hi,

I just ACCEPTed r-cran-pracma from NEW but noticed it was missing 
attribution in debian/copyright for at least Jonas Lundgren, Greg
von Winckel, Paul Godfrey, etc.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

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

Bug#894260: RFS: ghostwriter/1.7.3-1 [ITP]

[Sebastien CHAVAUX]

  Package: sponsorship-requests
  Severity: normal [important for RC bugs, wishlist for new packages]

  Dear mentors,

  I am looking for a sponsor for my package "ghostwriter"

 * Package name: ghostwriter
   Version : 1.7.3-1
   Upstream Author :wereturtle 

 * URL :http://wereturtle.github.io/ghostwriter/
 * License : GPLv3
   Section : editors

  It builds those binary packages:

ghostwriter - Distraction-free, themeable Markdown editor

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

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


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

dget 
-xhttps://mentors.debian.net/debian/pool/main/g/ghostwriter/ghostwriter_1.7.3-1.dsc

  More information about ghostwriter
 can be obtained fromhttp://wereturtle.github.io/ghostwriter/.

  Changes since the last upload:

  - Update to version 1.7.3:
  * Fixed segfault that occurred when changing the theme or interface style 
after opening the Preview Options dialog


  Regards,
   Sebastien CHAVAUX

Bug#910524: r-cran-emoa: Incomplete debian/copyright?

[Chris Lamb]

Source: r-cran-emoa
Version: 0.5-0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Andreas Tille , ftpmas...@debian.org

Hi,

I just ACCEPTed r-cran-emoa from NEW but noticed it was missing 
attribution in debian/copyright for at least Mike Buselli and Wessel
Dankers.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

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

Bug#910523: r-cran-eaf: Incomplete debian/copyright?

[Chris Lamb]

Source: r-cran-eaf
Version: 1.8-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Andreas Tille , ftpmas...@debian.org

Hi,

I just ACCEPTed r-cran-eaf from NEW but noticed it was missing 
attribution in debian/copyright for at least Wessel Dankers, Mike
Buselli, etc.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

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