Bug#821914: Gtk-Message: 11:22:21.562: Failed to load module "canberra-gtk-module" in leafpad too.

[shirish शिरीष]

Hi all,

Another symptom. This appears to also happen in leafpad .

$ leafpad
Gtk-Message: 11:22:21.562: Failed to load module "canberra-gtk-module"

-- 
  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#910635: guake shows two windows in system tray

[shirish शिरीष]

Package: guake
Version: 3.3.0-1
Severity: normal

Dear Maintainer,

Guake shows two windows in the system tray. It might be partially due
to the .xsession errors shared in #910535 by me. The rest the system
tray screenshot will show.


-- 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#904289: libgo build failure with GCC trunk 20181004

[Ian Lance Taylor]

On Mon, Oct 8, 2018 at 8:59 PM, Matthias Klose  wrote:
> On 08.10.2018 11:47, Svante Signell wrote:
>> On Fri, 2018-10-05 at 21:10 +0200, Svante Signell wrote:
>>> On Fri, 2018-10-05 at 01:38 +0200, Matthias Klose wrote:
 Hi Svante,

 please have a look at the recent libgo build failure with GCC trunk
 20181004 after the libgo merge.  Please could you update the
 patches and send them upstream again?
>>>
>>> Well I don't really know where to submit the patches to upstream, but
>>> here they are. Cc:ing the gcc-snapshot bug 904...@bugs.debian.org
>>> too.
>>
>> Hi again,
>>
>> Seems like more changes were needed this time: Attached are three
>> updated patches:
>> src_libgo_go_syscall.diff
>> add-gnu-to-libgo-headers.diff
>> add-gnu-to-libgo-test-headers.diff
>
> Thanks for the update, but please could you send *all* the patches to
> gcc-patc...@gcc.gnu.org, and maybe CC Ian?  Patches really have to be ready to
> be applied upstream, and not to some Debian package.
>
> Please see https://gcc.gnu.org/contribute.html how to contribute.  libgo might
> be a bit different, because the source is maintained in golang, and then
> imported into GCC.

The absolute best way to contribute to the libgo and gcc/go/gofrontend
directories is to use Gerrit, following the process described at
https://golang.org/doc/contribute.html.

But sending patches to gcc-patc...@gcc.gnu.org and CC'ing me is also
OK.  Yes, in general the patches have to apply to GCC trunk.

Thanks.

Ian

Bug#909941: Reverting your previous erlang upload until rabbitmq-server is fixed

[Thomas Goirand]

Dear Sergei,

The amount of work to package a new version of Rabbitmq-server is
non-trivial, there seems to be a lot of changes in the upstream code
organization. There's now a new rabbitmq-common package that is a
library for both the server and client. How should I name the library
package?

I know nothing about Erlang library packaging such as rabbitmq-common,
therefore, I'd very much appreciate your help doing it. Pointing at
example packages similar to that one would be very helpful, for example.

In the mean time, it'd be super nice of you if you could revert your
Erlang 21 upload until rabbitmq-server is fixed. Or is that too much
work to do also?

Also, (keep in mind I don't know much about Erlang, but did you think
about packaging multiple versions of Erlang in Debian, so we could
handle transitions better?

In anyways, can you say hello to me on IRC so we can discuss this?

Cheers,

Thomas Goirand (zigo)

Bug#910634: spice: FTBFS on all architectures

[Salvatore Bonaccorso]

Source: spice
Version: 0.14.0-1.1
Severity: serious
Justification: FTBFS everywhere

Hi

The NMU I uploaded as 0.14.0-1.1 FTBFS on *all* architectures. 

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

This was almost sure not the case when I prepared the NMU, at least
when building in my usual pbuilder envionment. Which possible change
or difference causes this?

Regards,
Salvatore

Bug#904289: libgo build failure with GCC trunk 20181004

[Matthias Klose]

On 08.10.2018 11:47, Svante Signell wrote:
> On Fri, 2018-10-05 at 21:10 +0200, Svante Signell wrote:
>> On Fri, 2018-10-05 at 01:38 +0200, Matthias Klose wrote:
>>> Hi Svante,
>>>
>>> please have a look at the recent libgo build failure with GCC trunk
>>> 20181004 after the libgo merge.  Please could you update the
>>> patches and send them upstream again?
>>
>> Well I don't really know where to submit the patches to upstream, but
>> here they are. Cc:ing the gcc-snapshot bug 904...@bugs.debian.org
>> too.
> 
> Hi again,
> 
> Seems like more changes were needed this time: Attached are three
> updated patches:
> src_libgo_go_syscall.diff
> add-gnu-to-libgo-headers.diff
> add-gnu-to-libgo-test-headers.diff

Thanks for the update, but please could you send *all* the patches to
gcc-patc...@gcc.gnu.org, and maybe CC Ian?  Patches really have to be ready to
be applied upstream, and not to some Debian package.

Please see https://gcc.gnu.org/contribute.html how to contribute.  libgo might
be a bit different, because the source is maintained in golang, and then
imported into GCC.

Matthias

Bug#910633: lists.debian.org: link to mail-archive.com and Wikipedia on Message-ID lookup failure

[Paul Wise]

Package: lists.debian.org
Severity: wishlist

On the page for Message-ID lookup failure:

Please add a link "The Mail Archive" to one of these two links. Note
the former does not offer https. The Mail Archive is archiving Debian
lists and has the unique feature of archiving the debian-bugs-dist
mailing list, which allows lookup of Debian BTS messages (#620467).

http://mid.mail-archive.com/msgid@example.org
https://www.mail-archive.com/search?l=mid=ms...@example.org

Please add a link "other services" or "other Message-ID lookup
services" to the Message-ID Wikipedia page, which includes a list of
links to Message-ID lookup services, including Debian's.

https://en.wikipedia.org/wiki/Message-ID

-- 
bye,
pabs

https://wiki.debian.org/PaulWise



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

Bug#907725: Fwd: Appropriate Section for PCF Fonts

[Paul Hardy]

Chris,

On Mon, Oct 8, 2018 at 9:41 AM Chris Lamb  wrote:
>
> Paul,
>
> > [..]
>
> Unfortunately I have very little insight or input to share on fonts or
> sections more generally in Debian so I will just have to leave this up
> to someone else. Apologies that I could not make progress here.

All's well that ends well.  I know now that the status quo is just
fine with my package.

> (I do somehow doubt a mass bug filing would be really appropriate or
> welcome, mind you.

I'm sure many facing the business end of a mass bug filing would find
displeasure with it. :-)  I expected that would be the least popular
option.  But IMHO I felt that if it was a bug, there should be a bug
filing against my package, and if it was not a bug, then the lintian
message should probably be removed.

> Did you consider "fixing" Lintian instead?)

Indeed I did, but I was not sure how to approach the issue properly,
so I posed the question on debian-policy thinking that might be the
best place to start[1].  I only received one response, which indicated
that section assignment was within the purview of the FTP Masters[2],
so then I followed up with an email to them.  In retrospect, I have
learned by seeing how Russ phrased this bug report.  Chalk one more up
for experience...

> Again, sorry I can't be of more help.

Actually, this bug that Russ filed is being resolved by taking two of
the actions that I asked about in the debian-policy mailing: the
lintian message will be removed, and "fonts" will be removed from the
web page description of the "x11" section, so that certainly helps.

Note, however, that there _are_ a few "xfonts-*" fonts in the "x11"
section.  If you and the rest of the FTP Team agrees, I suppose you
could change the lintian message to encourage those packages to set
their d/control section to "fonts".

Sorry I did not notice this bug until just before it was to be
archived.  I only saw it while searching to see if another bug had
been filed about something else in lintian (concerning
"wrong-path-for-interpreter" with the relaxed 4.2.1 policy), and in
fact that bug was already filed by someone else and already closed
(#908350).

Thank you for your detailed responses,


Paul Hardy

[1] https://lists.debian.org/debian-policy/2018/06/msg00098.html
[2] https://lists.debian.org/debian-policy/2018/06/msg00099.html

Bug#910632: iso-codes: ISO 3166-2 is out of date (specifically missing 2017-11-23 changes to CN)

[Julian Calaby]

Package: iso-codes
Version: 4.1-1
Severity: normal

Dear Maintainer,

The ISO 3166-2 data provided in this package appears to be missing changes from
2017.

Specifically the short codes for CN are listed as numbers instead of Alpha2
codes (i.e. CN-11 or CN-21 instead of CN-BJ or CN-LN)

It's possible that regions of other countries are also affected.

This was implemented in ISO 3166-2 on 2017-11-23 and appears to have been part
of the SAC 2007 changes.

See https://en.wikipedia.org/wiki/ISO_3166-2:CN
or https://www.iso.org/obp/ui/#iso:code:3166:CN

I must point out that this is not causing me any specific problems with any
particular Debian package, however this package's data has become an
authoritative source for a downstream package that I'm using.

Thanks,

Julian Calaby


-- 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/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

iso-codes depends on no packages.

iso-codes recommends no packages.

Versions of packages iso-codes suggests:
pn  isoquery  

-- no debconf information

Bug#910561: debian-policy does not recommend last version of libjs-sphinxdoc

[Sean Whitton]

control: tag -1 -wontfix +pending
control: reopen -1

Hello,

On Mon 08 Oct 2018 at 09:06AM +0200, Francois Mescam wrote:

> Upgrade of libjs-sphinxdoc to version 1.7.9-1 is blocked by debian-policy 
> which
> recommends libjs-sphinxdoc  1.7.8-1.
>
> Please solve this issue because many packages depend on libjs-sphinxdoc.

Ah, I'm sorry, I realised just as I was sending my previous message that
you meant upgrading the package on your own system, not upgrading the
version in Debian.

This will get fixed when we do another upload -- I am not at a machine
where I can do that right now, so marking as pending.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#806535: vim-common: Please add Multi-Arch: foreign

[James McCoy]

On Sun, Oct 07, 2018 at 12:13:45PM +0200, Elrond wrote:
> the exact same that applied to vim-runtime now applies
> also to vim-common.
> 
> Please add Multi-Arch: foreign to vim-common too.

Please don't completely repurpose old bugs.  If there's something new to
fix, the open a new bug.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB

Bug#910582: libpam-heimdal: libpam-heimdal updates PAM config with pam_krb5

[Russ Allbery]

Dave Love  writes:

> Installing libpam-heimdal updates the PAM config to use pam_krb5, not
> pam_heimdal, which obviously breaks badly:

The PAM module is named pam_krb5.so in both libpam-heimdal and
libpam-krb5.  The two packages are just built against different Kerberos
libraries.  So, this is expected; could you provide some more information
about what broke?  (Error messages, etc.)

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

Bug#910074: linux-image-4.9.0-8-amd64: BTRFS data loss - kernel BUG at .../linux-4.9.110/fs/btrfs/ctree.c:3178

[Nicholas D Steeves]

On Wed, Oct 03, 2018 at 09:56:13AM +, Michael Firth wrote:
> > 
> > As far as I know, if 'btrfs check' is clean then you're in the clear for 
> > any known
> > issues involving the fs structure.  Of course, a 'btrfs scrub' is necessary 
> > to
> > check for data and metadata corruption...  BTW, if you're using an ssd, make
> > sure you're mounting with -o nossd, because as far as I know linux-4.9.x 
> > still
> > hasn't been patched.
> > P.S. that requires a full rebalance to take effect.  Make up-to-date backups
> > before running that rebalance...
> 
> That is good to know. I will run a "scrub" on the partition soon to check for 
> any
> other issues. I am running on a VM on top of a hardware RAID array of
> spinning disks, so hopefully the SSD issue doesn't apply.

To find out:

  cat /sys/block/your_hardware_raid_block_device/queue/rotational

If it returns "0" then you're affected by the -o ssd bug, but if it
returns "1" then there is nothing to worry about. :-)  While this
issue will become obsolete when the fix is backported I'm curious to
learn if hardware RAID registers as nonrotational, so please let me
know.  I suspect it will register as nonrotational, because then the
kernel will let the RAID controller merge and reorder IO as it sees
fit.

> 
> There was a BTRFS patch in the update that became available an hour after my
> crash:
> 
> linux (4.9.110-3+deb9u5) stretch-security; urgency=high
> .
> .
> .
>   * btrfs: relocation: Only remove reloc rb_trees if reloc control has been
> initialized (CVE-2018-14609)
> 
> I'm not sure if that is a Debian specific patch or whether it is a Debian 
> specific 
> merge from another version

Oh Nice!  I'm really happy to see this.  Thank you Ben and kernel team!

> > I wasn't able to find status of the second one wrt linux-4.9.x.
> 
> Though the description is similar, I don't think patch 972419 is actually 
> either of
> the two patches referenced from that mail. I think I will ask on the BTRFS 
> mailing
> list what the current status of all of these patches is.

Thanks.

> > In principle I agree; although I think it would be safer to coordinate with 
> > Greg
> > Kroah-Harman about getting them applied upstream before importing them
> > into Debian, since (afaik) we don't have any btrfs specialists working on 
> > our
> > kernel...people who would know if importing one of these patches will
> > introduce unintended side-effects or a rabbit hole of patches.  Maybe it
> > would be safer to look at the delta between btrfs in 4.9.x and 4.14.x and 
> > ask
> > for backported fixes from 4.14.x to 4.9.x? (eg: more than six months of
> > testing in 4.14.x, like the -o ssd bug that is still present in 4.9.x)
> > 
> I agree with this, and with Hans's comment that because it isn't a Debian 
> specific
> issue it should be handled upstream. I guess the question comes partly from 
> not
> knowing if/how/when upstream V4.9.X kernel changes are merged into the Debian
> Stretch kernel.

The version number is a hint.  Looking at the changelog for the
package, you'll see stretch released with 4.9.30-2, was updated with
security fixes in 4.9.30-2+deb9u1, was updated from upstream LTS in
4.9.47-1, etc, and is now at 4.9.110-3+deb9u6.


Cheers,
Nicholas

Bug#910631: lightdm: first login hangs waiting for user-generated entropy

[Jules Bernable]

Package: lightdm
Version: 1.26.0-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

On my buster/sid system, LightDM hangs indefinitely on first login until
entropy is generated via mouse or keyboard input.
The login process seems to be delayed by the kernel itself, until the following
lines appear in journalctl:

kernel: random: crng init done
kernel: random: 7 urandom warning(s) missed due to ratelimiting

Installing the haveged package fixes the issue, as mentioned in the following
thread:
https://unix.stackexchange.com/questions/442698/when-i-log-in-it-hangs-until-
crng-init-done

This issue also seems related to bug #897572



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

Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /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:
pn  accountsservice  
ii  upower   0.99.8-2
pn  xserver-xephyr   

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

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

Bug#910074: linux-image-4.9.0-8-amd64: BTRFS data loss - kernel BUG at .../linux-4.9.110/fs/btrfs/ctree.c:3178

[Nicholas D Steeves]

Hi Hans,

On Wed, Oct 03, 2018 at 12:05:31AM +0200, Hans van Kranenburg wrote:
> Hi,
> 
> On 10/02/2018 10:08 PM, Nicholas D Steeves wrote:
> > Hi Michael,
> > 
> > On Tue, Oct 02, 2018 at 11:37:45AM +0100, Michael Firth wrote:
> >>
> >> BTRFS may not be a filesystem that everyone uses, but I feel if it is in
> >> the Debian kernel then bugs that can cause data loss should be fixed if
> >> a patch already exists.
> > 
> > In principle I agree; although I think it would be safer to coordinate
> > with Greg Kroah-Harman about getting them applied upstream before
> > importing them into Debian, since (afaik)
> 
> > we don't have any btrfs
> > specialists working on our kernel...people who would know if importing
> > one of these patches will introduce unintended side-effects or a
> > rabbit hole of patches.
> 
> This is not a debian specific issue. The upstream btrfs team does not
> have enough work capacity to do this, and mainly focuses on going
> forward instead of looking back. And I don't think there's really
> someone who would know the things mentioned above except for the authors
> of the patches themselves (who tag them for stable if it's data
> corruption and if they know it will work (tm)), or the btrfs maintainer
> who knows which ones to put together in which order to prepare the next
> kernel release.

Agreed!  Also, acknowledging when issues aren't Debian-specific and
then working with upstream so everyone can benefit is one reason we
have a great reputation for giving back to the larger community :-)

> 
> >  Maybe it would be safer to look at the delta
> > between btrfs in 4.9.x and 4.14.x and ask for backported fixes from
> > 4.14.x to 4.9.x? (eg: more than six months of testing in 4.14.x, like
> > the -o ssd bug that is still present in 4.9.x)
> 
> For the -o ssd issue, in hindsight, it was a mistake to not get that
> into 4.9 earlier.
> 
> Every user who wants to try out btrfs on his/her computer with Stretch
> and uses it as the root filesystem on a disk which is not too large is
> still affected by this sub-optimal behaviour.
> 
> So I guess that's a TODO for me, to still get it done now. It's 951e7966
> and 583b723151 with a few small changes to make it apply. At least it
> has had enough testing, and the amount of users with out-of-space
> filesystems has decreased notably in the last year in #btrfs IRC. :)

Thank you!  I updated our wiki page within a week of learning about
the patch, but in the future would you prefer if I file a bug?  I
don't imagine it will be more than two bugs a year ;-)  Btw, would you
please forward the bug to me for the 951e7966 and 583b723151 backport?

Sincerely,
Nicholas


signature.asc
Description: PGP signature

Bug#908192: Acknowledgement (linux-image-4.18.0-1-amd64: After upgrade kernel to linux-image-4.18.0-1-amd64, LXC can not start)

[Christian Brauner]

On Sat, 22 Sep 2018 21:20:19 +0200 Salvatore Bonaccorso
 wrote:
> Hi,
>
> On Thu, Sep 20, 2018 at 06:09:07PM +0800, johnw wrote:
> >
> > Is it also reverted/back port to Debian?
> > Because I still have this problem.
>
> it has not yet been reverted upstream, the discussion got stuck here:

Hey, I'm one of the ACKers of the original patch and the author
of the revert. The kernel patch that broke userspace won't be reverted upstream.
However, I'm also a LXC maintainer and I have fixed LXC upstream to handle
4.18 kernels. The relevant commits are:

master:
https://github.com/lxc/lxc/commit/3e04a6083eefe0b837db6d1b826721fd985ce052
https://github.com/lxc/lxc/commit/5067e4dd8594c3b1f8ee78f0e86edb480f84a156

stable-3.0:
https://github.com/lxc/lxc/commit/c221e3780a59ac08cd7e8758f7d71422f0c4decf

I haven't done a backport of this to stable-2.0 yet. So far there weren't
any complains for that one.

Christian

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

[Andreas Beckmann]

On 2018-10-08 22:46, Adrian Bunk wrote:
> Why is it using a 3 weeks old version of libepoxy-dev?

I thought I had rerun the spurious looking test on the weekend, but
somehow the old logfile was still there ...


Andreas

Bug#874727: closed by Anton Gladky (Bug#874727: fixed in coin3 3.1.4~abc9f50+dfsg2-1)

[mlampert]

I've attached an xml tool table.

* start FreeCAD from the command line
* Create a new document
* switch to "Path" Workbench
* start "Path Manager" from the Path menu
* import attached tooltable (note the file type selection)

You'll get:
Program received signal SIGSEGV, Segmentation fault.
#0  /lib/x86_64-linux-gnu/libc.so.6(+0x35fc0) [0x7f75fc00ffc0]
#1  /lib/x86_64-linux-gnu/libexpat.so.1(XML_SetHashSalt+0x1b) [0x7f75f584095b]
#2  /usr/lib/python2.7/lib-dynload/pyexpat.x86_64-linux-gnu.so(+0x75b0) 
[0x7f75c08145b0]
#3  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x94d6) 
[0x7f7602316c66]
#4  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x8e5f) 
[0x7f76023165ef]
#5  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x8e5f) 
[0x7f76023165ef]
#6  /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x732) 
[0x7f760230d032]


I don't think the file itself matters at all because it segfaults while trying 
to initialise libexpat, but in case the attachment gets filtered, this is the 
content:























On Fri, 5 Oct 2018 10:03:26 +0200
Christoph Berg  wrote:

> Re: markus 2018-10-05 <20181004193807.40af399c@yolanda>
> > it's a packaging bug - libcoin is statically linked with libexpat,
> > and the version being used is outdated. So anything that uses
> > libcoin and libexpat will run into a segfault.
> > 
> > I am not aware of any other application that uses libcoin.  
> 
> I noticed because PostGIS is affected via postgis B-D -> libsfcgal-dev
> -> libsfcgal-osg1 -> libopenscenegraph100v5 -> libcoin80v5. Looking
> at https://udd.debian.org/cgi-bin/autoremovals.cgi there's quite a few
> packages depending on coin3. So the question whether this affects
> freecad only or more packages is making quite a difference.
> 
> Do you have a recipe on how to reproduce the bug with freecad from
> experimental?
> 
> Christoph



tt.xml
Description: XML document

Bug#910630: varnish-modules depends on cruft package libvarnishapi1

[peter green]

package: varnish-modules
version: 0.12.1-1+b1
severity: serious
x-debbugs-cc: team+varnish-t...@tracker.debian.org

varnish-modules depends on libvarnishapi1 which is no longer built by varnish, 
it seems to have been replaced by libvarnishapi2

There does not seem to have been any attempt to re-build the package in Debian proper for 
this transition, however when we tried to rebuild it in raspbian the build failed. 
http://buildd.raspbian.org/status/fetch.php?pkg=varnish-modules=armhf=0.12.1-1%2Bb1=1539021262

Note: I placed the x-debbugs-cc because varnish-modules has a dead maintainer address and 
the "name" parts of the maintainer field are the same between varnish and 
varnish-modules.

Bug#892998: libnm/client: proxy *_enabled and metered properties to the wrong object make application using it crashing

[Michael Biebl]

Hi Fabio

On Thu, 15 Mar 2018 12:22:40 +0100 Fabio Fantoni
 wrote:
> Package: network-manager
> Version: 1.6.2-3
> Severity: important
> Tags: stretch
> 
> Trying Cinnamon next version (with switch to libnm) on Stretch was find that 
> it crash for this "small" upstream fix missed:
> libnm/client: proxy *_enabled and metered properties to the right object - 
> https://github.com/NetworkManager/NetworkManager/commit/c81005b84650b8e6d709ce6afda96fb55987cdb8
> Actually I'm not know other Stretch application using libnm that have/risk 
> this issue
> Other details here: https://github.com/linuxmint/Cinnamon/pull/6993
> This is for example already applied to Fedora 26 without issue FWIK: 
> https://src.fedoraproject.org/cgit/rpms/NetworkManager.git/commit/?h=f26=58e92b645a0d0b8f0b1e04116d76752e8d780bbd
> I reported this because is a important bug using libnm and can be fixed with 
> a small patch, in case there was any possibility of a new build 
> (1.6.2-3+deb9u1).
> Thanks for any reply and sorry for my bad english.

This is now waiting for an ack by the release team, see #910628

-- 
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#896818: libnma over GI not working

[Michael Biebl]

Hi Fabio

On Tue, 24 Apr 2018 16:32:10 +0200 Fabio Fantoni
 wrote:
> Package: network-manager-applet
> Version: 1.4.4-1
> Severity: important
> Tags: stretch
> 
> Trying to use libnma over GI from a python script is not working at all and 
> can also cause crash of other software using it.
> This patch solved it:
> https://git.gnome.org/browse/network-manager-applet/commit/?id=7a59d41e5fd0da51f1f7aae7518befdb1182
> I reported this because is a important bug using libnma and can be fixed with 
> a small patch, in case there was any possibility of a new build 
> (1.4.4-1+deb9u1).
> Thanks for any reply and sorry for my bad english.

This is now waiting for an ack by the release team, see #910629

Thanks for the patch at [1] even if I ended up not using it directly.
You really need to patch Makefile.am, not Makefile.in (as we run
autoreconf during build)

Regards,
Michael


[1]
https://salsa.debian.org/fantu-guest/network-manager-applet/commit/fd9033131b6e82e97d64cce9a640043e7742b167
-- 
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#910629: stretch-pu: package network-manager-applet/1.4.4-1+deb9u1

[Michael Biebl]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Hi,

I'd like to make stable upload for network-manager-applet fixing the
GObject-Introspection bindings for libnma.

While we don't have any software in stretch which uses those bindings,
there are 3rd party packages and downstream distros like Linux Mint
which want to make use of those bindings e.g. in Cinnamon. (See also the
related #910628).

The package is a cherry-pick/backport from upstream master and already
part of buster/sid.

Full debdiff is attached.

Thanks for considering,
Michael


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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/debian/changelog b/debian/changelog
index ad533660..985df157 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,14 @@
+network-manager-applet (1.4.4-1+deb9u1) stretch; urgency=medium
+
+  * libnma/pygobject: libnma/NMA must use libnm/NM instead of legacy
+libraries.
+libnma uses libnm, and not libnm-util/libnm-glib. Hence, the python
+bindings must load "NM" and not "NMClient"/"NetworkManager". As it was,
+the generated bindings for libnma were unusable and loading them
+would fail. (Closes: #896818)
+
+ -- Michael Biebl   Tue, 09 Oct 2018 00:59:55 +0200
+
 network-manager-applet (1.4.4-1) unstable; urgency=medium
 
   * New upstream release.
diff --git a/debian/gbp.conf b/debian/gbp.conf
index 478d845c..55b2a3d6 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,4 +1,4 @@
 [DEFAULT]
 pristine-tar = True
 patch-numbers = False
-debian-branch = master
+debian-branch = stretch
diff --git 
a/debian/patches/libnma-pygobject-libnma-NMA-must-use-libnm-NM-instead-of-.patch
 
b/debian/patches/libnma-pygobject-libnma-NMA-must-use-libnm-NM-instead-of-.patch
new file mode 100644
index ..55736529
--- /dev/null
+++ 
b/debian/patches/libnma-pygobject-libnma-NMA-must-use-libnm-NM-instead-of-.patch
@@ -0,0 +1,34 @@
+From: Thomas Haller 
+Date: Tue, 7 Mar 2017 09:43:03 +0100
+Subject: libnma/pygobject: libnma/NMA must use libnm/NM instead of legacy
+ libraries
+
+libnma uses libnm, and not libnm-util/libnm-glib. Hence, the python bindings
+must load "NM" and not "NMClient"/"NetworkManager".
+
+As it was, the generated bindings for libnma were unusable and loading
+them would fail with
+
+libnm-ERROR **: libnm-util symbols detected; Mixing libnm with 
libnm-util/libnm-glib is not supported
+
+https://bugzilla.gnome.org/show_bug.cgi?id=779153
+
+Fixes: 76a12beac4e8692f30071169e11e2b521ec4eab7
+(cherry picked from commit 7a59d41e5fd0da51f1f7aae7518befdb1182)
+---
+ src/libnma/Makefile.am | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/libnma/Makefile.am b/src/libnma/Makefile.am
+index b861db6..950b9fc 100644
+--- a/src/libnma/Makefile.am
 b/src/libnma/Makefile.am
+@@ -66,7 +66,7 @@ if HAVE_INTROSPECTION
+ introspection_sources = $(libnma_HEADERS) $(libnma_la_SOURCES)
+ 
+ NMA-1.0.gir: libnma.la
+-NMA_1_0_gir_INCLUDES = NMClient-1.0 NetworkManager-1.0 Gtk-3.0
++NMA_1_0_gir_INCLUDES = NM-1.0 Gtk-3.0
+ NMA_1_0_gir_EXPORT_PACKAGES = libnma
+ NMA_1_0_gir_CFLAGS = $(libnma_la_CFLAGS)
+ NMA_1_0_gir_LIBS = libnma.la
diff --git a/debian/patches/series b/debian/patches/series
index baed4ac7..72821c91 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 Allow-to-create-connections-without-admin-privileges.patch
 Force-online-state-with-unmanaged-devices.patch
+libnma-pygobject-libnma-NMA-must-use-libnm-NM-instead-of-.patch

Bug#890606: Patch for kopete 18.04.2-1 in experimental

[Felix Lechner]

 > However the patched source does not build against the old versions
> anymore. Can this be fixed? Otherwise we cannot do the transition with a
> binNMU.

Bernhard,

Please try the attached patch. It builds here both with the old and the new
libraries. I also sent it upstream. Thank you!

Best regards,
Felix


fix-mediastreamer-ftbfs.patch.xz
Description: application/xz

Bug#910628: stretch-pu: package network-manager/1.6.2-3+deb9u1

[Michael Biebl]

Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Hi,

I'd like to make a stable upload for network-manager, fixing a bug in
libnm0 when trying to access enabled and metered properties.

This fix was specifically requested by downstreams like Linux Mint which
use that functionality in their Cinnamon desktop.

The patch is cherry-picked from upstream and already fixed in
buster/sid.

Thanks for considering,
Michael

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff --git a/debian/changelog b/debian/changelog
index e93e0910e..ebb876f17 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+network-manager (1.6.2-3+deb9u1) stretch; urgency=medium
+
+  * libnm: Fix accessing enabled and metered properties.
+Those properties were proxied to the wrong object leading to a crash of
+clients using libnm. (Closes: #892998)
+
+ -- Michael Biebl   Tue, 09 Oct 2018 00:40:45 +0200
+
 network-manager (1.6.2-3) unstable; urgency=medium
 
   * device/wifi: block autoconnect while scanning is in progress.
diff --git a/debian/gbp.conf b/debian/gbp.conf
index 478d845ce..55b2a3d65 100644
--- a/debian/gbp.conf
+++ b/debian/gbp.conf
@@ -1,4 +1,4 @@
 [DEFAULT]
 pristine-tar = True
 patch-numbers = False
-debian-branch = master
+debian-branch = stretch
diff --git 
a/debian/patches/libnm-client-proxy-_enabled-and-metered-properties-to-the.patch
 
b/debian/patches/libnm-client-proxy-_enabled-and-metered-properties-to-the.patch
new file mode 100644
index 0..5287b860f
--- /dev/null
+++ 
b/debian/patches/libnm-client-proxy-_enabled-and-metered-properties-to-the.patch
@@ -0,0 +1,54 @@
+From: Lubomir Rintel 
+Date: Wed, 1 Nov 2017 21:29:39 +0100
+Subject: libnm/client: proxy *_enabled and metered properties to the right
+ object
+
+They're provided by the Manager, not by the RemoteSettings.
+
+(cherry picked from commit c81005b84650b8e6d709ce6afda96fb55987cdb8)
+(cherry picked from commit 34035ceee8e75d8cb7deb6f4aa211067bddcfe97)
+(cherry picked from commit b2af5f7ab676675a496adfa08541ecca43a9d9f8)
+---
+ libnm/nm-client.c | 8 
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/libnm/nm-client.c b/libnm/nm-client.c
+index 63eaa84..ba13347 100644
+--- a/libnm/nm-client.c
 b/libnm/nm-client.c
+@@ -2616,7 +2616,7 @@ get_property (GObject *object, guint prop_id,
+   break;
+   case PROP_WIRELESS_HARDWARE_ENABLED:
+   if (priv->manager)
+-  g_object_get_property (G_OBJECT (priv->settings), 
pspec->name, value);
++  g_object_get_property (G_OBJECT (priv->manager), 
pspec->name, value);
+   else
+   g_value_set_boolean (value, FALSE);
+   break;
+@@ -2625,7 +2625,7 @@ get_property (GObject *object, guint prop_id,
+   break;
+   case PROP_WWAN_HARDWARE_ENABLED:
+   if (priv->manager)
+-  g_object_get_property (G_OBJECT (priv->settings), 
pspec->name, value);
++  g_object_get_property (G_OBJECT (priv->manager), 
pspec->name, value);
+   else
+   g_value_set_boolean (value, FALSE);
+   break;
+@@ -2634,7 +2634,7 @@ get_property (GObject *object, guint prop_id,
+   break;
+   case PROP_WIMAX_HARDWARE_ENABLED:
+   if (priv->manager)
+-  g_object_get_property (G_OBJECT (priv->settings), 
pspec->name, value);
++  g_object_get_property (G_OBJECT (priv->manager), 
pspec->name, value);
+   else
+   g_value_set_boolean (value, FALSE);
+   break;
+@@ -2655,7 +2655,7 @@ get_property (GObject *object, guint prop_id,
+   break;
+   case PROP_METERED:
+   if (priv->manager)
+-  g_object_get_property (G_OBJECT (priv->settings), 
pspec->name, value);
++  g_object_get_property (G_OBJECT (priv->manager), 
pspec->name, value);
+   else
+   g_value_set_uint (value, NM_METERED_UNKNOWN);
+   break;
diff --git a/debian/patches/series b/debian/patches/series
index 7df065a43..e5e2cccd9 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -20,3 +20,4 @@ 
wifi-also-show-the-NM-D-Bus-path-for-the-Wi-Fi-AP-in-nm_w.patch
 device-separately-handle-NMDevice-s-autoconnect-by-user-a.patch
 device-add-get_autoconnect_allowed-virtual-function.patch
 device-wifi-block-autoconnect-while-scanning-is-in-progre.patch

Bug#910627: xul-ext-nostalgy: Please update to upstream 0.2.36 to be compatible with TB 60+

[Daniel Reichelt]

Package: xul-ext-nostalgy
Version: 0.2.34-1
Severity: important

Hi,

please update to the latest version available at [1] so it can be used again
with the version of Thunderbird (60+) shipped in Stretch.

Thanks!
Daniel

[1] https://addons.thunderbird.net/en-US/thunderbird/addon/nostalgy/

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

[Axel Beckert]

Hi Benda,

Benda Xu wrote:
> Thank you for raising this up.  Are you using openrc with sysvinit-core?

As mentioned: yes

> @Axel, what is the output of `rc-update` of the said system?

2ping |  default
   alsa-utils |  sysinit
  anacron |  default
 apparmor |  sysinit
 avahi-daemon |  default
 bootlogd |  sysinit
 console-setup.sh |  default
 cpufrequtils |  default
 cron |  default
   cryptdisks |  sysinit
 cryptdisks-early |  sysinit
 dbus |  default
  dnssec-triggerd |  default
  gpm |  default
   hwclock.sh |  sysinit
  iodined |  default
keyboard-setup.sh |  sysinit
 kmod |  sysinit
linuxlogo |  default
  loadcpufreq |  default
 lvm2 |  sysinit
 lvm2-lvmetad |  default
lvm2-lvmpolld |  default
   miredo |  default
   nethack-common |  default
   networking |  sysinit
   ntpsec |  default
  nvi |  default
  openvpn |  default
  postfix |  default
 pppd-dns |  sysinit
   procps |  sysinit
rsync |  default
  rsyslog |  default
savecache |off  
   screen-cleanup |  sysinit
smartmontools |  default
  ssh |  default
 sshguard |  default
stop-bootlogd |  default
 stop-bootlogd-single |  sysinit
  tor |  default
 udev |  sysinit
  unbound |  default
  uptimed |  default
  wdm |  default
 wicd |  default
   x11-common |  sysinit

There's especially no mountall.sh or similar listed.

On one of my older OpenRC ruunning systems, there are quite some
"mount" items listed:

[…]
 mountall-bootclean.sh |  sysinit
  mountall.sh |  sysinit
 mountdevsubfs.sh |  sysinit
   mountkernfs.sh |  sysinit
 mountnfs-bootclean.sh |  sysinit
  mountnfs.sh |  sysinit
[…]

Both machines are running Unstable and have sysvinit-core and e.g.
initscripts at version 2.88dsf-59.10, but the newly installed one is
amd64 with UEFI while the old one is i386 with classic BIOS. Not sure
if that should make a difference.

> /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?

Yes. And then even swap is activated:

# 

Bug#906848: [Pkg-mozext-maintainers] Bug#906848: Bug#906848: xul-ext-adblock-plus-element-hiding-helper no longer works with firefox-esr 60

[David Prévot]

Hi,

Le 08/10/2018 à 11:29, David Prévot a écrit :

> Le 08/10/2018 à 11:05, Moritz Mühlenhoff a écrit :
>> On Tue, Aug 21, 2018 at 08:54:05PM +0300, Adrian Bunk wrote:
>>> Package: xul-ext-adblock-plus-element-hiding-helper

Ooops.

>> Seems dead upstream, no update in 1.5 years, let's remove?`
> 
> Upstream seems very much alive

Apologies, I missed the “-element-hiding-helper” part. Doesn’t seem
available for current Firefox, so no objection for removal on my part.

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#873501: kivy FTBFS with Cython 0.26

[Dean Serenevy]

I'm sorry for the delay - I missed or didn't get your reply and just saw it 
this morning - I should have checked the bug report sooner!

Shashank Kumar wrote:
> I tried applying the patch on
> https://salsa.debian.org/python-team/modules/kivy.git but it's not working.
> Could you please specify the steps you took in order to get to the solution?

I've created a git repo from the latest on salsa with my changes:

   https://github.com/duelafn/deb-kivy-873501

Built / tested in docker via:

 docker run -it debian:buster
 cd
 apt-get update
 apt-get install git dpkg-dev pristine-tar
 git clone https://github.com/duelafn/deb-kivy-873501 kivy
 cd kivy
 dpkg-checkbuilddeps
 apt-get install cython3 debhelper dh-python libgl1-mesa-dev libgles2-mesa-dev 
libgstreamer1.0-dev libsdl2-dev libsdl2-image-dev libsdl2-mixer-dev 
libsdl2-ttf-dev pkg-config python3-all-dev
 pristine-tar checkout ../kivy_1.10.1.orig.tar.gz
 dpkg-buildpackage -rfakeroot --unsigned-changes --unsigned-source --post-clean 
--diff-ignore


Note: Also builds in stretch as long as you have debhelper from backports 
installed.



signature.asc
Description: OpenPGP digital signature

Bug#910594: lintian: complain about missing versioned dependency on init-system-helpers

[Stuart Prescott]

Hi Chris,

> > Over in #910593, I reported that the maintainer script was using a feature
> > of update-rc.d that is not available in stretch.
> 
> Yes, this is something that Lintian could indeed spot.
> 
> > One could also look for the dh_installinit call in debian/rules […]
> 
> Not quite sure what you mean by this bit?

The offending postinst would almost always be created by 

override_dh_installinit:
dh_installinit -u defaults-disabled

So in principle, lintian could look for that call from d/rules rather than the 
update-rc.d call in the postinst. I'm not sure what the relative abilities of 
lintian's d/rules and postinst checkers are, and whether that is a useful 
snippet of information.

Cheers
Stuart

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Bug#910626: exfalso: not all required libraries are installed

[Álvaro Herrera]

Package: exfalso
Version: 3.7.1-2
Severity: important

Dear Maintainer,

I ran 'apt install exfalso' and tried to run it, but it fails:

Traceback (most recent call last):
  File "/usr/bin/exfalso", line 74, in 
main(util.argv)
  File "/usr/bin/exfalso", line 63, in main
session.init("exfalso")
  File "/usr/lib/python2.7/dist-packages/quodlibet/qltk/session.py", line 29,
in init
client = bus.get_object("org.gnome.SessionManager", client_path)
  File "/usr/lib/python2.7/dist-packages/dbus/bus.py", line 241, in get_object
follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 244, in
__init__
_dbus_bindings.validate_object_path(object_path)
TypeError: validate_object_path() argument 1 must be string, not None


I suppose this means I'm missing a packaged library, but I don't know which one
it is.

I expected that exfalso would be able to run out-of-the-box after installing.
I tried
installing package quodlibet, but that didn't fix the problem.



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

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

Versions of packages exfalso depends on:
ii  gir1.2-gtk-3.0   3.22.11-1
ii  gir1.2-soup-2.4  2.56.0-2+deb9u2
ii  libjs-sphinxdoc  1.4.9-2
ii  python   2.7.13-2
ii  python-gi3.22.0-2
ii  python-gi-cairo  3.22.0-2
ii  python-mutagen   1.36-1
ii  sphinx-rtd-theme-common  0.1.9-1

Versions of packages exfalso recommends:
ii  python-musicbrainzngs  0.6-2

Versions of packages exfalso suggests:
ii  brasero   3.12.1-4
ii  gir1.2-gstreamer-1.0  1.10.4-1
ii  libmodplug1   1:0.8.8.5-3
ii  xfburn0.5.4-1

-- no debconf information

Bug#906848: [Pkg-mozext-maintainers] Bug#906848: xul-ext-adblock-plus-element-hiding-helper no longer works with firefox-esr 60

[David Prévot]

Hi,

Le 08/10/2018 à 11:05, Moritz Mühlenhoff a écrit :
> On Tue, Aug 21, 2018 at 08:54:05PM +0300, Adrian Bunk wrote:
>> Package: xul-ext-adblock-plus-element-hiding-helper

> Seems dead upstream, no update in 1.5 years, let's remove?`

Upstream seems very much alive (last update of the WebExt addon less
than a month ago) : https://adblockplus.org/releases/

I can confirm that it works with current version of Firefox, it “just”
need someone to do the busy work of preparing the new package(s).

Regards

David



signature.asc
Description: OpenPGP digital signature

Bug#910612: (no subject)

[Frank McCormick]

Apparently not on my machine. I usually put symlinks into 
/home/Picturestoday when I changed the symlinks to point to 
another dorectory, it started looking for the pics in the old directory 
for several starts in a row.


I had to go into /home/frank/.cache and clean out the directory.

Running 5.40-1 according to Debian.

Bug#909288: transition: kdepim 18.08

[Sandro Knauß]

Hey Emilio,

I uploaded kmailtransport_18.08.1-2 that should build on more archs (as it 
makes libkgapi optional).

hefee

@pino sorry - I forgotten to pull before starting to work, so your updates are 
not included in the -2.

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

Bug#906876: xul-ext-scrapbook no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Tue, Aug 21, 2018 at 09:51:34PM +0300, Adrian Bunk wrote:
> Package: xul-ext-scrapbook
> Version: 1.5.13-3
> Severity: serious
> 
> XUL addons are no longer supported. 

Seems dead upstream, no release in over two years, let's remove?

Cheers,
Moritz

Bug#906848: xul-ext-adblock-plus-element-hiding-helper no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Tue, Aug 21, 2018 at 08:54:05PM +0300, Adrian Bunk wrote:
> Package: xul-ext-adblock-plus-element-hiding-helper
> Version: 1.3.8-1
> Severity: serious
> 
> XUL addons are no longer supported.
> 
> If it is confirmed that this package works with thunderbird 60,
> it might be an option to change the dependency to only thunderbird.

Seems dead upstream, no update in 1.5 years, let's remove?`

Cheers,
Moritz

Bug#908644: [Rsbackup-maint] Bug#908644: rsbackup: diff for NMU version 5.0-2.1

[Matthew Vernon]

On 08/10/18 21:38, Adrian Bunk wrote:

On Mon, Oct 08, 2018 at 08:53:57PM +0100, Matthew Vernon wrote:

Hi,


Hi Matthew,


On 27/09/18 19:09, Adrian Bunk wrote:


I've prepared an NMU for rsbackup (versioned as 5.0-2.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.


Thanks, but the right answer is to upload 5.1-1, which I will be doing
shortly.


fine for me, I've canceled my NMU.

Note that the fix does not look as if it would depend on the upstream
version, please check that the new package would not FTBFS again if a
different automake version (e.g. 1.15 from stable) is installed.


I build a stretch package for my own purposes :)

Regards,

Matthew

Bug#910625: netperf: log files are not rotated

[sergio]

Package: netperf
Version: 2.6.0-2.1
Severity: serious
Justification: Policy 10.8


Netperf creates unlimited number of /var/log/netserver.debug_PID files (really
about 65K limited).

Policy 10.8 says: "Log files must be rotated occasionally so that they don’t 
grow"

Moreover Policy 10.8 says: "log files should be named /var/log/netperf.log"


Moreover it's not possible to change log file name. Looks like it's
hard-coded. Related bug #904394.

Bug#910624: RM: openinbrowser -- RoQA; broken with Firefox ESR60

[Moritz Muehlenhoff]

Package: ftp.debian.org
Severity: normal

Hi,
please remove openinbrowser. It's broken with Firefox ESR60 and
has been orphaned since 2013. If there's any renewed interest,
https://github.com/Rob--W/open-in-browser can be packaged.

Cheers,
Moritz

Bug#910576: libreoffice-base: in my form, all entries are "input required"

[Rene Engelhard]

forwarded 910576 https://bugs.documentfoundation.org/show_bug.cgi?id=120245
tag 910576 + upstream
tag 910576 + fixed-upstream
thanks

Hi,

On Mon, Oct 08, 2018 at 11:04:37AM +0200, Martin Lutz wrote:
> since the last update of libreoffice-base, all entries in my form are
> suddenly "input required". When saving my changes I get the error message
> "Error writing to database. Input required in field 'fieldname'. Please enter 
> a
> value".
> 
> In the corresponding table, all fields are still on the status "input 
> required"
> --> no. Saving an entry with empty fields is not a problem, there.
> 
> The database is mysql which is running on a different computer.

This sounds like
https://bugs.documentfoundation.org/show_bug.cgi?id=120353 which is
marked as duplicate of
https://bugs.documentfoundation.org/show_bug.cgi?id=120245 which is
fixed in git for 6.1.3 (and 6.2.0).

Regards,

Rene

Bug#906854: xul-ext-firexpath no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Tue, Aug 21, 2018 at 09:00:13PM +0300, Adrian Bunk wrote:
> Package: xul-ext-firexpath
> Version: 0.9.7.1-3
> Severity: serious
> 
> XUL addons are no longer supported.

Seems dead upstream, let's remove?

Cheers,
Moritz

Bug#906860: xul-ext-mozvoikko no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Tue, Aug 28, 2018 at 10:08:51AM +0300, Timo Jyrinki wrote:
> Unfortunately upstream has removed the API that makes it possible to add
> external spellcheckers, and the upstream selected library for
> spellchecking is unable to properly support a language with a structure
> of Finnish.
> 
> Currently there is no other option than to live without spell-checking
> support in Mozilla products, and eg copy-paste to and back from a text
> editor for spell checking. Or use a full Voikko library compiled into
> Javascript with dependencies like at
> https://www.puimula.org/htp/testing/js-libvoikko/js-libvoikko-demo.html

Let's remove mozvoikko from the archive, then?

Cheers,
Moritz

Bug#906851: xul-ext-firegestures no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Tue, Aug 21, 2018 at 08:57:15PM +0300, Adrian Bunk wrote:
> Package: xul-ext-firegestures
> Version: 1.10.9-1
> Severity: serious
> 
> XUL addons are no longer supported.

Seems dead upstream, let's remove?

Cheers,
Moritz
 

Bug#908644: [Rsbackup-maint] Bug#908644: rsbackup: diff for NMU version 5.0-2.1

[Matthew Vernon]

Hi,

On 27/09/18 19:09, Adrian Bunk wrote:


I've prepared an NMU for rsbackup (versioned as 5.0-2.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.


Thanks, but the right answer is to upload 5.1-1, which I will be doing 
shortly.


Regards,

Matthew

Bug#908644: [Rsbackup-maint] Bug#908644: rsbackup: diff for NMU version 5.0-2.1

[Adrian Bunk]

On Mon, Oct 08, 2018 at 08:53:57PM +0100, Matthew Vernon wrote:
> Hi,

Hi Matthew,

> On 27/09/18 19:09, Adrian Bunk wrote:
> 
> > I've prepared an NMU for rsbackup (versioned as 5.0-2.1) and uploaded
> > it to DELAYED/14. Please feel free to tell me if I should cancel it.
> 
> Thanks, but the right answer is to upload 5.1-1, which I will be doing
> shortly.

fine for me, I've canceled my NMU.

Note that the fix does not look as if it would depend on the upstream 
version, please check that the new package would not FTBFS again if a
different automake version (e.g. 1.15 from stable) is installed.

> Regards,
> 
> Matthew

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#902186: CVE-2018-12689

[Moritz Mühlenhoff]

On Mon, Oct 08, 2018 at 08:55:35PM +0200, Dominik George wrote:
> Control: tags -1 + moreinfo
> Control: severity -1 important
> 
> Heisann,
> 
> On Sat, Jun 23, 2018 at 10:45:39AM +0200, Moritz Muehlenhoff wrote:
> > Package: phpldapadmin
> > Severity: grave
> > Tags: security
> > 
> > Please see
> > http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12689
> 
> I am triaging this bug report because of a request of a user to get
> phpLDAPAdmin into testing again, and the maintainer seems to be unresponsive.
> 
> Doing so, I found that in my opinion, the CVE is invalid. Neither of the PoC
> works.
> 
>  PoC 1 (server_id parameter) does not work because the parameter is verified
>  using is_numeric before being passed on to anything special.
> 
>  PoC 2 makes phpLDAPAdmin simply display "Invalid DN syntax for user".
> 
> No matter what, I was not able to get anything out of phpLDAPAdmin with the
> information in the CVE and the refereces exploit. Thus, I am lowering the
> priority of this bug report to important and asking you to provide more
> information on how to produce the behaviour claimed in the CVE report.

We're just filing these bugs as they come in from MITRE, I don't even
use phpldapadmin and most probably never will.

I suggest you report this upstream and if they agree that it's confirmed to
be a non-issue, ask for a rejection via https://cveform.mitre.org/.

Cheers,
Moritz

Bug#910595: Thunar segfaults when using Wayland and makes it unusable (still)

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Mon, 2018-10-08 at 22:04 +0200, Yvan Masson wrote:
> Thanks for you private e-mail with explanations: I thought that 1.8.2
> would fix this issue because the Thunar changelog [1] says on line 4:
> 
> "- Fixed segfault while clicking or typing when using wayland (Bug #14461)"
> 
> 1. https://git.xfce.org/xfce/thunar/tree/NEWS
> 
Random thought: after upgrading Thunar, the daemon needs to be restarted,
either by closing/restarting the whole Xfce session, or by using:

thunar -q
thunar --daemon
thunar

Check in About that you're actually running 1.8.2.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlu7usgACgkQ3rYcyPpX
RFtfAAf/eZ86VIwCfSR/oysgcQhAqtO3T/MEhjFKjLYg3D0102zegSew2E3vy7jZ
M0Csb0ekKVCt7Jm8wUy5atdCfgvjmUkPefsZ2Wl9+w2Ku6zZaZDmAiKr/qJEJecu
6asWQuKokWeyfo9h23E9H2+7pXp/I0EfNeu7DJpHDPTUAg9frwKpBCN7zjug128+
LUqhmlDXpkkOxcyBW2VlK2j5qNPFO40qboXpfcffgnTkcI38dZKQBJ1uo9OI8Njw
13jb8IpPILOtskU+sMDe4DX2fSOQ9EyNkk6IOQqoPscIsVjt2j69cJU9Th4k4nPe
0X6eTEsgPrGsePFr+/Vgsy+cp6ROOw==
=AKEr
-END PGP SIGNATURE-

Bug#910245: RFS: engauge-digitizer/10.10+ds.1-1

[Tobias Winchen]

Dear Herbert,

I executed cowbuilder 2x in a fresh virtual machine and could not reproduce 
this problem. Please let me know if I can do anything else.

Bests,


Tobi





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

Bug#910601: libreoffice-common: Sometimes X11 crash when opened.

[Rene Engelhard]

tag 910601 + moreinfo
tag 910601 + unreproducible
thanks

Hi,

On Mon, Oct 08, 2018 at 05:15:28PM +0200, Nicola wrote:
> Package: libreoffice-common
> Version: 1:6.1.2-1
> Severity: normal
> 
> Dear Maintainer,
> 
> Sometimes X11 crash.

If you do what? Specific action? Randomly? Why a LibreOffice bug?
Which graphic driver?

> [18266.049204] kauditd_printk_skb: 19 callbacks suppressed
> [18266.049204] audit: type=1400 audit(1539010923.604:47): apparmor="ALLOWED" 
> operation="open" profile="libreoffice-soffice" 
> name="/home/nicola/.cache/mesa_shader_cache/index" pid=6859 
> comm="soffice.bin" requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000
> [18266.142172] audit: type=1400 audit(1539010923.696:48): apparmor="ALLOWED" 
> operation="mknod" profile="libreoffice-soffice" 
> name="/usr/local/share/fonts/.uuid.TMP-1K2Yod" pid=6858 comm="soffice.bin" 
> requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
> [18266.142247] audit: type=1400 audit(1539010923.696:49): apparmor="ALLOWED" 
> operation="mknod" profile="libreoffice-soffice" 
> name="/usr/share/fonts/cMap/.uuid.TMP-J6rugr" pid=6858 comm="soffice.bin" 
> requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
> [18266.142809] audit: type=1400 audit(1539010923.696:50): apparmor="ALLOWED" 
> operation="mknod" profile="libreoffice-soffice" 
> name="/usr/share/fonts/X11/util/.uuid.TMP-iXd47E" pid=6858 comm="soffice.bin" 
> requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
> [18266.142811] audit: type=1400 audit(1539010923.696:51): apparmor="ALLOWED" 
> operation="mknod" profile="libreoffice-soffice" 
> name="/usr/share/poppler/cMap/Adobe-CNS1/.uuid.TMP-2ifEZS" pid=6858 
> comm="soffice.bin" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
> [18266.142880] audit: type=1400 audit(1539010923.696:52): apparmor="ALLOWED" 
> operation="mknod" profile="libreoffice-soffice" 
> name="/usr/share/poppler/cMap/Adobe-GB1/.uuid.TMP-mMpeR6" pid=6858 
> comm="soffice.bin" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
> [18266.142882] audit: type=1400 audit(1539010923.696:53): apparmor="ALLOWED" 
> operation="mknod" profile="libreoffice-soffice" 
> name="/usr/share/poppler/cMap/Adobe-Japan1/.uuid.TMP-JhNOIk" pid=6858 
> comm="soffice.bin" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
> [18266.142883] audit: type=1400 audit(1539010923.696:54): apparmor="ALLOWED" 
> operation="mknod" profile="libreoffice-soffice" 
> name="/usr/share/poppler/cMap/Adobe-Japan2/.uuid.TMP-XMkpAy" pid=6858 
> comm="soffice.bin" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
> [18266.142930] audit: type=1400 audit(1539010923.696:55): apparmor="ALLOWED" 
> operation="mknod" profile="libreoffice-soffice" 
> name="/usr/share/poppler/cMap/Adobe-Korea1/.uuid.TMP-IM6ZrM" pid=6858 
> comm="soffice.bin" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
> [18266.142931] audit: type=1400 audit(1539010923.696:56): apparmor="ALLOWED" 
> operation="mknod" profile="libreoffice-soffice" 
> name="/usr/share/fonts/opentype/ipafont-gothic/.uuid.TMP-1C3Aj0" pid=6858 
> comm="soffice.bin" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
> [18268.987056] nouveau :01:00.0: bus: MMIO read of  FAULT at 
> 619444 [ IBUS ]


... so you want to say that this has to do with apparmor? Don't believe
so, but the last entries definitely are fonts and for poppler, so are
you trying to open some PDF?

Sorry, as of now this bug report isn't anything one can act on. Not me,
and not upstream.

Regards,

Rene

Bug#910595: Thunar segfaults when using Wayland and makes it unusable (still)

[Yvan Masson]

Thanks for you private e-mail with explanations: I thought that 1.8.2
would fix this issue because the Thunar changelog [1] says on line 4:

"- Fixed segfault while clicking or typing when using wayland (Bug #14461)"

1. https://git.xfce.org/xfce/thunar/tree/NEWS

Regards,
Yvan



signature.asc
Description: OpenPGP digital signature

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

[Holger Levsen]

Hi Chris,

On Mon, Oct 08, 2018 at 08:15:59PM +0100, Chris Lamb wrote:
> > But I think we want to move something distro agnostic, and salsa.d.o
> > is very much Debian centric, so I think we should look for something
> > else. I'd be fine to using github.com or gitlab.com or foobar.
> Let's try and enumerate some of the potential options here so we aren't
> lost or confusing each other in paragraphs (or otherwise letting this go
> on for too long):

thanks, this seems useful! :)

before answering, some questions about these scenarios:

>  a) Some hybrid where we have the code remain on salsa yet mirror it on
> Github. Somewhat like the situation ~12 months ago.

where would we track the upstream issues in a.)?

>  b) Another frankenstein hybrid where we have the code remain on salsa
> & mirror on Github, but move issue tracking to salsa.
> 
>  c) Make salsa the canonical location, enable issues on it and use it
> for MRs. "Forward" issues upstream to salsa from the BTS.
> 
>  d) Make GitHub the canonical location and use it for PRs and issues.
> Remove diffoscope entirely from salsa & "forward" issues to GitHub
> from the BTS.
> 
>  e) Make GitLab the canonical location for both code and use it for MRs
> and issues. Remove diffoscope entirely from salsa and forward
> "issues" here from the BTS.

you mean a gitlab.com instance in e.)?

> I'm not *really* that fussed philosophically but as someone who has
> done a lot of the diffoscope coding over the past years I just want to
> remove as much day-to-day infrastructure overhead with respect to
> collating, collapsing, merging issues and suchforth.

nods, same here. plus I want it easy for new non-Debian contributors.
(Wish I'm sure you want too.)

> It is very easy to overloop what a big mental barrier and annoyance it
> is to have to do this extra work.

understood but what extra work exactly? of course we should automate
mirroring...


-- 
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#909941: [Pkg-erlang-devel] erlang 21.1+dfsg-1 causes rabbitmq-server to fail to start/install

[Paul Gevers]

Control: clone -1 -2
Control: reassign -2 rabbitmq-server 3.6.10-1
Control: reopen -2
Control: severity -2 grave
Control: retitle -2 rabbitmq-server needs update for current erlang

On Mon, 8 Oct 2018 07:37:25 +0300 Sergei Golovan  wrote:
> 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.

So, cloning and reassigning back. It seems rabbitmq-server needs an
update to work.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#910616: [Parl-devel] Bug#910616: parl-desktop-eu, parl-desktop-world: Should depend on hunspell-lv instead of myspell-lv

[Jonas Smedegaard]

control: tag -1 pending

Quoting Agustin Martin (2018-10-08 20:54:31)
> Yet another pending myspell->hunspell bug report.
> 
> myspell-lv is now a transitional package to hunspell-lv. While it has 
> recently being added (and it will be available in buster), it would be 
> nice to think about changing the dependency.

Thanks for reporting!

Already prepared.


> Note that hunspell-lv is not available in current stable (although it 
> is in sid and testng) so, if you consider a parl-desktop backport, 
> myspell-lv should better stay as "hunspell-lv | myspell-lv" or 
> something like that.
> 
> As said, this is not urgent, but something to think about.

Thanks for your consideration.

boxer-data, build tool for parl-desktop-eu and parl-desktop-world, 
tracks packages in testing, stable, oldstable, and oldoldstable.  
Backporting will therefore (when boxer-data is up-to-date) resolve to 
the appropriate packages of the target environment.


 - Jonas

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

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


signature.asc
Description: signature

Bug#910622: keystone: [INTL:de] Updated German debconf translation

[Chris Leick]

Package: keystone
Version: 2_14.0.0-2
Severity: wishlist
Tags: l10n patch


Hi,

please find attached the newest German deconf translation.

Kind regards,
Chris


de.po.gz
Description: application/gzip

Bug#910621: horizon: [INTL:de] Updated German debconf translation

[Chris Leick]

Package: horizon
Version: 3.14.0.0-3
Severity: wishlist
Tags: l10n patch


Hi,

please find attached the newest German deconf translation.

Kind regards,
Chris


de.po.gz
Description: application/gzip

Bug#910589: myspell-ca: should be in package section oldlibs

[Jonas Smedegaard]

Quoting Agustin Martin (2018-10-08 21:15:05)
> On Mon, Oct 08, 2018 at 08:43:07PM +0200, Jonas Smedegaard wrote:
> > Reassigning?  parl-desktop-world cannot make myspell-ca change 
> > section.

Re-reading above I sound like a jerk: What in my mind was a friendly 
suggestion ended in writing as a demand.  Sorry!

> myspell-ca is only there because of parl-desktop-world, there is no 
> point in changing its section. Problem will go as soon as fixed 
> parl-desktop-world is accepted. That is why I did things this way.
> 
> > File a separate bugreport about parl-desktop-world depending on a 
> > transitional package, and tag this bug as affected by the new one.
> 
> No problem. Doing things this other way. I'd prefer a block, but using 
> affects.

It should all go away very soon, yes.

The very reason I spotted this (or that - the originally filed) issue 
was in my process of systematically checking _all_ hunspell and myspell 
packages to update boxer-data (and through that parl-desktop-world).  
Sorry, I could have saved you a bit of investigation work by elaborating 
on what I thought was unimportant to you. :-/


 - Jonas

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

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


signature.asc
Description: signature

Bug#910617: [Parl-devel] Bug#910617: parl-desktop-world: Must depend on hunspell-ca instead of myspell-ca

[Jonas Smedegaard]

Control: tag -1 pending

Quoting Agustin Martin (2018-10-08 21:04:05)
> parl-desktop-world depends on transitional package myspell-ca. Current 
> hunspell-ca package in sid and testing no longer provides myspell-ca, 
> so dependency needs to be changed to hunspell-ca.

Thanks for reporting!

Fix already committed to git locally...

 - Jonas

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

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


signature.asc
Description: signature

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

[Chris Lamb]

Hi Holger,

> But I think we want to move something distro agnostic, and salsa.d.o
> is very much Debian centric, so I think we should look for something
> else. I'd be fine to using github.com or gitlab.com or foobar.

Let's try and enumerate some of the potential options here so we aren't
lost or confusing each other in paragraphs (or otherwise letting this go
on for too long):

 a) Some hybrid where we have the code remain on salsa yet mirror it on
Github. Somewhat like the situation ~12 months ago.

 b) Another frankenstein hybrid where we have the code remain on salsa
& mirror on Github, but move issue tracking to salsa.

 c) Make salsa the canonical location, enable issues on it and use it
for MRs. "Forward" issues upstream to salsa from the BTS.

 d) Make GitHub the canonical location and use it for PRs and issues.
Remove diffoscope entirely from salsa & "forward" issues to GitHub
from the BTS.

 e) Make GitLab the canonical location for both code and use it for MRs
and issues. Remove diffoscope entirely from salsa and forward
"issues" here from the BTS.

I'm not *really* that fussed philosophically but as someone who has
done a lot of the diffoscope coding over the past years I just want to
remove as much day-to-day infrastructure overhead with respect to
collating, collapsing, merging issues and suchforth.

It is very easy to overloop what a big mental barrier and annoyance it
is to have to do this extra work.

(... not to mention how OCD-triggering it is to have duplicates, etc.)


Regards,

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

Bug#910589: myspell-ca: should be in package section oldlibs

[Agustin Martin]

Control: reassign -1 myspell-ca
Control: retitle -1 myspell-ca: obsolete hunspell-ca_3.0.2+repack1-1 has wrong 
section for it.
Control: severity -1 minor
Control: affects 910617 myspell-ca

On Mon, Oct 08, 2018 at 08:43:07PM +0200, Jonas Smedegaard wrote:
> Quoting Agustin Martin (2018-10-08 20:24:50)
> > Control: reassign -1 parl-desktop-world
> > Control: retitle -1 parl-desktop-world: Needs to depend on hunspell-ca 
> > instead of myspell-ca.
> > Control: severity -1 important
> > 
> > On Mon, Oct 08, 2018 at 07:20:22PM +0200, Agustin Martin wrote:
> > > Control: reassign -1 ftp.debian.org
> > > Control: retitle -1 RM: hunspell-ca_3.0.2+repack1-1 -- RoM; This 
> > > particular version does not belong to any release.
> > > Control: severity -1 normal
> > > 
> > > --
> > > Note for ftpmasters: 
> > > 
> > > archive seems to still contain hunspell-ca_3.0.2+repack1-1 version, but
> > > it does not belong to any release
> > 
> > Hi all,
> > 
> > Just noticed why this ancient version is still there. Sorry for the noise,
> > ftpmasters.
> > 
> > $ apt-cache rdepends myspell-ca
> > 
> > parl-desktop-world: Depends: myspell-ca
> > ... Some suggests, recomends and "or'ed" dependencies.
> > 
> > Unfortunately, this hard rdepends went unnoticed when dropping myspell-ca.
> > Will look at other rdepends in case there is another pending hard-depends.
> > There are a couple of Recommends (testing's firefox-esr-l10n-ca and
> > task-catalan-desktop)
> > 
> > I am reassigning this bug report to parl-desktop-world.
> 
> Reassigning?  parl-desktop-world cannot make myspell-ca change section.

myspell-ca is only there because of parl-desktop-world, there is no point in
changing its section. Problem will go as soon as fixed parl-desktop-world is
accepted. That is why I did things this way.

> File a separate bugreport about parl-desktop-world depending on a 
> transitional package, and tag this bug as affected by the new one.

No problem. Doing things this other way. I'd prefer a block, but using
affects.

Regards,

-- 
Agustin

Bug#910619: gnome-shell-extension-multi-monitors: New upstream release

[Jeremy Bicha]

Source: gnome-shell-extension-multi-monitors
Version: 0.00~git20180920.1.0ca053f-1
Severity: wishlist
X-Debbugs-CC: j...@debian.org

Please upgrade to the latest release:
https://github.com/spin83/multi-monitors-add-on/releases

Please update the debian/watch file too.

Thanks,
Jeremy Bicha

Bug#910595: Thunar segfaults when using Wayland and makes it unusable (still)

[Yvan Masson]

Le 08/10/2018 à 16:52, Yves-Alexis Perez a écrit :
> On Mon, 2018-10-08 at 16:28 +0200, Yvan Masson wrote:
>> Package: thunar
>> Version: 1.8.2-1
>> Severity: important
> 
>> Dear Maintainer,
> 
>> I reported a few days ago bug 910353 [1], saying that Thunar 1.8.1
>> crashes under Wayland and that version 1.8.2 should fixe the issue. Your
>> answer were fast (thanks!) and I could pick up thunar 1.8.2 from sid (I
>> use testing).
> 
>> Unfortunately, this new version still crashes under Wayland (no issue
>> under X11): maybe the segfault comes from another dependency that should
>> be upgraded?
> 
> I added the close tag based on your line:
> 
> “Could you upload 1.8.2 to fix this issue?”
> 
> At best it was confusing. What exactly where you referring to here?

Hi Yves-Alexis,

I am sorry, I do not understand your question (my english is not very
good), but I feel that I may have made you angry: in this case please
apologize, be sure that I never wanted to say anything offending and
that I respect the work you do.

If I can help you in any way to solve this issue, feel free to let me know.

Regards,
Yvan




signature.asc
Description: OpenPGP digital signature

Bug#910618: tinc: systemd service in wrong path

[Shengjing Zhu]

Package: tinc
Version: 1.1~pre17-1
Severity: normal

Dear Maintainer,

After upgrading to 1.1~pre17, the systemd service files are in
/usr/lib/x86_64-linux-gnu/systemd/, which is not recognized by systemd.

This is caused by https://github.com/gsliepen/tinc/commit/c2d8264
libdir will be set to multi-arch directory by debhelper.

Thanks
Shengjing Zhu

Bug#910617: parl-desktop-world: Must depend on hunspell-ca instead of myspell-ca

[Agustin Martin]

Package: parl-desktop-world
Version: 1.9.13
Severity: important

Dear Maintainer,

parl-desktop-world depends on transitional package myspell-ca. Current
hunspell-ca package in sid and testing no longer provides myspell-ca, so
dependency needs to be changed to hunspell-ca.

Regards,

-- 
Agustin

Bug#910610: stretch-pu: package dnsmasq/2.76-5+deb9u1

[Adam D. Barratt]

Control: severity -1 normal
Control: tags -1 + confirmed

On Mon, 2018-10-08 at 19:35 +0200, Santiago Ruano Rincón wrote:
> Package: release.debian.org
> Severity: important

p-u requests are always "normal".

> I'd like to propose the attached dnsmasq NMU to update the DNSSEC
> trust anchor shipped with the package, to the forthcoming KSK-2017,
> whose rollover will be happen next Thursday (2018-10-11). Please see
> #907887:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907887
> 
> While I have no feedback from Simon (in CC, and I hope he's doing
> well), I think this upload is important to prevent issues in non-
> default scenarios, where dnsmasq is running with DNSSEC enabled and
> relying on the trust anchors file included in dnsmasq-base.

I assume you mean "and *not* relying on"?

Please go ahead.

Regards,

Adam

Bug#910493: [Pkg-privacy-maintainers] Bug#910493: Handle transition from MAT to MAT2

[Daniel Kahn Gillmor]

On Sun 2018-10-07 10:31:13 +0200, intrigeri wrote:
> 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?

this all looks reasonable to me as well.

thanks for staying on top of it.

   --dkg

Bug#902186: CVE-2018-12689

[Dominik George]

Control: tags -1 + moreinfo
Control: severity -1 important

Heisann,

On Sat, Jun 23, 2018 at 10:45:39AM +0200, Moritz Muehlenhoff wrote:
> Package: phpldapadmin
> Severity: grave
> Tags: security
> 
> Please see
> http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12689

I am triaging this bug report because of a request of a user to get
phpLDAPAdmin into testing again, and the maintainer seems to be unresponsive.

Doing so, I found that in my opinion, the CVE is invalid. Neither of the PoC
works.

 PoC 1 (server_id parameter) does not work because the parameter is verified
 using is_numeric before being passed on to anything special.

 PoC 2 makes phpLDAPAdmin simply display "Invalid DN syntax for user".

No matter what, I was not able to get anything out of phpLDAPAdmin with the
information in the CVE and the refereces exploit. Thus, I am lowering the
priority of this bug report to important and asking you to provide more
information on how to produce the behaviour claimed in the CVE report.

Ha det bra,
Nik

Bug#910616: parl-desktop-eu,parl-desktop-world: Should depend on hunspell-lv instead of myspell-lv

[Agustin Martin]

Package: parl-desktop-eu,parl-desktop-world
Version: 1.9.13
Severity: normal

Hi, Jonas,

Yet another pending myspell->hunspell bug report.

myspell-lv is now a transitional package to hunspell-lv. While it has
recently being added (and it will be available in buster), it would be nice
to think about changing the dependency.

Note that hunspell-lv is not available in current stable (although it is in
sid and testng) so, if you consider a parl-desktop backport, myspell-lv
should better stay as "hunspell-lv | myspell-lv" or something like that.

As said, this is not urgent, but something to think about.

Thanks in advance,

Regards,

-- 
Agustin

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

[Pierre-Elliott Bécue]

Le lundi 08 octobre 2018 à 19:10:55+0200, Baptiste BEAUPLAT a écrit :
> Hello Pierre-Elliott,
> 
> Taking into account your suggestions, I re-uploaded the vitetris package
> with the following fixes:
> 
> * Rework package description
> * Remove extra licence file from package
> 
> Url:
> 
> Package on mentors: https://mentors.debian.net/package/vitetris
> Pool on
> mentors:https://mentors.debian.net/debian/pool/main/v/vitetris/vitetris_0.57.2-1.dsc
> Git: https://salsa.debian.org/lyknode-guest/vitetris
> 
> Best regards,

Hi,

Uploaded. Thanks for your contribution.

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#906643: transition: php7.3

[Emilio Pozuelo Monfort]

On 07/10/2018 20:21, Ondřej Surý wrote:
> 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.

No problem. I updated the tracker and scheduled binNMUs again.

Some modules fail to build against 7.3, see the tracker:

https://release.debian.org/transitions/html/php7.3.html

Cheers,
Emilio

Bug#910589: myspell-ca: should be in package section oldlibs

[Jonas Smedegaard]

Quoting Agustin Martin (2018-10-08 20:24:50)
> Control: reassign -1 parl-desktop-world
> Control: retitle -1 parl-desktop-world: Needs to depend on hunspell-ca 
> instead of myspell-ca.
> Control: severity -1 important
> 
> On Mon, Oct 08, 2018 at 07:20:22PM +0200, Agustin Martin wrote:
> > Control: reassign -1 ftp.debian.org
> > Control: retitle -1 RM: hunspell-ca_3.0.2+repack1-1 -- RoM; This particular 
> > version does not belong to any release.
> > Control: severity -1 normal
> > 
> > --
> > Note for ftpmasters: 
> > 
> > archive seems to still contain hunspell-ca_3.0.2+repack1-1 version, but
> > it does not belong to any release
> 
> Hi all,
> 
> Just noticed why this ancient version is still there. Sorry for the noise,
> ftpmasters.
> 
> $ apt-cache rdepends myspell-ca
> 
> parl-desktop-world: Depends: myspell-ca
> ... Some suggests, recomends and "or'ed" dependencies.
> 
> Unfortunately, this hard rdepends went unnoticed when dropping myspell-ca.
> Will look at other rdepends in case there is another pending hard-depends.
> There are a couple of Recommends (testing's firefox-esr-l10n-ca and
> task-catalan-desktop)
> 
> I am reassigning this bug report to parl-desktop-world.

Reassigning?  parl-desktop-world cannot make myspell-ca change section.

File a separate bugreport about parl-desktop-world depending on a 
transitional package, and tag this bug as affected by the new one.


 - Jonas

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

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


signature.asc
Description: signature

Bug#910251:

[Ron Lovell]

That should be libpsm2-2 11.2.68-1, not .78.

On Mon, Oct 8, 2018 at 1:39 PM Ron Lovell  wrote:

> Alastair,
>
> Thanks for the quick update. I see that I upgraded to libpsm2-2 11.2.78-1
> on 01 Oct 2018, so the timing fits.
>
> Thanks,
> Ron
> --
> James Ronald Lovell 
> Huntsville, AL, USA
>


-- 
James Ronald Lovell 
Huntsville, AL, USA

Bug#910498: debian-edu: autopkgtest regression: education-menus_2.10.38_amd64.deb (--unpack):, trying to overwrite '/usr/share/tasksel/descs/debian-edu-tasks.desc

[Holger Levsen]

On Mon, Oct 08, 2018 at 08:31:56PM +0200, Paul Gevers wrote:
> Maybe a bug in one of the helper functions (debhelper, dpkg*)?

maybe, yes. this needs more investigation...

> > on a related note, why are you filing serious bugs about this, Paul?
> > (More concerned about your work load here than anything else...)
> > Because, shouldn't the autotesting-regression be enough, especially in the
> > soon-to-be-future?
> In the soon-to-be-future, yes, but we're not there yet. As I am filing
> these bug to let you know about the regression, I might as well try to
> put the right severity on it.

right. I do check tracker.d.o/$srcpkg after uploads regularily so I
would have noticed anyway, but I guess not everyone's doing that.

> About my work-load,

aehm, sorry, of course you know best about your work-load!

> I focus on autopkgtest regressions with multiple
> packages involved first. And only process the regression ones later.
> What I try to achieve is that I understand case that our infrastructure
> isn't handling properly yet.
 
very nice! thanks for all your work on autopkgtest & britney & all that.
very very nice, in fact!


-- 
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#910251:

[Ron Lovell]

Alastair,

Thanks for the quick update. I see that I upgraded to libpsm2-2 11.2.78-1
on 01 Oct 2018, so the timing fits.

Thanks,
Ron
-- 
James Ronald Lovell 
Huntsville, AL, USA

Bug#910615: task-catalan-desktop: Please recommend hunspell-ca instead of dropped transitional package myspell-ca

[Agustin Martin]

Package: task-catalan-desktop
Version: 3.46
Severity: normal

Dear Maintainer,

myspell-ca transitional package is being dropped. Please change Recommends
to hunspell-ca.

Thanks in advance.

Regards,

-- 
Agustin

Bug#796795: grub-pc-bin: Please use a bigger font

[Samuel Thibault]

Control: severity -1 important

Hello,

Samuel Thibault, le lun. 24 août 2015 18:00:40 +0200, a ecrit:
> Screen DPI (at last!) gets bigger, and thus the font currently used by
> grub becomes too small, making it very hard to read the boot menu.

I now have a HiDPI display, and the font is now simply unreadable.

Samuel

Bug#910498: debian-edu: autopkgtest regression: education-menus_2.10.38_amd64.deb (--unpack):, trying to overwrite '/usr/share/tasksel/descs/debian-edu-tasks.desc

[Paul Gevers]

Hi,

On 08-10-18 12:54, Holger Levsen wrote:
> On Mon, Oct 08, 2018 at 12:39:13PM +0200, Wolfgang Schweer wrote:
>> Trying to reproduce this, I ran 'debuild -us -uc -ui' in a clean
>> debian-edu.git clone directory.
>> The output from
>> find debian/ -name '*tasks.desc' is
>> debian/education-tasks/usr/share/tasksel/descs/debian-edu-tasks.desc
>>
>> Also,
>> https://packages.debian.org/sid/amd64/education-menus/filelist
>> doesn't contain
>> /usr/share/tasksel/descs/debian-edu-tasks.desc
>>
>> I have no clue how to debug this further.
> 
> given the changes between those two src:debian-edu versions i'm also
> puzzled and clueless how this happened.

Maybe a bug in one of the helper functions (debhelper, dpkg*)?

> on a related note, why are you filing serious bugs about this, Paul?
> (More concerned about your work load here than anything else...)
> Because, shouldn't the autotesting-regression be enough, especially in the
> soon-to-be-future?

In the soon-to-be-future, yes, but we're not there yet. As I am filing
these bug to let you know about the regression, I might as well try to
put the right severity on it.

About my work-load, I focus on autopkgtest regressions with multiple
packages involved first. And only process the regression ones later.
What I try to achieve is that I understand case that our infrastructure
isn't handling properly yet.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#910589: myspell-ca: should be in package section oldlibs

[Agustin Martin]

Control: reassign -1 parl-desktop-world
Control: retitle -1 parl-desktop-world: Needs to depend on hunspell-ca instead 
of myspell-ca.
Control: severity -1 important

On Mon, Oct 08, 2018 at 07:20:22PM +0200, Agustin Martin wrote:
> Control: reassign -1 ftp.debian.org
> Control: retitle -1 RM: hunspell-ca_3.0.2+repack1-1 -- RoM; This particular 
> version does not belong to any release.
> Control: severity -1 normal
> 
> --
> Note for ftpmasters: 
> 
> archive seems to still contain hunspell-ca_3.0.2+repack1-1 version, but
> it does not belong to any release

Hi all,

Just noticed why this ancient version is still there. Sorry for the noise,
ftpmasters.

$ apt-cache rdepends myspell-ca

parl-desktop-world: Depends: myspell-ca
... Some suggests, recomends and "or'ed" dependencies.

Unfortunately, this hard rdepends went unnoticed when dropping myspell-ca.
Will look at other rdepends in case there is another pending hard-depends.
There are a couple of Recommends (testing's firefox-esr-l10n-ca and
task-catalan-desktop)

I am reassigning this bug report to parl-desktop-world.

Thanks all involved.

-- 
Agustin

Bug#910612: xscreensaver should clean out it's pic cache

[Jamie Zawinski]

Cache times out after 3 hours, or the first time no suitable images are found.

Bug#910614: RFP: node-ecstatic -- A nodejs simple static file server

[Jeff Cliff]

Package: wnpp
Severity: wishlist

* Package name: node-ecstatic
  Version : 3.2.0
  Upstream Author : Joshua Holbrook ( @jfhbr...@twitter.com )
* URL : https://notabug.org/themusicgod1/ecstatic
* License : MIT
  Programming Lang: javascript
  Description : A nodejs simple static file server

A simple static file server middleware. Use it with a raw http server, 
express/connect 
or on the CLI.

Bug#910613: Unecessary dependency on python3-tk

[Yuri D'Elia]

Package: python3-seaborn
Version: 0.8.0-1
Severity: normal

NMU version 0.8.0-1.1 add a Depends: python3-tk, however this dependency
shouldn't be there.

I fought hard to remove it in the first place.

If you follow the bug report in #896401 and #896003, the dependency is
triggered when using matplotlib.

matplotlib *already* recommends python3-tk.
That's already correct and enough.

matplotlib doesn't *depend* on it because the tk backend is *not*
required for matplotlib to work. matplotlib can work with agg, Qt or
cairo.

The python3-tk dependency is pulling extra useless dependencies on
headless systems.

Please remove the extra dependency.
Thanks

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

Kernel: Linux 4.18.0-2-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)

Versions of packages python3-seaborn depends on:
ii  python3 3.6.6-1
ii  python3-matplotlib  2.2.2-4+b1
ii  python3-numpy   1:1.14.5-1+b1
ii  python3-pandas  0.23.3-1
ii  python3-scipy   1.1.0-1+b1

Versions of packages python3-seaborn recommends:
pn  python3-bs4
ii  python3-patsy  0.4.1+git34-ga5b54c2-1

python3-seaborn suggests no packages.

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

[Juan Picca]

About issues: We can't change where the users create bug reports, only
suggest the correct place to do it. The extra work for BTS/salsa
issues (if enabled) for me is inevitable.

About the move from salsa.d.o, the question is: salsa.d.o can be used
for general projects born in debian or is most suited for debian
specific projects?

If salsa.d.o is suited, the next step should be enable the issues in
the repository and handle the work of manage duplicated issues between
the repository and the BTS,  while the users understand the correct
place to create issues.

If as Holger suggests, salsa.d.o is very much Debian centric then has
sense look for a new home for diffoscope and maybe other rb
repositories (eg website).
Personally i expect not.

Regards,
JMPC

Bug#910612: xscreensaver should clean out it's pic cache

[Frank McCormick]

Package: xscreensaver
Version: 5.40-1
Severity: normal

run xscreensaver glslideshow.
change selection of pics in /home/Pictures
xscreensaver tries to find old pics
it's getting info from /home/.cache/xscreensaver


Those files should be deleted after changing pic selection



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

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

Versions of packages xscreensaver depends on:
ii  libatk1.0-0  2.30.0-1
ii  libc62.27-6
ii  libcairo21.15.12-1
ii  libfontconfig1   2.13.1-1
ii  libfreetype6 2.8.1-2
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-6
ii  libglade2-0  1:2.6.4-2+b1
ii  libglib2.0-0 2.58.1-2
ii  libgtk2.0-0  2.24.32-3
ii  libice6  2:1.0.9-2
ii  libpam0g 1.1.8-3.8
ii  libpango-1.0-0   1.42.4-3
ii  libpangocairo-1.0-0  1.42.4-3
ii  libpangoft2-1.0-01.42.4-3
ii  libsm6   2:1.2.2-1+b3
ii  libx11-6 2:1.6.6-1
ii  libxext6 2:1.3.3-1+b2
ii  libxi6   2:1.7.9-1
ii  libxinerama1 2:1.1.4-1
ii  libxml2  2.9.4+dfsg1-7+b1
ii  libxmu6  2:1.1.2-2
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxt6   1:1.1.5-1
ii  libxxf86vm1  1:1.1.4-1+b2
ii  xscreensaver-data5.40-1

Versions of packages xscreensaver recommends:
ii  libjpeg-turbo-progs   1:1.5.2-2+b1
ii  perl  5.26.2-7
ii  wamerican [wordlist]  2018.04.16-1

Versions of packages xscreensaver suggests:
ii  firefox [www-browser]   62.0.3-1
pn  fortune 
pn  gdm3 | kdm-gdmcompat
ii  google-chrome-stable [www-browser]  69.0.3497.100-1
pn  qcam | streamer 
pn  xdaliclock  
pn  xfishtank   
ii  xscreensaver-data-extra 5.40-1
ii  xscreensaver-gl 5.40-1
ii  xscreensaver-gl-extra   5.40-1

-- no debconf information

Bug#910397: Tab crashes while connecting webrtc video conferencing

[Julien Cristau]

On Fri, Oct  5, 2018 at 23:53:46 +0200, Paul van der Vlis wrote:

> Package: firefox-esr
> Version: 60.2.2esr-1~deb9u1
> 
> When I connect with webrtc microphone and webcam the Firefox tab crashes
> when the second person connects. Both sides are crashing. This is since
> version 60, before no problem. Also no problem with Chromium.
> 
> Easy to test without account with e.g.:
> https://linkello.com
> https://meet.jit.si
> 
Hitting something that looks suspiciously like this, on appear.in.

Example report from about:crashes:
https://crash-stats.mozilla.org/report/index/1478bfee-aa7c-4307-a5c3-cb7460181008

libxul.so@0x33e0b70 resolves to:
/build/firefox-esr-RlCnTw/firefox-esr-60.2.2esr/media/webrtc/trunk/webrtc/base/task_queue_libevent.cc:320

https://hg.mozilla.org/releases/mozilla-esr60/file/FIREFOX_60_2_2esr_RELEASE/media/webrtc/trunk/webrtc/base/task_queue_libevent.cc#l320

Looks like either timer or timer->task is NULL?

Cheers,
Julien

Bug#910395: Bug#910611: openjfx: draws mediathekview and pdfsam unusable

[Markus Koschany]

Control: forcemerge 910395 910611

Am 08.10.18 um 19:37 schrieb Philip Rinn:
> Package: openjfx
> Version: 11+26-3
> Severity: normal
> 
> Hi,
> 
> since some days (sadly I don't know it the 8 -> 11 update triggered this)
> mediathekview and pdfsam don't start anymore:

Hi,

we are aware of the current issues with OpenJFX 11 and applications like
MediathekView and PDFsam. I am very close to release an update for
MediathekView if we can fix Debian bug #910585. PDFsam will require more
time but hopefully it can be fixed soon.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#910237: Bug

[Steve Robbins]

On Monday, October 8, 2018 1:58:13 AM CDT Graham Inggs wrote:
> Hi Steve / Doug
> 
> On Mon, 8 Oct 2018 at 07:27, Steve Robbins  wrote:
> > This level seems a bit extreme, to me, considering the guidelines in
> > https:// www.debian.org/Bugs/Developer
> 
> Severity serious is correct.  From the RC policy document [1]:
> 
> Packages must autobuild without failure on all architectures on which
> they are supported.

Right, and googletest autobuilds while mathicgb does not.  So my reading is 
that this criteria applies to a bug in mathicgb, not googletest.

 
> > Moreover, it's not clear that the bug lies with googletest.
> 
> Yes, there is at least an RC bug in googletest or mathicgb, hence Paul
> wrote:
> On Wed, 3 Oct 2018 at 20:27, Paul Gevers  wrote:
> > 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?

Yes.  Clearly there is a change in the interface that mathicgb is using.  I 
can't tell whether the change to googletest was incidental or deliberate.  In 
the former case, there would be a bug in googletest.  However, it would not be 
serious in my reading of the criteria ("is a severe violation of Debian policy 
(roughly, it violates a must or required directive), or, in the package 
maintainer's or release manager's opinion, makes the package unsuitable for 
release").

> Googletest 1.8.1-1 should not migrate to testing as long as mathicgb
> FTBFS.  

This is the assertion that I don't understand.

-Steve

Bug#910611: openjfx: draws mediathekview and pdfsam unusable

[Philip Rinn]

Package: openjfx
Version: 11+26-3
Severity: normal

Hi,

since some days (sadly I don't know it the 8 -> 11 update triggered this)
mediathekview and pdfsam don't start anymore:


philip@debian:~$ mediathekview
===
JavaFX wurde nicht im klassenpfad gefunden.
 Stellen Sie sicher, dass Sie ein Java JRE ab Version 8 benutzen.
 Falls Sie Linux nutzen, installieren Sie das openjfx-Paket ihres Package-
Managers,
 oder nutzen Sie eine eigene JRE-Installation.
===

Translation:
JavaFX was not found in the classpah.
Ensure that you are using Java JRE 8 or later.
If you use Linux, install the openjfx package provided by your pacakge manager
or use a seaparate JRE installation.

see also bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910395


philip@debian:~$ pdfsam
Exception in thread "main" java.lang.NoClassDefFoundError:
javafx/scene/layout/HBox
at java.base/java.lang.ClassLoader.defineClass1(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1009)
at
java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174)
at
java.base/jdk.internal.loader.BuiltinClassLoader.defineClass(BuiltinClassLoader.java:801)
at
java.base/jdk.internal.loader.BuiltinClassLoader.findClassOnClassPathOrNull(BuiltinClassLoader.java:699)
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClassOrNull(BuiltinClassLoader.java:622)
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:580)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:190)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
at org.pdfsam.community.App.main(App.java:34)
Caused by: java.lang.ClassNotFoundException: javafx.scene.layout.HBox
at
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582)
at
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:190)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499)
... 10 more



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

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

Versions of packages openjfx depends on:
ii  libopenjfx-java  11+26-3

Versions of packages openjfx recommends:
pn  openjfx-source  

openjfx suggests no packages.

-- no debconf information

Bug#910610: stretch-pu: package dnsmasq/2.76-5+deb9u1

[Santiago Ruano Rincón]

Package: release.debian.org
Severity: important
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Dear stable release managers,

I'd like to propose the attached dnsmasq NMU to update the DNSSEC trust
anchor shipped with the package, to the forthcoming KSK-2017, whose
rollover will be happen next Thursday (2018-10-11). Please see #907887:

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

While I have no feedback from Simon (in CC, and I hope he's doing well),
I think this upload is important to prevent issues in non-default
scenarios, where dnsmasq is running with DNSSEC enabled and relying on
the trust anchors file included in dnsmasq-base.

May I go ahead?

Cheers,

  -- Santiago
diff -u dnsmasq-2.76/debian/changelog dnsmasq-2.76/debian/changelog
--- dnsmasq-2.76/debian/changelog
+++ dnsmasq-2.76/debian/changelog
@@ -1,3 +1,11 @@
+dnsmasq (2.76-5+deb9u1.1) stretch; urgency=medium
+
+  * Non-maintainer upload.
+  * trust-anchors.conf: include latest DNS trust anchor KSK-2017.
+(Closes: #907887)
+
+ -- Santiago Ruano Rincón   Fri, 21 Sep 2018 17:06:18 
+0200
+
 dnsmasq (2.76-5+deb9u1) stretch-security; urgency=high
 
   * Non-maintainer upload by the Security Team.
only in patch2:
unchanged:
--- dnsmasq-2.76.orig/trust-anchors.conf
+++ dnsmasq-2.76/trust-anchors.conf
@@ -1,9 +1,10 @@
-# The root DNSSEC trust anchor, valid as at 30/01/2014
+# The root DNSSEC trust anchor, valid as at 10/02/2017
 
 # Note that this is a DS record (ie a hash of the root Zone Signing Key) 
 # If was downloaded from https://data.iana.org/root-anchors/root-anchors.xml
 
 
trust-anchor=.,19036,8,2,49AAC11D7B6F6446702E54A1607371607A1A41855200FD2CE1CDDE32F24E8FB5
+trust-anchor=.,20326,8,2,E06D44B80B8F1D39A95C0B0D7C65D08458E880409BBC683457104237C7F8EC8D
 
 
 


signature.asc
Description: PGP signature

Bug#910579: tracker: cannot initialize database: error in view fts_view

[Hideki Yamane]

On Mon, 08 Oct 2018 19:48:36 +0900 Hideki Yamane  wrote:
> Package: tracker
> Version: 2.1.4-1
> Severity: important
> 
> Dear Maintainer,
> 
>  Recently, I found tracker eats lots of CPU and it shows below log.

 It's same issue on upstream issue tracker
 https://gitlab.gnome.org/GNOME/tracker/issues/40

 And "tracker reset --hard" solved problem.


-- 
Regards,

 Hideki Yamane henrich @ debian.org/iijmio-mail.jp

Bug#910589: myspell-ca: should be in package section oldlibs

[Agustin Martin]

Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: hunspell-ca_3.0.2+repack1-1 -- RoM; This particular 
version does not belong to any release.
Control: severity -1 normal

--
Note for ftpmasters: 

archive seems to still contain hunspell-ca_3.0.2+repack1-1 version, but
it does not belong to any release

stretch (stable): 3.0.1+repack1-3: all
buster (testing): 3.0.3+repack1-1: all
sid (unstable)  : 3.0.3+repack1-1: all

Please remove hunspell-ca_3.0.2+repack1-1 version from the archive.

hunspell-ca_3.0.2+repack1-1 should have been automatically removed when new
version (3.0.2+repack1-2, Sep 2017) reached testing, but seems something
went wrong.

This results in dropped myspell-ca being still available from sid.

If interested, read below for more details about this particular case.
--

On Mon, Oct 08, 2018 at 06:02:18PM +0200, Jonas Smedegaard wrote:
> Quoting Agustin Martin (2018-10-08 17:51:34)
> > On Mon, Oct 08, 2018 at 03:04:21PM +0200, Jonas Smedegaard wrote:
> > > myspell-ca is an empty transitional package, and as such belongs in 
> > > package section oldlibs rather than text.
> [...]
> > myspell-ca was dropped in 3.0.2+repack1-2 (07 Sep 2017) and its 
> > control file already had Section:oldlibs at that time. It has 
> > Section:oldlibs even in current stable version (3.0.1+repack1-2).
> > 
> > Seems override file still has some ancient stuff. In this case, where 
> > transitional package is already gone I do not think it worths changes 
> > by ftpmasters.
> > 
> > Unless you object I will close this bug report in some days. Otherwise 
> > I will reassign this bug report to ftp.debian.org.
> 
> If package is gone then I certainly agree you can simply close this bug 
> as obsolete.
> 
> ...but it seems to me that the package did _not_ get removed yet - see 
> e.g. https://packages.debian.org/search?keywords=hunspell-ca which lists 
> the package in release 3.0.3+repack1-1 in both Buster and Sid.

Hi, Jonas,

Thanks a lot for the aditional info,

Indeed, myspell-ca seems to still be available in Sid, as given by

https://packages.debian.org/search?keywords=myspell-ca

in (old) version 3.0.2+repack1-1. 
https://tracker.debian.org/pkg/hunspell-ca does not show it.

Looking at ftp.debian.org/debian/pool/main/h/hunspell-ca I still see it
there, and available with sources for that 3.0.2+repack1-1 version!!

As a result of that, myspell-ca is still available for Sid (as shown by
apt-cache policy myspell-ca).

I am reassigning this bug report to ftp.debian.org asking for removal of
that particular version 3.0.2+repack1-1.

Thanks for warning about this obsolete stuff.

Regards,

-- 
Agustin

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

[Baptiste BEAUPLAT]

Hello Pierre-Elliott,

Taking into account your suggestions, I re-uploaded the vitetris package
with the following fixes:

* Rework package description
* Remove extra licence file from package

Url:

Package on mentors: https://mentors.debian.net/package/vitetris
Pool on
mentors:https://mentors.debian.net/debian/pool/main/v/vitetris/vitetris_0.57.2-1.dsc
Git: https://salsa.debian.org/lyknode-guest/vitetris

Best regards,

-- 
Baptiste BEAUPLAT - lyknode




signature.asc
Description: OpenPGP digital signature

Bug#910609: node-colors: updated version

[Jeffrey Cliff]

Package: node-colors
Version: 1.1.2-1
Severity: normal
Tags: patch

Dear Maintainer,

Before upstream github was taken over by NSA/Microsoft, there was a newer
version of node-colors available upstream.  The following patch patches
node-colors to the newer version (a commit or two past 1.2.4).

The changes include bug fixes, tweaks to the styling, improved tests and a
slightly different API - see commit log for full details:
https://notabug.org/themusicgod1/colors/commits/master . It's a lot of
little changes(32K).  Newer versions are required by other projects such as
mist ( #827314 ).

-- 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-colors depends on:
ii  nodejs  8.11.2~dfsg-1

node-colors recommends no packages.

node-colors suggests no packages.

-- no debconf information
diff -r colors.js-1.2.4/debian/changelog colors.js-1.1.2/debian/changelog
1,6d0
< colors.js (1.2.4-1) UNRELEASED; urgency=medium
< 
<   * New upstream version 1.2.4-1
< 
<  -- Jeffrey Cliff   Mon, 08 Oct 2018 09:57:02 +0500
< 
diff -r colors.js-1.2.4/debian/control colors.js-1.1.2/debian/control
14c14
< Depends: ${misc:Depends}, nodejs(>= 0.1.90)
---
> Depends: ${misc:Depends}, nodejs
Only in colors.js-1.2.4/debian: .debhelper
Only in colors.js-1.2.4/debian: files
Only in colors.js-1.2.4/debian: node-colors
Only in colors.js-1.2.4/debian: node-colors.debhelper.log
Only in colors.js-1.2.4/debian: node-colors.substvars
Only in colors.js-1.2.4: .eslintrc.json
diff -r colors.js-1.2.4/examples/normal-usage.js colors.js-1.1.2/examples/normal-usage.js
3c3
< console.log('First some yellow text'.yellow);
---
> console.log("First some yellow text".yellow);
5c5
< console.log('Underline that text'.yellow.underline);
---
> console.log("Underline that text".yellow.underline);
7c7
< console.log('Make it bold and red'.red.bold);
---
> console.log("Make it bold and red".red.bold);
9c9
< console.log(('Double Raindows All Day Long').rainbow);
---
> console.log(("Double Raindows All Day Long").rainbow)
11c11
< console.log('Drop the bass'.trap);
---
> console.log("Drop the bass".trap)
13c13
< console.log('DROP THE RAINBOW BASS'.trap.rainbow);
---
> console.log("DROP THE RAINBOW BASS".trap.rainbow)
15,16d14
< // styles not widely supported
< console.log('Chains are also cool.'.bold.italic.underline.red);
18,21c16,19
< // styles not widely supported
< console.log('So '.green + 'are'.underline + ' ' + 'inverse'.inverse
<   + ' styles! '.yellow.bold);
< console.log('Zebras are so fun!'.zebra);
---
> console.log('Chains are also cool.'.bold.italic.underline.red); // styles not widely supported
> 
> console.log('So '.green + 'are'.underline + ' ' + 'inverse'.inverse + ' styles! '.yellow.bold); // styles not widely supported
> console.log("Zebras are so fun!".zebra);
26c24
< console.log('This is ' + 'not'.strikethrough + ' fun.');
---
> console.log("This is " + "not".strikethrough + " fun.");
28,30c26,28
< console.log('Background color attack!'.black.bgWhite);
< console.log('Use random styles on everything!'.random);
< console.log('America, Heck Yeah!'.america);
---
> console.log('Background color attack!'.black.bgWhite)
> console.log('Use random styles on everything!'.random)
> console.log('America, Heck Yeah!'.america)
33c31
< console.log('Setting themes is useful');
---
> console.log('Setting themes is useful')
50c48
<   error: 'red',
---
>   error: 'red'
54c52
< console.log('this is an error'.error);
---
> console.log("this is an error".error);
57c55
< console.log('this is a warning'.warn);
---
> console.log("this is a warning".warn);
60c58
< console.log('this is an input'.input);
---
> console.log("this is an input".input);
65,69c63
< try {
<   colors.setTheme(require(__dirname + '/../themes/generic-logging.js'));
< } catch (err) {
<   console.log(err);
< }
---
> colors.setTheme(__dirname + '/../themes/generic-logging.js');
72c66
< console.log('this is an error'.error);
---
> console.log("this is an error".error);
75c69
< console.log('this is a warning'.warn);
---
> console.log("this is a warning".warn);
78,80c72
< console.log('this is an input'.input);
< 
< // console.log("Don't summon".zalgo)
---
> console.log("this is an input".input);
81a74
> //console.log("Don't summon".zalgo)
\ No newline at end of file
diff -r colors.js-1.2.4/examples/safe-string.js colors.js-1.1.2/examples/safe-string.js
3c3
< console.log(colors.yellow('First some yellow text'));
---
> console.log(colors.yellow("First some yellow text"));
5c5
< console.log(colors.yellow.underline('Underline that text'));
---
> console.log(colors.yellow.underline("Underline that text"));
7c7
< console.log(colors.red.bold('Make it bold and red'));

Bug#695873: memtest86+ patch works on 5.01-3ubuntu2

[Edwin Török]

Dear Maintainer,

I have just run into this problem, applied the patch from the bugreport
and confirmed that it works with memtest86+ 5.01-3ubuntu2 on a Dell
PowerEdge R720.

Could you please apply the patch to the package in Debian?

Thanks,
--Edwin

Bug#910608: RFS: libtheft/0.4.5-1 ITP #910296

[Richard Ipsum]

Package: sponsorship-requests
 Severity: wishlist

 Dear mentors,

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

* Package name: libtheft
  Version : 0.4.5-1
  Upstream Author : Scott Vokes 
* URL : https://github.com/silentbicycle/theft
* License : ISC
  Section : libs

 It builds those binary packages:

   libtheft-dev - property-based testing for C

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

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


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

   dget -x 
https://mentors.debian.net/debian/pool/main/libt/libtheft/libtheft_0.4.5-1.dsc

 More information about libtheft can be obtained from 
https://github.com/silentbicycle/theft
 and https://yakking.branchable.com/posts/property-testing-in-c/.

 Changes since the last upload:

 libtheft (0.4.5-1) unstable; urgency=medium

  * Initial release (Closes: #910296)

 -- Richard Ipsum   Thu, 04 Oct 2018 18:07:05 +0100

 Regards,
  Richard Ipsum

Bug#910607: zfs-linux: 'zfs receive' can apparently corrupt system mount table.

[Colm Buckley]

Source: zfs-linux
Version: v0.7.11-1
Severity: important
Tags: upstream

Descendent filesystems which have out-of-tree mount points are not
correctly recovered on 'zfs send | zfs receive', leading to apparent
corruption of the mount table. With kernel 4.18, processes accessing
problematic parts of the filesystem can become wedged.

See full report in upstream at https://github.com/zfsonlinux/zfs/issues/7970

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

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

Bug#909750: firefox tries to write to /usr/* directories

[Vincas Dargis]

Running `sudo fc-cache -f` didn't helped.

Bug#907725: Fwd: Appropriate Section for PCF Fonts

[Chris Lamb]

Paul,

> [..]

Unfortunately I have very little insight or input to share on fonts or
sections more generally in Debian so I will just have to leave this up
to someone else. Apologies that I could not make progress here.

(I do somehow doubt a mass bug filing would be really appropriate or
welcome, mind you. Did you consider "fixing" Lintian instead?)

> looking at the NEW queue it is obvious how swamped they are so I
> wasn't expecting a rapid response.

As an aside, the raw number of the NEW queue is highly misleading as
there are huge number of source packages blocked on an identical issue.

Again, sorry I can't be of more help.


Regards,

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

Bug#906472: How should sparse depend on gcc?

[Uwe Kleine-König]

Hello,

On 09/21/2018 04:33 PM, Uwe Kleine-König wrote:
> sparse is a C code checker that reuses include files from gcc. Currently
> there are missing the needed dependencies
> (https://bugs.debian.org/906472).
> 
> Now I wonder, what is the right way to depend on gcc. For sparse it
> would be enough to depend on libgcc-8-dev (I think), but as cgcc (which
> is included in the sparse package) calls gcc, too, I need a dependency
> on the gcc package directly (which via gcc-8 depends on libgcc-8-dev).
> 
> As gcc-7 doesn't provide the needed paths, gcc 4:7.whatever isn't enough
> though.
> 
> I can imagine the following options to depend on:
> 
>   a) gcc, libgcc-8-dev
>   b) gcc (>= 4:8~), gcc (<< 4:9)
> 
> . Both have the disadvantage that they need manual adaption when gcc
> bumps it's major version.
> 
> a) also has the disadvantage that gcc might provide gcc-9 and so sparse
> uses different includes than the default compiler (not sure this is bad
> enough to care).
> 
> b) is bad, because gcc_4:9~prerelease12 would be good enough to make
> dpkg happy, but sparse would fail anyhow.
> 
> Alternatively sparse could stop hardcoding the include path and ask gcc
> on each invokation. But I don't like that much as the path hardly ever
> changes and it adds some overhead to sparse.
> 
> Do you have any thoughts/recommendations?

FTR: I changed cgcc to call gcc-8 (instead of cc) now and added a
dependency on gcc-8 now. This way it should be given that the include
files don't disappear and the called programs are around.

Best regards
Uwe



signature.asc
Description: OpenPGP digital signature

Bug#910594: lintian: complain about missing versioned dependency on init-system-helpers

[Chris Lamb]

Hi Stuart,

> Over in #910593, I reported that the maintainer script was using a feature of
> update-rc.d that is not available in stretch.

Yes, this is something that Lintian could indeed spot.

> One could also look for the dh_installinit call in debian/rules […]

Not quite sure what you mean by this bit?


Regards,

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

Bug#908204: git-buildpackage: cannot use gbp push without tagging a release

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sun, 9 Sep 2018 17:59:19 +0200 Guido =?iso-8859-1?Q?G=FCnther?= <
a...@sigxcpu.org> wrote:
> Hi,
> On Sun, Sep 09, 2018 at 10:45:35PM +0900, Norbert Preining wrote:
> > Hi Guido,
> > 
> > > See the man page.
> > 
> > Ok, was that always like this? I faintly remember (but without
> > screenshot to prove it) that I could gbp push stuff even without a
> > tagged debian release!?
> 
> It pushes everything *except* for the tip of your packaging branch (that
> is any tags needed, upstream and pristine tar.
> > 
> > > not up to date. If this does not happen it's a bug but pushing non
> > > uptodate debian packaging branch is not the focus.
> > 
> > ? I don't get what you want to say? I want gbp push to push the branches
> > that are normally used by gbp (master/upstream/pristine-tar) and push
> > any tag from gbp tag that isn't up there.
> 
> And it does that, see this test:
> 
> 
https://github.com/agx/git-buildpackage/blob/master/tests/component/deb/test_push.py#L106
> 
> > Is this so unreasonable?
> > 
> > Maybe I am the only developer on this earth that uses two computers and
> > prefers to push/pull, but I was more than once beaten by a not pushed
> > pristine-tar branch...
> 
Hi,

I started using gbp push/pull recently and I'm also surprised by the current
behavior. What is the rationale for *not* pushing the Debian branch as part of
the push?

For me, gbp push semantics are: “just push everything needed”, but it's
obviously not the intended behavior. What is the intended behavior then?

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlu7husACgkQ3rYcyPpX
RFux4gf+O2W4z5q4fHNb5GSsI9ifqv4yZ8YDopsBWPrPO11sFV22akRzpb6W13p5
ebl5bBWIcrfY6gX85vZZaY2YD7zmq/pXGZn1eaI7rEHWA0SYgIyPqbreQcOPjkFJ
DZhj1DKV4pQJr2yvrLnm89u7xKqR+LZEBWwR2svRTxvwyY5VHZ7DuAGJj9jZX+dq
SIka5d46+vcGgyhB+93Wwee2+MM8EgyNFal+dDE0OOhN4NQBu7nt0m8O2CKlD+7p
a/GWDOUj1UlxA0bLi/PoAeiXBbkpHXz9HdbYjfqCyWmy+VD65K6wzTMtE9NSVwiR
7iYbZtJj7rSwj/LTyRXKu59Am1MNwA==
=+cgN
-END PGP SIGNATURE-

Bug#910606: benchmark: FTBFS on hppa - needs CycleTimer

[John David Anglin]

Source: benchmark
Severity: normal
Tags: patch

Dear Maintainer,

The build fails here:

[ 25%] Building CXX object src/CMakeFiles/benchmark.dir/sysinfo.cc.o
cd /<>/obj-hppa-linux-gnu/src && /usr/bin/c++  -DHAVE_POSIX_REGEX 
-DHAVE_STD_REGEX -DHAVE_STEADY_CLOCK -Dbenchmark_EXPORTS 
-I/<>/include -I/<>/src 
-I/<>/src/../include  -g -O2 -fdebug-prefix-map=/<>=. 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -std=c++11  
-Wall  -Wextra  -Wshadow  -pedantic  -pedantic-errors  -Wfloat-equal  
-fstrict-aliasing  -Wstrict-aliasing -fPIC   -o 
CMakeFiles/benchmark.dir/sysinfo.cc.o -c /<>/src/sysinfo.cc
In file included from /<>/src/sysinfo.cc:57:
/<>/src/cycleclock.h:171:2: error: #error You need to define 
CycleTimer for your OS and CPU
 #error You need to define CycleTimer for your OS and CPU

The attached patch adds a bit of code to access the interval timer on hppa.
This fixes the build error.

Note that a 32-bit counter value is returned when the processor is running
in narrow mode.  The counter nominally runs at the processor frequency.

Regards,
Dave Anglin

-- System Information:
Debian Release: buster/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 4.14.74+ (SMP w/4 CPU cores)
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: systemd (via /run/systemd/system)
--- cycleclock.h.save   2018-10-08 11:07:53.775998772 -0400
+++ cycleclock.h2018-10-08 12:01:01.01340 -0400
@@ -100,6 +100,11 @@
   int64_t itc;
   asm("mov %0 = ar.itc" : "=r"(itc));
   return itc;
+#elif defined(__hppa__)
+  // Counter can only be read when PSW S bit is 0.
+  long itc;
+  asm("mfctl 16,%0" : "=r"(itc));
+  return static_cast(itc);
 #elif defined(COMPILER_MSVC) && defined(_M_IX86)
   // Older MSVC compilers (like 7.x) don't seem to support the
   // __rdtsc intrinsic properly, so I prefer to use _asm instead

Bug#910587: hunspell-eu-es: should be in package section oldlibs

[Agustin Martin]

Control: reassign -1 ftp.debian.org
Control: retitle -1 override: hunspell-eu-es:oldlibs/optional

On Mon, Oct 08, 2018 at 02:56:15PM +0200, Jonas Smedegaard wrote:
> Package: hunspell-eu-es
> Version: 0.5.20151110-3
> Severity: minor
> 
> hunspell-eu-es is an empty transitional package,
> and as such belong in package section oldlibs rather than text.

Hi Jonas,

This is yet another example of ancient overrides, hunspell-eu-es control
file contains Section: oldlibs since 2015.

Reassigning to ftp.debian.org.

Thanks for the info,

-- 
Agustin