Bug#899513: Debian中文团队邮件地址即将失效，可能需要一位DD在5月末前采取行动

[Lumin]

(In order to draw attention from admins of debian-chinese team, this
mail is written in Simplified Chinese deliberately.)

// Encoding: UTF-8, Simplified Chinese

致 Debian 中文团队：

随着 Alioth 逐步被弃用，相关的邮件列表服务也受到波及。虽然数月前
Boyuan 已经在 debian-chinese-gb 邮件列表提出邮件列表迁移问题[1]，但并
没有的到任何答复。

现在仍然在使用中文团队 Alioth 地址[2]的软件包应该都已经收到了相应的
RC BUG， 比如[3]。按照 Boyuan 的建议，我们有以下两个选择来处理中文团队
邮件地址的问题：

 「1」邮件地址整体迁移到 »team+chin...@tracker.debian.org«
 「2」让一位 DD 出面向 Alioth Lists Team 申请邮件地址续期。

鉴于选项「2」的最后截至日期是本月末，恳请中文团队的各位管理员尽快
决定一个统一的解决方案。另外必须说明，我和 Boyuan 均是 DM，没有
足够权限来进行决策和相应操作。

非常感谢。

[1] https://lists.debian.org/debian-chinese-gb/2018/01/msg6.html
[2] chinese-develop...@lists.alioth.debian.org
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899513


signature.asc
Description: PGP signature

Bug#900095: marked as done (FTBFS against xserver-xorg-core 1.20.0)

[Debian Bug Tracking System]

Your message dated Sat, 26 May 2018 05:34:23 +
with message-id 
and subject line Bug#900095: fixed in xserver-xorg-video-vmware 1:13.3.0-2
has caused the Debian Bug report #900095,
regarding FTBFS against xserver-xorg-core 1.20.0
to be marked as done.

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

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


-- 
900095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xserver-xorg-video-vmware
Version: 13.2.1-1
Severity: serious

The recent update of xserver-xorg-core to 1.20.0 makes the package
FTBFS as can be seen by the latest binNMU

https://buildd.debian.org/status/package.php?p=xserver-xorg-video-vmware

make[3]: Entering directory '/<>/build/saa'
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../saa -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wpointer-arith 
-Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes 
-Wnested-externs -Wbad-function-cast -Wold-style-definition 
-Wdeclaration-after-statement -Wunused -Wuninitialized -Wshadow 
-Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls -Wlogical-op 
-Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main 
-Werror=missing-braces -Werror=sequence-point -Werror=return-type 
-Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address 
-Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing 
-fvisibility=hidden -I/usr/include/xorg -I/usr/include/pixman-1 
-I/usr/include/libdrm -I/usr/include/X11/dri -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o libsaa_la-saa.lo `test -f 'saa.c' || echo 
'../../saa/'`saa.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../saa -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 
-Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast 
-Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized 
-Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls 
-Wlogical-op -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main 
-Werror=missing-braces -Werror=sequence-point -Werror=return-type 
-Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address 
-Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing 
-fvisibility=hidden -I/usr/include/xorg -I/usr/include/pixman-1 
-I/usr/include/libdrm -I/usr/include/X11/dri -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c ../../saa/saa.c  -fPIC -DPIC -o .libs/libsaa_la-saa.o
../../saa/saa.c: In function 'saa_validate_gc':
../../saa/saa.c:399:31: error: implicit declaration of function 
'fbGetRotatedPixmap'; did you mean 'fbGetScreenPixmap'? 
[-Werror=implicit-function-declaration]
  PixmapPtr pRotatedTile = fbGetRotatedPixmap(pGC);
   ^~
   fbGetScreenPixmap
../../saa/saa.c:399:31: warning: nested extern declaration of 
'fbGetRotatedPixmap' [-Wnested-externs]
../../saa/saa.c:399:31: warning: initialization makes pointer from integer 
without a cast [-Wint-conversion]
In file included from ../../saa/saa.c:37:0:
../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier 
from pointer target type [-Wdiscarded-qualifiers]
  (priv)->saved_##mem = (real)->mem; \
  ^
../../saa/saa.c:424:5: note: in expansion of macro 'saa_swap'
 saa_swap(sgc, pGC, funcs);
 ^~~~
../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier 
from pointer target type [-Wdiscarded-qualifiers]
  (priv)->saved_##mem = (real)->mem; \
  ^
../../saa/saa.c:426:5: note: in expansion of macro 'saa_swap'
 saa_swap(sgc, pGC, funcs);
 ^~~~
../../saa/saa.c: In function 'saa_destroy_gc':
../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier 
from pointer target type [-Wdiscarded-qualifiers]
  (priv)->saved_##mem = (real)->mem; \
  ^
../../saa/saa.c:444:5: note: in expansion of macro 'saa_swap'
 saa_swap(sgc, pGC, funcs);
 ^~~~
../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier 
from pointer target type [-Wdiscarded-qualifiers]
  (priv)->saved_##mem = (real)->mem; \
  ^
../../saa/saa.c:446:5: note: in expansion of macro 'saa_swap'
 saa_swap(sgc, pGC, funcs);
 ^~~~
../../saa/saa.c: In function 'saa_change_gc':
../../saa/saa_priv.h:131:22: warning: assi

Bug#900095: FTBFS against xserver-xorg-core 1.20.0

[Michael Biebl]

Source: xserver-xorg-video-vmware
Version: 13.2.1-1
Severity: serious

The recent update of xserver-xorg-core to 1.20.0 makes the package
FTBFS as can be seen by the latest binNMU

https://buildd.debian.org/status/package.php?p=xserver-xorg-video-vmware

make[3]: Entering directory '/<>/build/saa'
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../saa -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wpointer-arith 
-Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes 
-Wnested-externs -Wbad-function-cast -Wold-style-definition 
-Wdeclaration-after-statement -Wunused -Wuninitialized -Wshadow 
-Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls -Wlogical-op 
-Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main 
-Werror=missing-braces -Werror=sequence-point -Werror=return-type 
-Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address 
-Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing 
-fvisibility=hidden -I/usr/include/xorg -I/usr/include/pixman-1 
-I/usr/include/libdrm -I/usr/include/X11/dri -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o libsaa_la-saa.lo `test -f 'saa.c' || echo 
'../../saa/'`saa.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../saa -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wpointer-arith -Wmissing-declarations -Wformat=2 
-Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Wbad-function-cast 
-Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized 
-Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls 
-Wlogical-op -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main 
-Werror=missing-braces -Werror=sequence-point -Werror=return-type 
-Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address 
-Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing 
-fvisibility=hidden -I/usr/include/xorg -I/usr/include/pixman-1 
-I/usr/include/libdrm -I/usr/include/X11/dri -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c ../../saa/saa.c  -fPIC -DPIC -o .libs/libsaa_la-saa.o
../../saa/saa.c: In function 'saa_validate_gc':
../../saa/saa.c:399:31: error: implicit declaration of function 
'fbGetRotatedPixmap'; did you mean 'fbGetScreenPixmap'? 
[-Werror=implicit-function-declaration]
  PixmapPtr pRotatedTile = fbGetRotatedPixmap(pGC);
   ^~
   fbGetScreenPixmap
../../saa/saa.c:399:31: warning: nested extern declaration of 
'fbGetRotatedPixmap' [-Wnested-externs]
../../saa/saa.c:399:31: warning: initialization makes pointer from integer 
without a cast [-Wint-conversion]
In file included from ../../saa/saa.c:37:0:
../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier 
from pointer target type [-Wdiscarded-qualifiers]
  (priv)->saved_##mem = (real)->mem; \
  ^
../../saa/saa.c:424:5: note: in expansion of macro 'saa_swap'
 saa_swap(sgc, pGC, funcs);
 ^~~~
../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier 
from pointer target type [-Wdiscarded-qualifiers]
  (priv)->saved_##mem = (real)->mem; \
  ^
../../saa/saa.c:426:5: note: in expansion of macro 'saa_swap'
 saa_swap(sgc, pGC, funcs);
 ^~~~
../../saa/saa.c: In function 'saa_destroy_gc':
../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier 
from pointer target type [-Wdiscarded-qualifiers]
  (priv)->saved_##mem = (real)->mem; \
  ^
../../saa/saa.c:444:5: note: in expansion of macro 'saa_swap'
 saa_swap(sgc, pGC, funcs);
 ^~~~
../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier 
from pointer target type [-Wdiscarded-qualifiers]
  (priv)->saved_##mem = (real)->mem; \
  ^
../../saa/saa.c:446:5: note: in expansion of macro 'saa_swap'
 saa_swap(sgc, pGC, funcs);
 ^~~~
../../saa/saa.c: In function 'saa_change_gc':
../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier 
from pointer target type [-Wdiscarded-qualifiers]
  (priv)->saved_##mem = (real)->mem; \
  ^
../../saa/saa.c:454:5: note: in expansion of macro 'saa_swap'
 saa_swap(sgc, pGC, funcs);
 ^~~~
../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier 
from pointer target type [-Wdiscarded-qualifiers]
  (priv)->saved_##mem = (real)->mem; \
  ^
../../saa/saa.c:456:5: note: in expansion of macro 'saa_swap'
 saa_swap(sgc, pGC, funcs);
 ^~~~
../../saa/saa.c: In function 'saa_copy_gc':
../../saa/saa_priv.h:131:22: warning: assignment discards 'const' qualifier 
from pointer target type [-Wdiscarded-qualifiers]
  (priv)->saved_##mem = (real)->mem; \
  ^
../../saa/saa.c:464:5: note: in expa

Bug#899124: fonts-font-awesome: completely breaks web applications, with no notice

[Pierre-Elliott Bécue]

Le mardi 22 mai 2018 à 21:16:14+0530, Vasudev Kamath a écrit :
> Hi Antonio,
> 
> Antonio Terceiro  writes:
> 
> > Control: forwarded -1 
> > https://salsa.debian.org/fonts-team/fonts-font-awesome/merge_requests/1
> >
> > On Sun, May 20, 2018 at 06:15:08PM -0300, Antonio Terceiro wrote:
> >> Control: reopen -1
> >> 
> >> On Sun, May 20, 2018 at 10:32:38PM +0530, Vasudev Kamath wrote:
> >> > Antonio Terceiro  writes:
> >> > > 2) revert the changes in fonts-font-awesome in unstable, upload the
> >> > > new release to experimental, and give people a few months to adapt.
> >> > 
> >> > I'm okay with this solution. I've currently fixed the broken links and
> >> > uploaded the fixes. If you would like more time to adapt to the version
> >> > 5 of font, I can request its removal from unstable and re-upload old
> >> > version to unstable and then upload this new version to experimental.
> >> 
> >> There is no such thing as requesting removal. you need to upload it with
> >> a higher version number, but with the old contents. Something like
> >> 5.0.10+really4.7.0-1.
> >> 
> >> Or maybe not. I will try if I can work things out with the new version,
> >> so expect a few patches.
> >> 
> >> For now I'm reopening this bug (which was not really fixed by your -3
> >> upload), and let's see what I can get.
> >
> > So here it is:
> > https://salsa.debian.org/fonts-team/fonts-font-awesome/merge_requests/1
> >
> > This merge request fixes usage of v5, and add a backwards compatibility
> > layer for the v4 when used with CSS (which was the only option in v4
> > AFAICT). It also adds autopkgtest to automatically test that the needed
> > files are in the right places both for v5 and for v4.
> 
> Thanks for this!. I've merged this and pushed new version to unstable.
> 
> >
> > LESS and SCSS are not handled.
> 
> Let's see if any one is really using them, if so we will get bug report.
> 
> Thanks and Warm Regards,

Hi,

I'm maintaining HyperKitty, and it relies on fontawesome-webfont.ttf and
FontAwesome.otf from the v4 version. To avoid shipping the files with the
package, I linked them from the debian's one in d/rules. (see [1])

Do we agree that there is no backward compability for such a case?

Cheers!

[1] 
https://salsa.debian.org/mailman-team/hyperkitty/blob/ad8b848059fcebe9392eeb79235297cf029051a9/debian/rules#L23

-- 
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#900089: [zfs-dkms]

[Antonio Russo]

What is the output of

# lsb_release -is

?

Bug#899466: marked as done (bzr-loom: Invalid maintainer address pkg-bazaar-ma...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 25 May 2018 22:17:46 +0100
with message-id <20180525211746.GA20451@blodeuwedd>
and subject line Migrated to alioth-lists.debian.net
has caused the Debian Bug report #899466,
regarding bzr-loom: Invalid maintainer address 
pkg-bazaar-ma...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bzr-loom
Version: 2.2.0-5
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of bzr-loom,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package bzr-loom since the list address
pkg-bazaar-ma...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-bazaar-ma...@lists.alioth.debian.org is 17.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
The pkg-bazaar-maint@ list has been migrated to alioth-lists.debian.net 
(thanks, Dominic!).


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

Bug#899875: marked as done (bzr-explorer: Invalid maintainer address pkg-bazaar-ma...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 25 May 2018 22:17:46 +0100
with message-id <20180525211746.GA20451@blodeuwedd>
and subject line Migrated to alioth-lists.debian.net
has caused the Debian Bug report #899875,
regarding bzr-explorer: Invalid maintainer address 
pkg-bazaar-ma...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bzr-explorer
Version: 1.3.0-2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of bzr-explorer,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package bzr-explorer since the list address
pkg-bazaar-ma...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-bazaar-ma...@lists.alioth.debian.org is 17.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
The pkg-bazaar-maint@ list has been migrated to alioth-lists.debian.net 
(thanks, Dominic!).


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

Bug#899886: marked as done (bzr-xmloutput: Invalid maintainer address pkg-bazaar-ma...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 25 May 2018 22:17:46 +0100
with message-id <20180525211746.GA20451@blodeuwedd>
and subject line Migrated to alioth-lists.debian.net
has caused the Debian Bug report #899886,
regarding bzr-xmloutput: Invalid maintainer address 
pkg-bazaar-ma...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bzr-xmloutput
Version: 0.8.8+bzr162-5
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of bzr-xmloutput,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package bzr-xmloutput since the list address
pkg-bazaar-ma...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-bazaar-ma...@lists.alioth.debian.org is 17.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
The pkg-bazaar-maint@ list has been migrated to alioth-lists.debian.net 
(thanks, Dominic!).


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

Bug#900046: marked as done (ifupdown doesn't work inside lxc)

[Debian Bug Tracking System]

Your message dated Fri, 25 May 2018 21:06:58 +
with message-id 
and subject line Bug#900046: fixed in ifupdown 0.8.34
has caused the Debian Bug report #900046,
regarding ifupdown doesn't work inside lxc
to be marked as done.

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

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


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

Package: ifupdown
Version: 0.8.33

upgrading from 0.8.32 to 0.8.33 ifupdown doesn't work anymore inside 
lxc. Downgrading fix the problem, but dpkg takes a lot in the set up phase.


BTW host is running 0.8.32

--
Ivan Sergio Borgonovo
https://www.webthatworks.it https://www.borgonovo.net
--- End Message ---
--- Begin Message ---
Source: ifupdown
Source-Version: 0.8.34

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

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

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

Debian distribution maintenance software
pp.
Guus Sliepen  (supplier of updated ifupdown package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 25 May 2018 22:34:33 +0200
Source: ifupdown
Binary: ifupdown
Architecture: source amd64
Version: 0.8.34
Distribution: unstable
Urgency: medium
Maintainer: Guus Sliepen 
Changed-By: Guus Sliepen 
Description:
 ifupdown   - high level tools to configure network interfaces
Closes: 900046
Changes:
 ifupdown (0.8.34) unstable; urgency=medium
 .
   [ Guus Sliepen ]
   * Handle SIGINT and SIGTERM more gracefully.
   * VLAN interfaces in the same allow class are now brought up automatically
 if the physical interface is brought up.
 .
   [ Antonio Terceiro ]
   * Don't call udevadm settle if udev is not installed. Closes: #900046
Checksums-Sha1:
 59b01f8474bfef92427484489878b0eec2e2df1d 1527 ifupdown_0.8.34.dsc
 eba2921b959857f0e1290eb9231720f2a99900db 82008 ifupdown_0.8.34.tar.xz
 5e6f843c6e0a44364dd2dfd691856801ce8c94ad 66044 ifupdown-dbgsym_0.8.34_amd64.deb
 7e828105826c54bd00e7b423d678acce6d5f0b1c 6770 ifupdown_0.8.34_amd64.buildinfo
 0fbee463b05ab0909319e907cdb8dd69ddac766d 82356 ifupdown_0.8.34_amd64.deb
Checksums-Sha256:
 6b3bd38277869a05c0f24252a750e31e34d295fb30251b90ff106ec6f17b8899 1527 
ifupdown_0.8.34.dsc
 8319961313d78320c8d0841ea9ca1490359a924d019df8e6d7cded86a1963cbd 82008 
ifupdown_0.8.34.tar.xz
 0b821ec62d68cdb2c49677a997e2bed2335170f85cf9d8dc93a5a9537ce3ecab 66044 
ifupdown-dbgsym_0.8.34_amd64.deb
 4b461a33c3d5f431e94a5ab8a31be3419783812a9747a2dc4620d66bb32f753b 6770 
ifupdown_0.8.34_amd64.buildinfo
 233fa6ebd63e4efa0ab8f469156945cfeed14fa808724b0040260e9fd8cb3d5f 82356 
ifupdown_0.8.34_amd64.deb
Files:
 8c96dcefe3ac09d79e61c7d436687e48 1527 admin important ifupdown_0.8.34.dsc
 7653c9df041b1392c438407780e52c1f 82008 admin important ifupdown_0.8.34.tar.xz
 9e0f3ea3961dc9f7300c62bff1536bef 66044 debug optional 
ifupdown-dbgsym_0.8.34_amd64.deb
 922465de40e716d7445324d5c1a7af7a 6770 admin important 
ifupdown_0.8.34_amd64.buildinfo
 69d726a84bdd32c65af735cbfc5e5b87 82356 admin important 
ifupdown_0.8.34_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEETRt3lsA+CDGZG91CP0kN64ce+foFAlsIc5sACgkQP0kN64ce
+fr64w/9HZV+FDAMTx+kaa0xNoFCI8TezuM7jREODR/rdy0FDJVvIAqiU5MIw6Oi
/Lsl5RUrJym1K+Jrq8GyR+4h+ZKPGddcZ3BHX4bUgTDaZEJvDr+v4BayKeKT6azu
zk4I9+Lzj7fJTO9eoEviM63SrqFncpOT79woMr59Wg/OWUXFxqZiEsj5rNjj14KO
iv5IIlgqKzAZ1Y1LcQvRboGsXLoQUhsDOk2m3rm/IiDXigrTvaONYXkJyGs0XRkK
yCQn8NVEu+LZ1oS7qjlA6mY3S53r3Wjd1NWiFmGljti4uASK1ySVK+koxzHnuhdV
M04l8hNjqklzAct8US2qVQN6q03x9VH9lJ0IMRNIV9ckdUEAiOVXk9nkuOrj06ya
JISEl3RPLchqfjDtHug6QJAr4AdbNUfZswkU4pPUGfbITA72yhpmsBgf6zCE6F4V
OR0NHQWF7rDD3SsbZUpEdZvRcLGEOZizY4K/UBsH1FDMCW+fjDE0ojvxhTu6Sdw2
eGhfAKN+okfGDQj/siR6/YkcRnk80YCE0/foiwidAxsDLW+WjQqRavw4pNENmDI3
1RXSMv/rhaTN5Rg4feCsHrG7BLxazudDRV/pW6aVne1L+sDF6rxWStQznAUvnPk6
fxu0L5yin1H0wwg142Aif+aAlRJ5lKZzsN2g/FW3XLZeGAT9IR0=
=f7/B
-END PGP SIGNATURE End Message ---

Bug#899496: marked as done (f2fs-tools: Invalid maintainer address filesystems-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 25 May 2018 21:58:49 +0100
with message-id <20180525205849.pqlxdvxiko3vn...@urchin.earth.li>
and subject line Re: Bug#899496: f2fs-tools: Invalid maintainer address 
filesystems-de...@lists.alioth.debian.org
has caused the Debian Bug report #899496,
regarding f2fs-tools: Invalid maintainer address 
filesystems-de...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:f2fs-tools
Version: 1.10.0-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of f2fs-tools,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package f2fs-tools since the list address
filesystems-de...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
filesystems-de...@lists.alioth.debian.org is 8.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Thu, May 24, 2018 at 02:03:52AM -0700, Vincent Cheng wrote:

> I'd like to volunteer to be the list owner for the filesystems-devel
> list and have the list migrated over to the alioth-lists service. What
> information do I need to provide to complete this migration? Thank
> you!

No more information, I've migrated the list and CCed the old owner
for the record.

Dominic.--- End Message ---

Bug#681726: Eclipse is 6 Years Behind in Debian

[Markus Koschany]

Hello,

Am 25.05.2018 um 21:50 schrieb Josh Blagden:
> Hi folks,
> 
>     I just wanted to make the observation that Debian has had the same
> version of Eclipse for the last six years. When can we expect to see a
> new version to the Debian repository?

Maybe when a solar and lunar eclipse happen at the same time.

On a more serious note, we do not intend to ship the current version
with Debian 10 "Buster" again because, as you have rightly observed, it
is obsolete and also broken. I recommend Debian bug #681726 for further
reading. [1]

I still intend to save parts of Eclipse (eclipse-platform) but will also
look into other alternatives to save aspectj and its
reverse-dependencies, whatever is easier to achieve. Though I have made
up my mind and I don't intend to maintain Eclipse and all plugin
packages alone for Buster. I will focus on Netbeans 9 as an alternative
IDE instead which hopefully requires less maintenance but this also
depends on whether it will be released in time before the next freeze.

So in short, we are aware of the situation but we could need more help
from people who really want to _maintain_ Eclipse.

I also thought about something that was discussed at DebConf17 in
Montreal, just packaging the upstream tarball as is. Obviously we can't
ship that in Debian main but we could provide a eclipse-downloader
package in contrib instead. I'm not sure if this is really needed or
desired because it shouldn't be too difficult to run the Eclipse
installer manually. Just a thought, not a promise.

Hope that helps clarifying the situation a little

Regards,

Markus

[1] https://bugs.debian.org/681726



signature.asc
Description: OpenPGP digital signature

Bug#900084: haproxy: CVE-2018-11469

[Salvatore Bonaccorso]

Source: haproxy
Version: 1.8.0-1
Severity: grave
Tags: patch security upstream fixed-upstream

Hi,

The following vulnerability was published for haproxy.

CVE-2018-11469[0]:
| Incorrect caching of responses to requests including an Authorization
| header in HAProxy 1.8.0 through 1.8.9 (if cache enabled) allows
| attackers to achieve information disclosure via an unauthenticated
| remote request, related to the proto_http.c
| check_request_for_cacheability function.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-11469
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11469
[1] 
https://git.haproxy.org/?p=haproxy-1.8.git;a=commit;h=17514045e5d934dede62116216c1b016fe23dd06

Regards,
Salvatore

Processed: notfixed 899773 in 0.12.0-1, notfixed 897000 in 3.1.0-1

[Debian Bug Tracking System]

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

> # do not confuse the bts with invalid bugs
> notfixed 899773 0.12.0-1
Bug #899773 {Done: Yves-Alexis Perez } [src:exo] exo: 
Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org
No longer marked as fixed in versions exo/0.12.0-1.
> notfixed 897000 3.1.0-1
Bug #897000 {Done: Gregor Riepl } [cura] cura: crash on 
startup
No longer marked as fixed in versions cura/3.1.0-1.
> thanks
Stopping processing here.

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

Bug#899475: marked as done (cjs: Invalid maintainer address pkg-cinnamon-t...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 25 May 2018 19:58:02 +0200
with message-id <20180525175800.m4gnc7y7yqpe4...@neoptolemo.gnuservers.com.ar>
and subject line Re: Bug#899475: cjs: Invalid maintainer address 
pkg-cinnamon-t...@lists.alioth.debian.org
has caused the Debian Bug report #899475,
regarding cjs: Invalid maintainer address 
pkg-cinnamon-t...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cjs
Version: 3.2.0-3
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of cjs,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package cjs since the list address
pkg-cinnamon-t...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-cinnamon-t...@lists.alioth.debian.org is 2.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


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

Version: 3.8.0-1

¡Hola Christoph!

El 2018-05-24 a las 09:43 +0200, Christoph Biedl escribió:

Package: src:cjs
Version: 3.2.0-3
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer


This is fixed in the experimental version.

Happy hacking,
--
"If I ask another professor what he teaches in the introductory programming 
course, whether he answers proudly "Pascal" or diffidently "FORTRAN," I know 
that he is teaching a grammar, a set of semantic rules, and some finished 
algorithms, leaving the students to discover, on their own, some process of 
design."

-- Robert W. Floyd
Saludos /\/\ /\ >< `/


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

Bug#899785: marked as done (exe-thumbnailer: Invalid maintainer address pkg-wine-pa...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 25 May 2018 17:35:11 +
with message-id 
and subject line Bug#899785: fixed in exe-thumbnailer 0.10.0-3
has caused the Debian Bug report #899785,
regarding exe-thumbnailer: Invalid maintainer address 
pkg-wine-pa...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:exe-thumbnailer
Version: 0.10.0-2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of exe-thumbnailer,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package exe-thumbnailer since the list address
pkg-wine-pa...@lists.alioth.debian.org used in the Maintainer: field
was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-wine-pa...@lists.alioth.debian.org is 1.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: exe-thumbnailer
Source-Version: 0.10.0-3

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

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

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

Debian distribution maintenance software
pp.
James Lu  (supplier of updated exe-thumbnailer 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 May 2018 12:39:21 -0700
Source: exe-thumbnailer
Binary: exe-thumbnailer gnome-exe-thumbnailer
Architecture: source
Version: 0.10.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Team 
Changed-By: James Lu 
Description:
 exe-thumbnailer - Windows executable (.exe, etc.) thumbnailer for Linux 
desktops
 gnome-exe-thumbnailer - transitional dummy package for exe-thumbnailer
Closes: 899785
Changes:
 exe-thumbnailer (0.10.0-3) unstable; urgency=medium
 .
   * debian/ packaging updates:
 - Update my email and copyright years.
 - Update maintainer email to the new Debian Wine list. (Closes: #899785)
 - Move Vcs-* fields to salsa.d.o
 - Bump standards version to 4.1.4, removing the obsolete get-orig-source
   rule accordingly.
 - Bump dh compat level to 11.
 - Add Enhances: pcmanfm-qt as that also supports freedesktop thumbnailers
Checksums-Sha1:
 b0a06710901f379e71fbfcdfc73f844fe36b33c5 2755 exe-thumbnailer_0.10.0-3.dsc
 4a7c19267a26f87ff4cd038f16f65721486d6b6e 4924 
exe-thumbnailer_0.10.0-3.debian.tar.xz
 e4ad36c755033c7c5cf6997359b67ae3ae300015 6289 
exe-thumbnailer_0.10.0-3_source.buildinfo
Checksums-Sha256:
 a406c2d3d9122f910109f6b7c0981924d65ee344ce9

Processed: severity of 900036 is important

[Debian Bug Tracking System]

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

> severity 900036 important
Bug #900036 [firmware-nonfree] firmware-nonfree: Buster kernel needs updated 
(upstream) firmware versions
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#900069: openmpi: mpicc/mpicxx comiler wrappers set rpath

[Matthias Maier]

On Fri, May 25, 2018, at 11:43 CDT, Graham Inggs  wrote:

> I hit this problem in 3.1.0-4 a few hours ago, before 3.1.0-5 was
> picked up by the mirrors.
>
> Are you sure this still occurs in 3.1.0-5?  Otherwise, this is a
> duplicate of #899391.

I don't think so. I have:

  # dpkg -l | grep libopenmpi
  ii libopenmpi-dev:amd64 3.1.0-5 amd64
  ii libopenmpi3:amd643.1.0-5 amd64

  #mpicc --showme
  gcc [...]
-Wl,-rpath -Wl,/usr/lib/x86_64-linux-gnu/openmpi/lib
-Wl,--enable-new-dtags -L/usr/lib/x86_64-linux-gnu/openmpi/lib [...]

Best,
Matthias

Bug#900073: clementine: fails to play anything: streaming stopped, reason not linked (-1)

[Sebastian Ramacher]

Package: clementine
Version: 1.3.1+git542-gf00d9727c+dfsg-1
Severity: grave

Since the last update clementine [1] refuses to play any files. clementine was 
able
to play these files in previously. I see the following error messages:

18:50:13.677 ERROR GstEnginePipeline:65212 "gstbaseparse.c(3611): 
gst_base_parse_loop (): 
/GstPipeline:pipeline/GstURIDecodeBin:uridecodebin-198/GstDecodeBin:decodebin13/GstFlacParse:flacparse13:\nstreaming
 stopped, reason not-linked (-1)"

(for flac files)

18:58:48.333 ERROR GstEnginePipeline:6521 "gstbaseparse.c(3611): 
gst_base_parse_loop (): 
/GstPipeline:pipeline/GstURIDecodeBin:uridecodebin-0/GstDecodeBin:decodebin1/GstMpegAudioParse:mpegaudioparse1:\nstreaming
 stopped, reason not-linked (-1)"

(for mp3 files)

Please let me know if you need any more information.

Cheers

[1] … not necessarily since the last clementine update. This could also be
releated to gstreamer 1.14.1.

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

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

Versions of packages clementine depends on:
ii  gstreamer1.0-plugins-base   1.14.1-1
ii  gstreamer1.0-plugins-good   1.14.1-1
ii  gstreamer1.0-plugins-ugly   1.14.1-1
ii  libc6   2.27-3
ii  libcdio17   1.0.0-2+b1
ii  libchromaprint1 1.4.3-2
ii  libcrypto++65.6.4-8
ii  libfftw3-double33.3.7-1+b1
ii  libgcc1 1:8.1.0-3
ii  libgdk-pixbuf2.0-0  2.36.11-2
ii  libglib2.0-02.56.1-2
ii  libgpod40.8.3-11
ii  libgstreamer-plugins-base1.0-0  1.14.1-1
ii  libgstreamer1.0-0   1.14.1-1
ii  libimobiledevice6   1.2.1~git20180302.3a37a4e-1
ii  libmtp9 1.1.13-1
ii  libmygpo-qt5-1  1.1.0-2
ii  libplist3   2.0.0-3
ii  libprojectm2v5  2.1.0+dfsg-4+b3
ii  libprotobuf10   3.0.0-9.1
ii  libpulse0   11.1-5
ii  libqt4-sql-sqlite   4:4.8.7+dfsg-17
ii  libqt5concurrent5   5.10.1+dfsg-7
ii  libqt5core5a5.10.1+dfsg-7
ii  libqt5dbus5 5.10.1+dfsg-7
ii  libqt5gui5  5.10.1+dfsg-7
ii  libqt5network5  5.10.1+dfsg-7
ii  libqt5opengl5   5.10.1+dfsg-7
ii  libqt5sql5  5.10.1+dfsg-7
ii  libqt5widgets5  5.10.1+dfsg-7
ii  libqt5x11extras55.10.1-2
ii  libqt5xml5  5.10.1+dfsg-7
ii  libsqlite3-03.23.1-1
ii  libstdc++6  8.1.0-3
ii  libtag1v5   1.11.1+dfsg.1-0.2+b1
ii  libx11-62:1.6.5-1
ii  projectm-data   2.1.0+dfsg-4
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages clementine recommends:
ii  gstreamer1.0-pulseaudio  1.14.1-1

Versions of packages clementine suggests:
ii  gstreamer1.0-plugins-bad  1.14.1-1

-- no debconf information

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#891994: Qt5 migration of EpiGrass? (Was: Bug#891994: epigrass: Depends on Qt4-only python-qwt5-qt4)

[Cláudia Torres Codeço]

Hi Andreas,

Thank you for the information. We do plan to work in the migration to Qt5.

best regards,

Claudia





De: Andreas Tille 
Enviado: sexta-feira, 25 de maio de 2018 09:14:51
Para: 891...@bugs.debian.org; Flávio Codeço Coelho; Cláudia Torres Codeço
Assunto: Qt5 migration of EpiGrass? (Was: Bug#891994: epigrass: Depends on 
Qt4-only python-qwt5-qt4)

Control: forwarded -1 Cláudia Torres Codeço , Flávio Codeço 
Coelho 
Control: tags -1 help
Control: tags -1 upstream

Hi Cláudia and Flávio,

the Debian package of EpiGrass received a serious bug report which means
that we can not distribute EpiGrass with the next Debian releas if it
will not be ported to Qt5.  I have not seen any update of EpiGrass since
Nov. 2016.  I would like to ask whether you intend to work on a Qt5
migration.

Kind regards and thanks for providing this useful tool as Free Software

 Andreas.

On Sat, Mar 03, 2018 at 09:23:29PM +0100, Andreas Beckmann wrote:
> Package: epigrass
> Version: 2.4.7-2
> Severity: serious
> Justification: blocks python-qwt5-qt4 removal
> Control: block 886779 with -1
>
> Hi,
>
> epigrass Depends on the Qt4-only python-qwt5-qt4 which is scheduled for
> removal (#886779). Please switch to a Qt5 solution or drop the
> Dependency altogether.
>
>
> Andreas
>
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
>

--
http://fam-tille.de

Bug#900069: openmpi: mpicc/mpicxx comiler wrappers set rpath

[Graham Inggs]

I hit this problem in 3.1.0-4 a few hours ago, before 3.1.0-5 was picked 
up by the mirrors.


Are you sure this still occurs in 3.1.0-5?  Otherwise, this is a 
duplicate of #899391.

Bug#900069: openmpi: mpicc/mpicxx comiler wrappers set rpath

[Matthias Maier]

Source: openmpi
Version: 3.1.0-5
Severity: serious
Tags: sid

Hi,

Openmpi version 3.1.0 (3.1.0-5) configures mpicc/mpicxx with an
rpath/new-dtags:

  $ mpicc --showme LINKER
  gcc LINKER [...]
-Wl,-rpath -Wl,/usr/lib/x86_64-linux-gnu/openmpi/lib
-Wl,--enable-new-dtags -L/usr/lib/x86_64-linux-gnu/openmpi/lib
[...]

With that every package that either uses the mpicc/mpicxx compiler
wrapper, or CMake (that queries the compiler wrapper) for compilation
now inadvertently sets an rpath (and gets rejected due to the
corresponding lintian check being fatal).

Best,
Matthias

Processed: Re: debian-installer: Installer showes Debootstrap Error debian stretch live installation

[Debian Bug Tracking System]

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

> retitle 866629 debian-installer: live installation without internet 
> connection fails with "failed to determine the codename for the release."
Bug #866629 [live-installer] debian-installer: Installer showes Debootstrap 
Error debian stretch live installation
Changed Bug title to 'debian-installer: live installation without internet 
connection fails with "failed to determine the codename for the release."' from 
'debian-installer: Installer showes Debootstrap Error debian stretch live 
installation'.
> thanks
Stopping processing here.

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

Bug#866629: debian-installer: Installer showes Debootstrap Error debian stretch live installation

[Chris Lamb]

retitle 866629 debian-installer: live installation without internet connection 
fails with "failed to determine the codename for the release."
thanks

(I've only skimmed the bug so only 80% sure it is internet connection-
related, but I think a rename might make it easier to find/parse at
the very least.)


Regards,

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

Processed: tagging 900051

[Debian Bug Tracking System]

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

> # stretch is not affected
> tags 900051 + sid buster
Bug #900051 [libgnupg-interface-perl] libgnupg-interface-perl: 
t/get_public_keys.t fails with gnupg2/2.2.7-1
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: Re: Bug#900051: libgnupg-interface-perl: t/get_public_keys.t fails with gnupg2/2.2.7-1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #900051 [libgnupg-interface-perl] libgnupg-interface-perl: 
t/get_public_keys.t fails with gnupg2/2.2.7-1
Severity set to 'serious' from 'important'

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

Bug#884481: marked as done (libbatik-java: Squiggle will not open files: access denied)

[Debian Bug Tracking System]

Your message dated Fri, 25 May 2018 13:19:42 +
with message-id 
and subject line Bug#884481: fixed in batik 1.10-1
has caused the Debian Bug report #884481,
regarding libbatik-java: Squiggle will not open files: access denied
to be marked as done.

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

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


-- 
884481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884481
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbatik-java
Version: 1.9-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Squiggle (svgbrowser) no longer opens svg files so is rendered useless.

$ squiggle spiro-swirls-smiley_Clipart_svg_File.svg 
java.security.AccessControlException: access denied ("java.net.NetPermission" 
"setDefaultAuthenticator")
at 
java.security.AccessControlContext.checkPermission(AccessControlContext.java:472)
at 
java.security.AccessController.checkPermission(AccessController.java:884)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:549)
at java.net.Authenticator.setDefault(Authenticator.java:127)
at org.apache.batik.apps.svgbrowser.Main.(Main.java:411)
at org.apache.batik.apps.svgbrowser.Main.main(Main.java:165)

The GUI shows this (roughly, I had to OCR it):

java.Security.AccessControlException: access denied ("java.io.FilePermission" 
"Spiro-Swirls-Smiley_Clipart_svg_File.svg" "read")
at 
java.Security.AccessControlConteM.checkPermiSSionIIAccessControlConteMJava:{U2}
at 
java.Security.AccessController.checkPermiSSioniAccessControllerJava:EH34)
at java.Iang.SecurityManager.checkPermiSSi0niSecurityManagerJava:549)
at java.Iang.SecurityManager.checkReadiSecurityManagerJava:EIEIEIII
at java.i0.File.isDirectoryIIFile.java:844)
at 
sun.netwww.protocol.file.FileURLConnection.connect(FileURLConnection.java:82)
at 
sun.netwww.protocol.file.FileURLConnection.getlnputStreamliFileURLConnection.java:18E!)
at 
org.apache.batik.util.ParsedURLData.openStreamInternalliParsedURLData.java:554)
at org.apache.batik.util.ParsedURLData.openStreamiParsedURLDataJava:4N3)
at org.apache.batik.util.ParsedURL.openStreamiParsedURLJava:441II
at 
org.apache.batik.anim.dom.SAXSVGDocumentFactory.createDocumentIISAXSVGDocumentFactory.java:l59)
at 
org.apache.batik.anim.dom.SAXSVGDocumentFactory.createSVGDocument(SAXSVGDocumentFactory.java:124)
at 
org.apache.batik.bridge.DocumentLoader.IoadDocumentiDocumentLoaderJava:106)
at 
org.apache.batik.swingsvg.SVGDocumentLoader.runliSVGDocumentLoader.java:84)


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

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

Versions of packages libbatik-java depends on:
ii  java-wrappers 0.2
ii  libjaxp1.3-java   1.3.05-2
ii  libxalan2-java2.7.2-1
ii  libxml-commons-external-java  1.4.01-2
ii  libxmlgraphics-commons-java   2.2-1

Versions of packages libbatik-java recommends:
ii  default-jre  2:1.8-59

Versions of packages libbatik-java suggests:
pn  jython 
ii  librhino-java  1.7.7.1-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: batik
Source-Version: 1.10-1

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

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

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated batik package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 May 2018 13:53:34 +0200
Source: batik
Binary: libbatik-java
Architecture: source
Version: 1.10-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libbatik-java - xml.apache.org SVG Library
Closes: 8

Processed: Re: ifupdown doesn't work inside lxc

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #900046 [ifupdown] ifupdown doesn't work inside lxc
Severity set to 'grave' from 'normal'

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

Processed: Qt5 migration of EpiGrass? (Was: Bug#891994: epigrass: Depends on Qt4-only python-qwt5-qt4)

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 Cláudia Torres Codeço , Flávio Codeço Coelho 
> 
Bug #891994 [epigrass] epigrass: Depends on Qt4-only python-qwt5-qt4
Set Bug forwarded-to-address to 'Cláudia Torres Codeço , 
Flávio Codeço Coelho '.
> tags -1 help
Bug #891994 [epigrass] epigrass: Depends on Qt4-only python-qwt5-qt4
Added tag(s) help.
> tags -1 upstream
Bug #891994 [epigrass] epigrass: Depends on Qt4-only python-qwt5-qt4
Added tag(s) upstream.

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

Bug#891994: Qt5 migration of EpiGrass? (Was: Bug#891994: epigrass: Depends on Qt4-only python-qwt5-qt4)

[Andreas Tille]

Control: forwarded -1 Cláudia Torres Codeço , Flávio Codeço 
Coelho 
Control: tags -1 help
Control: tags -1 upstream

Hi Cláudia and Flávio,

the Debian package of EpiGrass received a serious bug report which means
that we can not distribute EpiGrass with the next Debian releas if it
will not be ported to Qt5.  I have not seen any update of EpiGrass since
Nov. 2016.  I would like to ask whether you intend to work on a Qt5
migration.

Kind regards and thanks for providing this useful tool as Free Software

 Andreas.

On Sat, Mar 03, 2018 at 09:23:29PM +0100, Andreas Beckmann wrote:
> Package: epigrass
> Version: 2.4.7-2
> Severity: serious
> Justification: blocks python-qwt5-qt4 removal
> Control: block 886779 with -1
> 
> Hi,
> 
> epigrass Depends on the Qt4-only python-qwt5-qt4 which is scheduled for
> removal (#886779). Please switch to a Qt5 solution or drop the
> Dependency altogether.
> 
> 
> Andreas
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> 

-- 
http://fam-tille.de

Bug#900059: libgit2: Testsuite failure due to alignment-related crashes

[John Paul Adrian Glaubitz]

Source: libgit2
Version: 0.23.1-1
Severity: serious
Tags: patch upstream
Justification: fails to build from source
User: debian-sp...@lists.debian.org
Usertags: sparc64

Hello!

libgit2's testsuite fails because of an unaligned access which affects
both mipsel (and mips64el in experimental) as well as sparc64:

Test project /<>/libgit2-0.26.0+dfsg.1/build-debian-release
Start 1: libgit2_clar
Start 2: libgit2_clar-cred_callback
Start 3: libgit2_clar-proxy_credentials_in_url
Start 4: libgit2_clar-proxy_credentials_request
1/4 Test #3: libgit2_clar-proxy_credentials_in_url    Passed0.07 sec
2/4 Test #2: libgit2_clar-cred_callback ...   Passed0.07 sec
3/4 Test #4: libgit2_clar-proxy_credentials_request ...   Passed0.07 sec
4/4 Test #1: libgit2_clar .***Exception: Bus error 
60.88 sec
Loaded 338 suites: 
Started

I have written a patch to address this issue which I have sent upstream [1]. I
am attaching the patch to this bug report so you can include it with the
Debian package.

However, I think you will have to update the libgit2 version in experimental
anyway as there are still some unrelated testsuite failures in that version
which are not caused by unaligned access.

Adrian

> [1] https://github.com/libgit2/libgit2/pull/4655

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
>From 2ce5a21f46e78cdc3f04cb783e372828494199d5 Mon Sep 17 00:00:00 2001
From: John Paul Adrian Glaubitz 
Date: Fri, 25 May 2018 01:41:33 +0200
Subject: [PATCH] index: Fix alignment issues in write_disk_entry()

In order to avoid alignment issues on certain target architectures,
it is necessary to use memcpy() when modifying elements of a struct
inside a buffer returned by git_filebuf_reserve().
---
 src/index.c | 42 +-
 1 file changed, 21 insertions(+), 21 deletions(-)

diff --git a/src/index.c b/src/index.c
index a867547fb..3dcb6dde7 100644
--- a/src/index.c
+++ b/src/index.c
@@ -2605,7 +2605,7 @@ static bool is_index_extended(git_index *index)
 static int write_disk_entry(git_filebuf *file, git_index_entry *entry, const 
char *last)
 {
void *mem = NULL;
-   struct entry_short *ondisk;
+   struct entry_short ondisk;
size_t path_len, disk_size;
int varint_len = 0;
char *path;
@@ -2633,9 +2633,7 @@ static int write_disk_entry(git_filebuf *file, 
git_index_entry *entry, const cha
if (git_filebuf_reserve(file, &mem, disk_size) < 0)
return -1;
 
-   ondisk = (struct entry_short *)mem;
-
-   memset(ondisk, 0x0, disk_size);
+   memset(mem, 0x0, disk_size);
 
/**
 * Yes, we have to truncate.
@@ -2647,30 +2645,32 @@ static int write_disk_entry(git_filebuf *file, 
git_index_entry *entry, const cha
 *
 * In 2038 I will be either too dead or too rich to care about this
 */
-   ondisk->ctime.seconds = htonl((uint32_t)entry->ctime.seconds);
-   ondisk->mtime.seconds = htonl((uint32_t)entry->mtime.seconds);
-   ondisk->ctime.nanoseconds = htonl(entry->ctime.nanoseconds);
-   ondisk->mtime.nanoseconds = htonl(entry->mtime.nanoseconds);
-   ondisk->dev = htonl(entry->dev);
-   ondisk->ino = htonl(entry->ino);
-   ondisk->mode = htonl(entry->mode);
-   ondisk->uid = htonl(entry->uid);
-   ondisk->gid = htonl(entry->gid);
-   ondisk->file_size = htonl((uint32_t)entry->file_size);
+   ondisk.ctime.seconds = htonl((uint32_t)entry->ctime.seconds);
+   ondisk.mtime.seconds = htonl((uint32_t)entry->mtime.seconds);
+   ondisk.ctime.nanoseconds = htonl(entry->ctime.nanoseconds);
+   ondisk.mtime.nanoseconds = htonl(entry->mtime.nanoseconds);
+   ondisk.dev = htonl(entry->dev);
+   ondisk.ino = htonl(entry->ino);
+   ondisk.mode = htonl(entry->mode);
+   ondisk.uid = htonl(entry->uid);
+   ondisk.gid = htonl(entry->gid);
+   ondisk.file_size = htonl((uint32_t)entry->file_size);
 
-   git_oid_cpy(&ondisk->oid, &entry->id);
+   git_oid_cpy(&ondisk.oid, &entry->id);
 
-   ondisk->flags = htons(entry->flags);
+   ondisk.flags = htons(entry->flags);
 
if (entry->flags & GIT_IDXENTRY_EXTENDED) {
-   struct entry_long *ondisk_ext;
-   ondisk_ext = (struct entry_long *)ondisk;
-   ondisk_ext->flags_extended = htons(entry->flags_extended &
+   struct entry_long ondisk_ext;
+   memcpy(&ondisk_ext, &ondisk, sizeof(struct entry_short));
+   ondisk_ext.flags_extended = htons(entry->flags_extended &
GIT_IDXENTRY_EXTENDED_FLAGS);
-   path = ondisk_ext->path;
+   memcpy(mem, &ondisk_ext, sizeof(struct entry_long));
+   path = ((struct entry_long*)mem)->path;

Bug#899775: mc: Invalid maintainer address pkg-mc-de...@lists.alioth.debian.org

[Andreas Tille]

Uh, somebody did not answer the call to salvage this list

Should we try to ask alioth-lists admins?  Any other idea how to
communicate about mc

Kind regards

Andreas.


-- 
http://fam-tille.de

Bug#873341: Any news for this issue?

[Andreas Tille]

Hi,

I once libscala-pickling-java and I wonder whether I could provide any
help.  I'd love to finalise the project that made me stumbling about sbt
last year.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#897436: marked as done (broken nautilus integration)

[Debian Bug Tracking System]

Your message dated Fri, 25 May 2018 11:06:18 +
with message-id 
and subject line Bug#897436: fixed in owncloud-client 2.4.1+dfsg-1.1
has caused the Debian Bug report #897436,
regarding broken nautilus integration
to be marked as done.

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

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


-- 
897436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nautilus-owncloud
Version: 2.4.1+dfsg-1
Severity: serious

I can't pinpoint it to an exact update, but I noticed that the
owncloud/nextcloud nautilus integration no longer works.

When I start nautilus from the command line, I get:
$ nautilus
sys:1: PyGIWarning: Nautilus was imported without specifying a version first. 
Use gi.require_version('Nautilus', '3.0') before import to ensure that the 
right version gets loaded.
Initializing ownCloud-client-nautilus extension
Socket File: /run/user/1000/ownCloud/socket
Setting connected to True.
Socket watch id: 13
Server response: REGISTER_PATH:/mnt/data/ownCloud
Server response: GET_STRINGS:BEGIN
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/gi/overrides/GLib.py", line 668, in 

func_fdtransform = lambda _, cond, *data: callback(channel, cond, *data)
  File "/usr/share/nautilus-python/extensions/syncstate-ownCloud.py", line 131, 
in _handle_notify
self._handle_server_response(l.decode())
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 30: 
ordinal not in range(128)

I'm filing this with RC severity, as this basically makes
nautilus-owncloud unusable.

If you need further information, please ask.

Regards,
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.15.0-3-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 nautilus-owncloud depends on:
ii  nautilus  3.26.3.1-1
ii  owncloud-client   2.4.1+dfsg-1
ii  owncloud-client-data  2.4.1+dfsg-1
ii  python-nautilus   1.1-6
ii  python3   3.6.5-3

nautilus-owncloud recommends no packages.

Versions of packages nautilus-owncloud suggests:
pn  nautilus-script-manager  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: owncloud-client
Source-Version: 2.4.1+dfsg-1.1

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

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

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

Debian distribution maintenance software
pp.
Pierre-Elliott Bécue  (supplier of updated owncloud-client 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 24 May 2018 03:40:48 +0200
Source: owncloud-client
Binary: owncloud-client owncloud-client-doc libowncloudsync0 
libowncloudsync-dev owncloud-client-data owncloud-client-l10n 
owncloud-client-cmd dolphin-owncloud nautilus-owncloud nemo-owncloud 
caja-owncloud
Architecture: source
Version: 2.4.1+dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: ownCloud for Debian maintainers 

Changed-By: Pierre-Elliott Bécue 
Description:
 caja-owncloud - ownCloud integration for Caja
 dolphin-owncloud - ownCloud integration for Dolphin
 libowncloudsync-dev - development files for owncloudsync
 libowncloudsync0 - ownCloudSync folder synchronization - libraries
 nautilus-owncloud - ownCloud integration for Nautilus
 nemo-owncloud - ownCloud integration for Nemo
 owncloud-client - folder synchronization with an ownCloud server - GUI
 owncloud-client-cmd - folder synchronization with an ownCloud server - cmd 
client
 owncloud-client-data - ownCloudSync folder synchronization - shared data
 owncloud-client-doc - ownCloudSync folder synchronization - documentation
 owncloud-client-l10n - ownCloudSync folder synchronization - localization
Closes: 897436
Changes:
 owncloud-client (2.4.1+dfsg-1.1) unstable; urgency=med

Bug#890993: (Bug#890993) primer3 FTBFS on big endian: test failure

[Andreas Tille]

Hi Liubov,

On Fri, May 25, 2018 at 12:36:54PM +0200, Liubov Chuprikova wrote:
> I tried to figure out what exactly could cause the failure. The error
> refers to the test files in the kmer_lists directory that are in binary
> format. It seems they were generated on a little-endian architecture, that
> is why the test fails on big-endian when it tries to verify the file by
> comparing its first bytes with a given magic.
> 
> kmer_list/readme.txt says that the test files could be downloaded from
> http://primer3.ut.ee/lists.htm, which says the files can also be created by
> *glistmaker* from GenomeTester4 package.
> 
> So one solution could be to generate a set of similar test files for
> big-endian architectures. For this, only genome sequences in Fasta format
> would be necessary. But at this point, I get stuck as I have never faced a
> need to emulate big-endian. Are there other ways to deal with that type of
> problem?

While I think your suggestion is the proper solution I do not think that
it is worth the effort.  I would rather do the following:

  1. Exclude those test that are failing (it is only a small number)
 for the architectures where the test fails).  Please do not hesitate
 to ask here if you are lacking ideas how to do this.  May be the
 python-cogent package can serve as an exemple.  Its probably
 sufficient to do something like this:

  override_dh_auto_test:
ifeq ($(BUILDARCH),...)
  mkdir tempdir
  mv test/... tempdir
endif
  dh_auto_test --sourcedirectory=test
  dh clean --sourcedirectory=test
ifeq ($(BUILDARCH),...)
  move back files to restore original source state
  rmdir tempdir
endif

  2. Since you have saved time to work out proper tests on rarely
 used architectures you have time to package
   https://github.com/bioinfo-ut/GenomeTester4

While the later is half joking this could be quite useful.  You would
have need the tool for your original plan - may be for other things as
well and you could learn packaging.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#900032: [Pkg-javascript-devel] Bug#900032: mocha: missing-copyright-file /usr/share/doc/mocha/copyright

[Bastien ROUCARIES]

Hi,

I am really clueless. You are right but it will do this only with upgrade.

I have used correctly dpkg-maintscript-helper.

Could you crosscheck, my script ?

Bastien

On Thu, May 24, 2018 at 11:58 PM, Thorsten Glaser  wrote:
> Package: mocha
> Version: 4.1.0+ds1-1
> Severity: serious
> Justification: Policy 12.5
>
> Adequate reports:
>
> mocha: missing-copyright-file /usr/share/doc/mocha/copyright
>
> And adequate is right, as /usr/share/doc/mocha/ is empty.
>
> -- System Information:
> Debian Release: buster/sid
>   APT prefers unreleased
>   APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 
> 'unstable'), (100, 'experimental')
> Architecture: x32 (x86_64)
> Foreign Architectures: i386, amd64
>
> Kernel: Linux 4.15.0-1-amd64 (SMP w/8 CPU cores)
> Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=C 
> (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/lksh
> Init: sysvinit (via /sbin/init)
>
> Versions of packages mocha depends on:
> ii  dpkg   1.19.0.5+b1
> ii  libjs-mocha4.1.0+ds1-1
> ii  node-browser-stdout1.3.0-1
> ii  node-commander 2.12.2-1
> ii  node-debug 3.1.0-2
> ii  node-diff  1.4.0~dfsg-1
> ii  node-escape-string-regexp  1.0.5-1
> ii  node-glob  7.1.2-6
> ii  node-growl 1.7.0-1
> ii  node-he1.1.1-1
> ii  node-mkdirp0.5.1-1
> ii  node-supports-color4.4.0-2
> ii  nodejs 10.1.0~dfsg-1
> ii  oxygen-icon-theme  5:5.46.0-1
>
> mocha recommends no packages.
>
> mocha suggests no packages.
>
> -- no debconf information
>
> --
> Pkg-javascript-devel mailing list
> pkg-javascript-de...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Bug#890993: (Bug#890993) primer3 FTBFS on big endian: test failure

[Liubov Chuprikova]

Hi Andreas, Hi all,

I tried to figure out what exactly could cause the failure. The error
refers to the test files in the kmer_lists directory that are in binary
format. It seems they were generated on a little-endian architecture, that
is why the test fails on big-endian when it tries to verify the file by
comparing its first bytes with a given magic.

kmer_list/readme.txt says that the test files could be downloaded from
http://primer3.ut.ee/lists.htm, which says the files can also be created by
*glistmaker* from GenomeTester4 package.

So one solution could be to generate a set of similar test files for
big-endian architectures. For this, only genome sequences in Fasta format
would be necessary. But at this point, I get stuck as I have never faced a
need to emulate big-endian. Are there other ways to deal with that type of
problem?

With regards,
Liubov

Bug#897691: marked as done (python3-hbmqtt: overly generic python module name: /usr/lib/python3/dist-packages/scripts/__init__.py)

[Debian Bug Tracking System]

Your message dated Fri, 25 May 2018 10:05:23 +
with message-id 
and subject line Bug#897691: fixed in python-hbmqtt 0.9.2-2
has caused the Debian Bug report #897691,
regarding python3-hbmqtt: overly generic python module name: 
/usr/lib/python3/dist-packages/scripts/__init__.py
to be marked as done.

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

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


-- 
897691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897691
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-hbmqtt
Version: 0.9.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package uses a very generic
python module name that now clashes with other packages:

/usr/lib/python3/dist-packages/scripts/__init__.py


Andreas
--- End Message ---
--- Begin Message ---
Source: python-hbmqtt
Source-Version: 0.9.2-2

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

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

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

Debian distribution maintenance software
pp.
Stein Magnus Jodal  (supplier of updated python-hbmqtt 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 May 2018 11:30:53 +0200
Source: python-hbmqtt
Binary: python3-hbmqtt
Architecture: source all
Version: 0.9.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Stein Magnus Jodal 
Description:
 python3-hbmqtt - MQTT client/broker for asyncio
Closes: 897691
Changes:
 python-hbmqtt (0.9.2-2) unstable; urgency=medium
 .
   * debian/control
 - Remove redundant X-Python3-Version
   * debian/patches/
 - Add patch to remove the `scripts` module (closes: 897691)
Checksums-Sha1:
 4ef4afb0fdbcb588deb032e407516cbc71f915c4 2153 python-hbmqtt_0.9.2-2.dsc
 0f166894930af521b9d56f4533181973db4ccc69 2960 
python-hbmqtt_0.9.2-2.debian.tar.xz
 c37ecce7bef66b64874f7bc95acb30e79979f1f1 6624 
python-hbmqtt_0.9.2-2_amd64.buildinfo
 06a239f34ff50e73e8c20f726f1991d26c3a5477 35288 python3-hbmqtt_0.9.2-2_all.deb
Checksums-Sha256:
 92d09746260f2a05bea3056a3a276557ad78527b3dd6c56a1b7646740e2bc058 2153 
python-hbmqtt_0.9.2-2.dsc
 7af6ba7f9f1be51dfe71b11f957251a13dfa8a9945ed5f8eccf5d4e58741721f 2960 
python-hbmqtt_0.9.2-2.debian.tar.xz
 f3e101834da30d69b4f22db08eec237bf1128b197efefac3f0ec1ff2b45e0575 6624 
python-hbmqtt_0.9.2-2_amd64.buildinfo
 07bb2de7bc58eaef9159d4b6e1819649fa8e61e0693f429cea34426836cd0bf2 35288 
python3-hbmqtt_0.9.2-2_all.deb
Files:
 42af05a625f4c413740b2a98d1252c67 2153 python optional python-hbmqtt_0.9.2-2.dsc
 503daccef11fc0b0b6468a357779c786 2960 python optional 
python-hbmqtt_0.9.2-2.debian.tar.xz
 cc9bd3ef17f4291cd11543ec346a522a 6624 python optional 
python-hbmqtt_0.9.2-2_amd64.buildinfo
 680064c7cb714eab8b53a7da8d3c5b02 35288 python optional 
python3-hbmqtt_0.9.2-2_all.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEgKr0kHY4JR8IscpGILTH9aF8WPYFAlsH264RHGpvZGFsQGRl
Ymlhbi5vcmcACgkQILTH9aF8WPb3vg/+NCT+NDDfYivGAeygTAoCcVstcUDvYA1E
P2veaRYZTfF+CX6/0348U1mySEsQmRJAYowmgrl9X0oZfbzukxsIyjz8wrqz15yy
SACY40LnvLiyk/oytznVsGUdXli8uQdplhUV9xAVDWbewQNBzrMBcepeUI5YhEOx
/fI45fVtvMlbelQzIE2tmqWyK7O+HrNjtScXlCLZUiKJvv2KyPP8PxaEz9VZyXNT
IDsc4ZFe4l6VLg+MyVx6lVhSPaGWM2dadfr7jxF7ehPXHVdA96rQqnKKR7v3FdSP
uOXhmpXFnXgImEOJJNvO4PF8a1AibnJNTKST2CvazglS3j38TcDGvzEZL4FOK6pi
ybU2rxlCgBRlQbYsgKqNR7V3FWI1wyMAJMTe6pZFgEa6wYEVMnQEEFVVT27dpAlG
9sbpqLATJVL976y95dWi73a+WwIYVBYahQOgiEgVaYaT66w7fHu4XxIDwJfqFW/3
B66uyygXkR0ruc/DXlvyIksoC8oc0etgAZoj9cledHi1XhKsgbgmw3jQmMwiSPH4
dwlsqe/o9mR11kf9YqmsVphLSZlBAFUB8Gh54kOMLkombZHYPtHPrbCCneqN8FvL
2y3AyIgDAtnhJmmlabgev/Fn4ibuEfCfXLZE/qoY/MreEJPygGdehEqP8hgJrNLf
qFpWN0Jvw6M=
=OYSi
-END PGP SIGNATURE End Message ---

Processed: severity of libghc-cmark-gdm-dev is RC, breaks pandoc

[Debian Bug Tracking System]

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

> severity 897001 serious
Bug #897001 [libghc-cmark-gfm-dev] libghc-cmark-gfm-dev: not big-endian-safe
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#895612: marked as done (haskell-protobuf: FTBFS: testCase import ambiguity)

[Debian Bug Tracking System]

Your message dated Fri, 25 May 2018 09:49:39 +
with message-id 
and subject line Bug#895612: fixed in haskell-protobuf 0.2.1.1-4
has caused the Debian Bug report #895612,
regarding haskell-protobuf: FTBFS: testCase import ambiguity
to be marked as done.

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

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


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

https://github.com/alphaHeavy/protobuf/issues/35
--- End Message ---
--- Begin Message ---
Source: haskell-protobuf
Source-Version: 0.2.1.1-4

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

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

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

Debian distribution maintenance software
pp.
Clint Adams  (supplier of updated haskell-protobuf package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 06 May 2018 22:10:23 -0400
Source: haskell-protobuf
Binary: libghc-protobuf-dev libghc-protobuf-prof libghc-protobuf-doc
Architecture: source
Version: 0.2.1.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Clint Adams 
Description:
 libghc-protobuf-dev - ${haskell:ShortDescription}${haskell:ShortBlurb}
 libghc-protobuf-doc - ${haskell:ShortDescription}${haskell:ShortBlurb}
 libghc-protobuf-prof - ${haskell:ShortDescription}${haskell:ShortBlurb}
Closes: 895612
Changes:
 haskell-protobuf (0.2.1.1-4) unstable; urgency=medium
 .
   [ Clint Adams ]
   * Set Rules-Requires-Root to no.
 .
   [ Steve Langasek ]
   * d/p/0001-Fix-compilation-on-GHC-8.0.patch,
 d/p/0002-Fix-tests-compilation.patch: cherry-pick from upstream to fix
 compilation with ghc 8.2.  Closes: #895612.
 .
   [ Gianfranco Costamagna ]
   * Upload to unstable
Checksums-Sha1:
 fe7af10a315b1ca18bd677d684288161780375c9 3023 haskell-protobuf_0.2.1.1-4.dsc
 2c5bbe4b49a5ab44545404871eb1e9afdc01bc9c 4864 
haskell-protobuf_0.2.1.1-4.debian.tar.xz
 5c5be02f4318fe6547677e44b06b9c6109f8bec9 9132 
haskell-protobuf_0.2.1.1-4_source.buildinfo
Checksums-Sha256:
 cb4ebaa5ec3a97e17322ac9b76ef7640685a1b4057a8277a377a10da816e9603 3023 
haskell-protobuf_0.2.1.1-4.dsc
 989389a02af2d068c7f7348b77ccbb917c5cb4d043285a846d3303026c8c7ea3 4864 
haskell-protobuf_0.2.1.1-4.debian.tar.xz
 86d2252296e90c99ff0e7b104595c40a653c53c38454daa3c8215b1c6192b1bf 9132 
haskell-protobuf_0.2.1.1-4_source.buildinfo
Files:
 5aa368da76bc07ba1bbda3d095a4a786 3023 haskell optional 
haskell-protobuf_0.2.1.1-4.dsc
 88873cb8366c98a291a44461b2038d27 4864 haskell optional 
haskell-protobuf_0.2.1.1-4.debian.tar.xz
 af4547bb2b821a6bb69e1480f889844b 9132 haskell optional 
haskell-protobuf_0.2.1.1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJbB9sMAAoJEPNPCXROn13Z4y4P/AxTp98EwfeGcsSHNMf25iJy
EjtqIIeJ71KLavt9ElD/neRnjniACQPP42eFkuLiGxPAvpsiXVgCsKpbXd9jYarA
RoYuRT4suAqUIZlcmU7BhYqP43DydjAiEBV1me8F1NL2TGor8sXHlVu1MPP2zCwr
Lg/P8ADsM8GOHWPEt/GEpf3SE4JebW6Mq0ZHP7qB8qaTBDOeoP9Jrbx22ROeDWbU
Ns9zY4eSrphzxOEnIh9w9QlXaSZIZii9YDqheJYqdiu5j16Lyn9QFZhPFXGQ0PR9
+6AxcS6mEyQH0MlR8ut5RR0kwNDHH7qwOubXvgmMuwZS/ZWpu+mPNaiLeDUn40EU
2ldy8z80l9ZGCDPG8sqvnrKLotdCfdCf4USkHDl1HH8E7z0ToPibtMn7+N45FvHi
so34ICCUL8Adt9tDRSNz964H+oUedZBugLncqUluztvUXZmEv0XCS/BAGq4fSGJ3
BEqu8iX0+yXq20YnFgoQyCTkCrr1LMYR9WNjcS/199TRq7Z/oUvWySYT6LmVpkG8
h84xT2OIJV2shDo6jUJFDdHh+VNK5WeYBxV8MAnPVZDJyYDl2/FMLd6YU24+CS4c
9/9X6zBCTvd+t2tZlETbn1xSi+6tzk+72SiuUYtEAeAqjCaT7inCL/wpxQG6wLS0
qrvSGlz9N1t421ukLy2/
=pRZ5
-END PGP SIGNATURE End Message ---

Bug#894333: marked as done (torbrowser-launcher: Should recommend rebooting when upgrading to >= 0.2.9-2~ for the first time)

[Debian Bug Tracking System]

Your message dated Fri, 25 May 2018 09:36:20 +
with message-id 
and subject line Bug#894333: fixed in torbrowser-launcher 0.2.9-3
has caused the Debian Bug report #894333,
regarding torbrowser-launcher: Should recommend rebooting when upgrading to >= 
0.2.9-2~ for the first time
to be marked as done.

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

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


-- 
894333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894333
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: torbrowser-launcher
Version: 0.2.9-2
Severity: serious

Hi,

I see an upstream PR of mine
(https://github.com/micahflee/torbrowser-launcher/pull/310) has been
applied to 0.2.9-2 but the recommendations included in there for
package maintainers were not followed (see e.g. commit d62a69).

Let's fix that before the package makes it into testing and
stretch-backports. I suggest adding a NEWS.Debian entry that strongly
recommends users to reboot their system after upgrading to >= 0.2.9-2~.

Ideally, a postinst snippet would detect whether we're upgrading to
a version >= 0.2.9-2~ for the first time and if so, display the same
recommendation (in a non-interactive way). But let's not block on
that :)

Cheers,
-- 
intrigeri
--- End Message ---
--- Begin Message ---
Source: torbrowser-launcher
Source-Version: 0.2.9-3

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

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

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

Debian distribution maintenance software
pp.
intrigeri  (supplier of updated torbrowser-launcher 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 25 May 2018 09:12:30 +
Source: torbrowser-launcher
Binary: torbrowser-launcher
Architecture: source
Version: 0.2.9-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers 

Changed-By: intrigeri 
Closes: 894333
Description: 
 torbrowser-launcher - helps download and run the Tor Browser Bundle
Changes:
 torbrowser-launcher (0.2.9-3) unstable; urgency=medium
 .
   * Team upload.
   * NEWS.Debian: recommend rebooting the system after upgrading to 0.2.9-2
 (Closes: #894333)
   * Update Vcs-* control fields wrt. the move to Salsa.
Checksums-Sha1: 
 cfef26533d26de27c7438d23bf45ad9784fc2f26 2211 torbrowser-launcher_0.2.9-3.dsc
 ee5c294b5f6bc581829a9abc6825e5d68c6376b1 13568 
torbrowser-launcher_0.2.9-3.debian.tar.xz
Checksums-Sha256: 
 68fcea00502dd4d6d1f9d90bb3c6bf8e622730336c9127848d40b95276433fa2 2211 
torbrowser-launcher_0.2.9-3.dsc
 5fa5371a597a6ab3fbba0a63262b07d82879a5e2bd2e0c03de43028762d48745 13568 
torbrowser-launcher_0.2.9-3.debian.tar.xz
Files: 
 3dd2cf0ac0efad3af87b6f181dcc2ae4 2211 contrib/web optional 
torbrowser-launcher_0.2.9-3.dsc
 aa82d12750dd78533f827c5e3955cfb8 13568 contrib/web optional 
torbrowser-launcher_0.2.9-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEcMAxqZeuB0p8dimNy2kI2AAOzf4FAlsH1NUACgkQy2kI2AAO
zf4gMw/8D1UAWhqP/l0VgGpgEL20WYhfCbybUUH/FJGwuJ5PxBYrwyihs6n3CwlA
eiBBrAvFhpk/U/AQsnmbWDzUqizDiCxVP/CWcKH39sLOcn/KTccQf9yb4gMeW1ZX
kLWnCD7TfrUBPMZDIy91rrzMucfz94txEdQvpfMhlXUBSGmO26ueFYTApn1kzAXW
31rW3cYZ9NNQRkw8jCCRRWx1rMbTpb5N+DecXhQs8edbJuLCM+dz6YSLnRpnDbuz
q9T1j5gF0AwCW2oyOnvR+GnNc5H4x8+bMkuU344UmhWddAVCk/RZX1xLs6rHi0mG
uAZTg9dren0gdGcnRdBnU5vXfrDQmlFu0N5h9+YLHQu2WL+d8xn3PFtquLOCWsUL
wcAeo8T3fdP755p7c2itxJ4tI8i8Mx3YvVK1Rl5AS7Mv1lG5SdyNbpmjGj2RNkhx
/NVBpZbSO83YH9o0maByw4nndCcWMCLKGcyAZ/TCDpJjVMEbKxgfcX756SlLdUN7
Es7LsW7CDJ2qzKBoBORi9h7V/groZpFNM7DjTjwxIhd7n+Mpp8yOnHaxa/ipNtKV
lEUVidqFPA3zCjd4pm5I0fWJBrMVpXj0cU94+qkgWm9fQhVrnQwvTFtOs263R7Kf
XBChmULZ3aGC1dl2Y7Bbf/p4iZ7r1ItZV1Fz3J5uaaG9Q6u4s/g=
=sCFT
-END PGP SIGNATURE End Message ---

Bug#900018: FTBFS with latest cmdliner

[Andy Li]

On Fri, May 25, 2018 at 3:02 PM, Mehdi Dogguy  wrote:
>
> I have the feeling that OPAM team is not willing to support OPAM 1.2.2
> for a long time. So it doesn't make sense, at least for me, to
> include it in Buster.
>
> Yesterday, I've uploaded opam-file-format to NEW. As soon as it gets
> accepted, I'll upload latest version of OPAM to Debian/Sid.
>
> It's based on the discussion with upstream at
>> https://discuss.ocaml.org/t/the-forever-beta-issue/1779/6
>
>
Upstream mentioned in the linked discussion (above) that opam 1.2.2 is
their LTS release.
Sadly, opam 2 is not yet final, and "is still subject to
backwards-incompatible changes". See
https://bugzilla.redhat.com/show_bug.cgi?id=1501992#c23
I think we better stick to 1.2.2 for now.

Best regards,
Andy

Bug#898976: openjdk-7: 2018 Q2 security update

[Emilio Pozuelo Monfort]

On Fri, 18 May 2018 08:29:14 +0200 Emilio Pozuelo Monfort  
wrote:
> Source: openjdk-7
> Version: 7u171-2.6.13-1
> Severity: serious
> Tags: security
> 
> Hi,
> 
> As usual, there are a few security issues from 2018 Q2. There's no update
> yet, though it's in progress:
> 
> http://mail.openjdk.java.net/pipermail/jdk7u-dev/2018-May/010767.html
> 
> We can either backport those changes or wait for the release.

icedtea 2.6.14 for openjdk 7u181 is out now.

Cheers,
Emilio

Bug#900014: radvd: /etc/radvd.conf syntax error, unexpected T_BAD_TOKEN, expecting '{'

[Geert Stappers]

Control: retitle -1 radvd: What is wrong with my configuration ?
Control: severity -1 minor
Control: tag -1 moreinfo

On Thu, May 24, 2018 at 07:09:12PM +0200, MANAOUIL KARIM wrote:
> 
> Whenever i start the deamon, i get the following syntax error, i have no idea 
> what's wrong:
> 
> [May 24 12:06:00] radvd (1076): version 2.15 started
> /etc/radvd.conf:1 error: syntax error, unexpected T_BAD_TOKEN, expecting '{'
> [May 24 12:06:00] radvd (1076): Freeing Interfaces
> [May 24 12:06:00] radvd (1076): freeing interface enp0s8
> [May 24 12:06:00] radvd (1076): exiting, failed to read config file
 [...] 
> What is wrong with my configuration ?

This from a working configuration, note the nested  curly brackets


interface br0
{
   AdvSendAdvert on;
   IgnoreIfMissing on;
   MinRtrAdvInterval 3;
   MaxRtrAdvInterval 10;
   prefix fd45:bd2a:bb0b:a82d::/64
   {
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr off;
   };
};


Advice:

*  Put the above config in your config with minimal change,
   e.g. replace the br0 with your enp0s8
   Then you have a running radvd  ( which advertizes wrong information )
*  Make further changes for your network.


Kind request:
*  Email your /etc/radvd.conf to this bugreport


Groeten
Geert Stappers
DD
-- 
Leven en laten leven

Processed: Re: Bug#900014: radvd: /etc/radvd.conf syntax error, unexpected T_BAD_TOKEN, expecting '{'

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 radvd: What is wrong with my configuration ?
Bug #900014 [radvd] rradvd: /etc/radvd.conf syntax error, unexpected 
T_BAD_TOKEN, expecting '{'
Changed Bug title to 'radvd: What is wrong with my configuration ?' from 
'rradvd: /etc/radvd.conf syntax error, unexpected T_BAD_TOKEN, expecting '{''.
> severity -1 minor
Bug #900014 [radvd] radvd: What is wrong with my configuration ?
Severity set to 'minor' from 'grave'
> tag -1 moreinfo
Bug #900014 [radvd] radvd: What is wrong with my configuration ?
Added tag(s) moreinfo.

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

Bug#900018: FTBFS with latest cmdliner

[Mehdi Dogguy]

Hi Andy,

On 2018-05-25 08:40, Andy Li wrote:

I've a patch:
https://github.com/ocaml/opam/compare/1.2.2...andyli:1.2.2-fix.patch


That's great!

FWIW, I've opened this bug report so that Opam doesn't migrate to
testing before being fixed or updated to a newer version. I have
the feeling that OPAM team is not willing to support OPAM 1.2.2
for a long time. So it doesn't make sense, at least for me, to
include it in Buster.

Yesterday, I've uploaded opam-file-format to NEW. As soon as it gets
accepted, I'll upload latest version of OPAM to Debian/Sid.


It's based on the discussion with upstream at
https://discuss.ocaml.org/t/the-forever-beta-issue/1779/6



Thanks for the pointer.

Cheers,

--
Mehdi