If I'm reading that log file correctly, the issue is simply that initdb is
dumping that
message on stderr. Our test considers that a failure.
This would seem to suggest a problem with debian's postgres package.
However I think we can safely ignore it by changing
AT_CHECK([initdb -A trust], [
also sprach Norbert Preining [2017-06-03 00:12 +0200]:
> Then how are you planning to deal with this serious bug after
> years of inactivity?
Sounds like it might need ctte attention.
--
.''`. martin f. krafft @martinkrafft
: :' : proud Debian developer
`. `'` http://people.debian.org/~
Hi,
maybe the pspp regression failure is related to bug #863928 in PSQL where the
regression fails when the database is initialized. This is exactly what we do
in the failing test 247 in pspp.
Friedrich
Dear Adrian, dear Lucas,
thanks for your reports. Maybe you can help me with the analysis as I have
problems to reproduce it
here locally.
As already reported in the bug log
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863933
I think the problem is due to locale settings in the environme
Processing commands for cont...@bugs.debian.org:
> # lowering severity from critical given that visualvm is working for some
> users
> severity 863337 important
Bug #863337 [visualvm] visualvm: Typos in launcher script - does not start
anymore
Severity set to 'important' from 'grave'
> thanks
St
> try: grep-excuses nvidia-cuda-toolkit
> :-)
I find it's already unblocked, and get a new tool :-)
Thanks.
On 2017-06-03 03:11, Lumin wrote:
> Hi,
>
> We should either lower the severity of this bug or request for an unblock for
> this package to prevent it and its r-deps from autoremoval.
try: grep-excuses nvidia-cuda-toolkit
:-)
Andreas
Hi,
We should either lower the severity of this bug or request for an unblock for
this package to prevent it and its r-deps from autoremoval.
Your message dated Sat, 03 Jun 2017 00:18:35 +
with message-id
and subject line Bug#863944: fixed in debian-goodies 0.73
has caused the Debian Bug report #863944,
regarding /usr/bin/check-enhancements: continue: only meaningful in a `for',
`while', or `until' loop
to be marked as done.
This
Your message dated Fri, 02 Jun 2017 23:33:35 +
with message-id
and subject line Bug#863944: fixed in debian-goodies 0.69.1
has caused the Debian Bug report #863944,
regarding /usr/bin/check-enhancements: continue: only meaningful in a `for',
`while', or `until' loop
to be marked as done.
Thi
Your message dated Fri, 02 Jun 2017 23:03:37 +
with message-id
and subject line Bug#863671: fixed in picocom 1.7-2
has caused the Debian Bug report #863671,
regarding CVE-2015-9059
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Processing control commands:
> tag -1 + confirmed
Bug #863944 [debian-goodies] /usr/bin/check-enhancements: continue: only
meaningful in a `for', `while', or `until' loop
Added tag(s) confirmed.
> severity -1 serious
Bug #863944 [debian-goodies] /usr/bin/check-enhancements: continue: only
meanin
Good morning,
>As one of the systemd maintainers I am explicitly and publicly
>requesting that you do not introduce this unwanted change.
Then how are you planning to deal with this serious bug after years of
inactivity?
Norbert
On June 3, 2017 5:49:39 AM GMT+09:00, m...@linux.it wrote:
>On
On 02/06/17 at 14:58 -0400, Samuel Thibault wrote:
> Hello,
>
> Lucas Nussbaum, on jeu. 01 juin 2017 21:59:00 -0400, wrote:
> > /<>/tools/.libs/libfxt.so.0(_fini+0x0)[0xf76e3774]
> > /<>/tools/.libs/libfxt.so.0(+0x7023)[0xf76e1023]
> > /<>/tools/.libs/libfxt.so.0(fxt_fdwrite+0x6d9)[0xf76ddff9]
>
Source: neovim-qt
Version: 0.2.7-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
The experimental mipsel build of neovim-qt failed, as detailed in
https://buildd.debian.org/status/fetch.php?pkg=neovim-qt&arch=mipsel&ver=0.2.7-1&stamp=1496289160&r
cool, thanks!
On 6/2/2017 1:52 AM, Carsten Schoenert wrote:
Hello Frederico,
Am 02.06.2017 um 02:12 schrieb Frederico Rodrigues Abraham:
Hi all. Thanks for maintaining the thunderbird package in debian, much
appreciated.
I'd like to know if you've seen this issue: when I add a google mail
ac
On Jun 02, Norbert Preining wrote:
> I am planning to upload an NMU fixing this issue to DELAY3 and hope that
> release managers allow this fix into stretch.
You cannot do a NMU just because the maintainers of a package disagree
with you.
As one of the systemd maintainers I am explicitly and pu
On Fri 2017-06-02 02:53:47 +0200, Michael Biebl wrote:
> Seems like you want a Breaks/Replaces: runit-init in runit to ensure the
> package is properly upgraded for users who have already runit-init
> installed.
good call, thanks for the reminder. I'll do that in 2.1.2-9.2, which
i'll upload shor
On Fri, Jun 02, 2017 at 03:52:51PM +0200, Graham Inggs wrote:
> According to the reproducible build history [1], this package has FTBFS on
> i386 for a long time.
>
> It also never successfully built on i386 in Ubuntu [2].
>
> If there are no objections, I will file a bug requesting removal of th
Processing control commands:
> tags -1 - help unreproducible
Bug #863936 [src:gecode] gecode: FTBFS: mv: cannot stat
'gecode/flatzinc/parser.tab.hpp': No such file or directory
Ignoring request to alter tags of bug #863936 to the same tags previously set
> tags -1 patch
Bug #863936 [src:gecode] g
Control: tags -1 - help unreproducible
Control: tags -1 patch
On Fri, Jun 02, 2017 at 09:01:56PM +0300, Kari Pahula wrote:
> tags 863936 + help unreproducible
> thanks
>
> Unfortunately, I couldn't reproduce the FTBFS. I tried building it a
> few times with sbuild in a stretch environment and it
Processing control commands:
> tags -1 - help unreproducible
Bug #863936 [src:gecode] gecode: FTBFS: mv: cannot stat
'gecode/flatzinc/parser.tab.hpp': No such file or directory
Removed tag(s) help and unreproducible.
> tags -1 patch
Bug #863936 [src:gecode] gecode: FTBFS: mv: cannot stat
'gecode
Your message dated Fri, 2 Jun 2017 21:14:51 +0200
with message-id <20170602191451.cvndb5aczp6bwdmu@eldamar.local>
and subject line Re: Bug#863988: remmina not in stretch repository
has caused the Debian Bug report #863988,
regarding remmina not in stretch repository
to be marked as done.
This mean
Package: remmina
Version: 1.1.2-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Package remmina has disappeared from the stretch repository. This can be seen
for example here:
https://packages.debian.org/search?keywords=remmina
where remmina shows both in jessie and s
Processing control commands:
> severity -1 grave
Bug #863897 [src:sudo] sudo: Further issue in parsing /proc/[pid]/stat when
process name contains newline
Severity set to 'grave' from 'important'
--
863897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863897
Debian Bug Tracking System
Conta
Hello,
Lucas Nussbaum, on jeu. 01 juin 2017 21:59:00 -0400, wrote:
> /<>/tools/.libs/libfxt.so.0(_fini+0x0)[0xf76e3774]
> /<>/tools/.libs/libfxt.so.0(+0x7023)[0xf76e1023]
> /<>/tools/.libs/libfxt.so.0(fxt_fdwrite+0x6d9)[0xf76ddff9]
I proofread the code in that area, and I found an issue, could yo
Your message dated Fri, 02 Jun 2017 18:19:13 +
with message-id
and subject line Bug#861484: fixed in llvm-toolchain-3.8 1:3.8.1-24
has caused the Debian Bug report #861484,
regarding llvm-toolchain-3.8: Fix R_AARCH64_MOVW_UABS_G3 relocation
to be marked as done.
This means that you claim that
Your message dated Fri, 02 Jun 2017 18:19:13 +
with message-id
and subject line Bug#862360: fixed in llvm-toolchain-3.8 1:3.8.1-24
has caused the Debian Bug report #862360,
regarding llvm-toolchain-3.8: Fix R_AARCH64_MOVW_UABS_G3 relocation
to be marked as done.
This means that you claim that
Your message dated Fri, 02 Jun 2017 18:19:13 +
with message-id
and subject line Bug#862360: fixed in llvm-toolchain-3.8 1:3.8.1-24
has caused the Debian Bug report #862360,
regarding llvm-toolchain-3.8: Fix R_AARCH64_MOVW_UABS_G3 relocation
to be marked as done.
This means that you claim that
Your message dated Fri, 02 Jun 2017 18:19:13 +
with message-id
and subject line Bug#861484: fixed in llvm-toolchain-3.8 1:3.8.1-24
has caused the Debian Bug report #861484,
regarding llvm-toolchain-3.8: Fix R_AARCH64_MOVW_UABS_G3 relocation
to be marked as done.
This means that you claim that
tags 863936 + help unreproducible
thanks
Unfortunately, I couldn't reproduce the FTBFS. I tried building it a
few times with sbuild in a stretch environment and it worked fine
every time. The last upload for Gecode was in March and I reckon that
the build deps haven't changed much at all since t
Processing commands for cont...@bugs.debian.org:
> tags 863936 + help unreproducible
Bug #863936 [src:gecode] gecode: FTBFS: mv: cannot stat
'gecode/flatzinc/parser.tab.hpp': No such file or directory
Added tag(s) unreproducible and help.
> thanks
Stopping processing here.
Please contact me if y
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello folks,
I wanted to register a voice of dissent here. I don't think
"embarrassment" justifies breaking people's working and valid
certificates in this way.
This is only barely a security issue - StartCom and WoSign were
being punished for not
Processing commands for cont...@bugs.debian.org:
> found 863961 10.3
Bug #863961 [debhelper] Optimisation to avoid calling Getopt makes some CDBS
packages (and CDBS itself) FTBFS
Marked as found in versions debhelper/10.3.
> thanks
Stopping processing here.
Please contact me if you need assistan
Am 02.06.2017 um 16:46 schrieb Norbert Preining:
>> Your reasoning is flawed. The Google DNS servers are not set as default.
>
> AC_ARG_WITH(dns-servers,
> AS_HELP_STRING([--with-dns-servers=DNSSERVERS],
> [Space-separated list of default DNS servers]),
> [DNS_SERVE
Processing control commands:
> severity -1 serious
Bug #539798 [texlive-base] texlive: please suggest -doc packages
Severity set to 'serious' from 'wishlist'
> tags - wontfix
Unknown command or malformed arguments to command.
--
539798: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539798
De
> Your reasoning is flawed. The Google DNS servers are not set as default.
AC_ARG_WITH(dns-servers,
AS_HELP_STRING([--with-dns-servers=DNSSERVERS],
[Space-separated list of default DNS servers]),
[DNS_SERVERS="$withval"],
[DNS_SERVERS="8.8.8.8 8.8.4.4 2001:4
Am 02.06.2017 um 16:32 schrieb Norbert Preining:
> Dear maintainers,
>
> leaking information, whatsoever, is not acceptable in Debian, and against
> policy, at least lintian errors out on many occasions with
> privacy-foobar*
> errors.
>
> Setting the default servers to Google is not accept
Dear maintainers,
leaking information, whatsoever, is not acceptable in Debian, and against
policy, at least lintian errors out on many occasions with
privacy-foobar*
errors.
Setting the default servers to Google is not acceptable.
Ignoring this fact with the explanation that one can *d
Processing commands for cont...@bugs.debian.org:
> unarchive 761658
Bug #761658 {Done: m...@linux.it (Marco d'Itri)} [systemd] Please do not
default to using Google nameservers
Unarchived Bug 761658
> severity 761658 serious
Bug #761658 {Done: m...@linux.it (Marco d'Itri)} [systemd] Please do not
I solved this by updating the ca-certificates-java package in backports. I
could then install the jdk and jre.
apt-get install -t jessie-backports ca-certificates-java
--bs
According to the reproducible build history [1], this package has FTBFS
on i386 for a long time.
It also never successfully built on i386 in Ubuntu [2].
If there are no objections, I will file a bug requesting removal of the
i386 binary package.
[1] https://tests.reproducible-builds.org/de
Your message dated Fri, 02 Jun 2017 13:18:51 +
with message-id
and subject line Bug#863966: fixed in sparse 0.5.0-3
has caused the Debian Bug report #863966,
regarding sparse-test-inspect: fails to upgrade from 'sid' - trying to
overwrite /usr/bin/test-inspect
to be marked as done.
This mean
Processing control commands:
> tag -1 patch pending
Bug #863594 [veusz-helpers] veusz-helpers: duplicates .../veusz/resources
symlink
Added tag(s) pending and patch.
--
863594: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Followup-For: Bug #863594
Control: tag -1 patch pending
Hi,
I just uploaded a NMU to DELAYED/2 that fixes this issue with the
attached patch.
Andreas
diff -Nru veusz-1.21.1/debian/changelog veusz-1.21.1/debian/changelog
--- veusz-1.21.1/debian/changelog 2014-09-01 04:42:27.0 +0200
+++ ve
Processing commands for cont...@bugs.debian.org:
> tags 863929 help
Bug #863929 [src:falcon] falcon: FTBFS: Test failures ("Task
Node(0-rawreads/job_0001) failed with exit-code=256")
Added tag(s) help.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
863929: http:
tags 863929 help
thanks
Hi,
just to let you know: I'm basically offline until Tuesday and thus can not
do anything quickly, neither do I have the slightest idea what might cause
this issue after having just a quick look.
Kind regards
Andreas.
--
http://fam-tille.de
Your message dated Fri, 02 Jun 2017 13:03:39 +
with message-id
and subject line Bug#863906: fixed in asterisk 1:13.14.1~dfsg-2
has caused the Debian Bug report #863906,
regarding asterisk: CVE-2017-9358: AST-2017-004: Memory exhaustion on short
SCCP packets
to be marked as done.
This means t
Package: ncurses-term
Version: 6.0+20170408-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it
Package: mariadb-client-10.3
Version: 10.3.0-0+exp2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
beca
On Fri, Jun 02, 2017 at 11:30:24AM +0200, Andreas Henriksson wrote:
> Hello Adrian,
Hi Andreas,
> On Wed, May 24, 2017 at 08:52:12PM +0300, Adrian Bunk wrote:
> > If a member of the release team states that this is acceptable
> > for a stable release, then that's how it is.
>
> If the release te
Package: sparse-test-inspect
Version: 0.5.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it
Processing commands for cont...@bugs.debian.org:
> retitle 863901 pjproject: CVE-2017-9372: AST-2017-002: Buffer Overrun in
> PJSIP transaction layer
Bug #863901 {Done: Bernhard Schmidt } [src:pjproject]
AST-2017-002: Buffer Overrun in PJSIP transaction layer
Changed Bug title to 'pjproject: CVE
Followup-For: Bug #863721
Control: found -1 0.5.3-3
You want Breaks+Replaces: python-ncclient (<< 0.5.3)
Andreas
Processing control commands:
> found -1 0.5.3-3
Bug #863721 {Done: Sebastien Badia } [python-ncclient-doc]
python-ncclient-doc: fails to upgrade from 'testing' - trying to overwrite
/usr/share/doc/python-ncclient/html/_sources/api.txt
Marked as found in versions python-ncclient/0.5.3-3; no longe
On വെള്ളി 02 ജൂണ് 2017 03:24 വൈകു, Pirate Praveen wrote:
> I could not reproduce on an existing stretch lxc container. I will also
> try to create a fresh lxc container.
>
On a freshly created stretch lxc container also, I could not reproduce it.
signature.asc
Description: OpenPGP digital sig
Your message dated Fri, 02 Jun 2017 12:03:44 +
with message-id
and subject line Bug#863395: fixed in dacs 1.4.38a-2
has caused the Debian Bug report #863395,
regarding libapache2-mod-dacs: fails to load module: undefined symbol:
ssl_hook_Fixup
to be marked as done.
This means that you claim
- Forwarded message from Barry Brachman -
Date: Sun, 28 May 2017 12:35:44 -0700
From: Barry Brachman
Reply-to: barry.brach...@gmail.com
To: Christoph Berg
Subject: Re: ssl_hook_Fixup needed?
Hi Christoph --
>Debian has again run into the "undefined symbol: ssl_hook_Fixup"
>problem. H
Package: debhelper
Version: 10.4
Severity: serious
Tags: patch
Hi,
tl;dr this is caused by 91b064a0baea0ef37937bce56e5b080ac5a52595.
When building cdbs from sid with 10.4:
14: build hdparmFAILED (hdparm.at:18)
This package has a "common-install-prehook-ar
Processing commands for cont...@bugs.debian.org:
> tags 863901 + upstream
Bug #863901 {Done: Bernhard Schmidt } [src:pjproject]
AST-2017-002: Buffer Overrun in PJSIP transaction layer
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
863901:
Package: kopano-server
Version: 8.1.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package left unowned files on
the system after purge, which is a violation of policy 6.8 (or 10.8):
https://www.debian.org/doc/debian-policy
Hi,
On 02/06/17 at 11:32 +0200, Sandro Knauß wrote:
> Hey,
>
> > During a rebuild of all packages in stretch (in a stretch chroot, not a
> > sid chroot), your package failed to build on i386.
> >
> > Note that the build node has a lot of RAM, so if memory is really
> > exhausted, it could mean
On വെള്ളി 02 ജൂണ് 2017 01:38 വൈകു, Joerg Jaspert wrote:
> installed gitlab on a fresh stretch system. Its doing lots of stuff in
> its postinst, until finally:
Can you share more details about your system?
phyisical/vm/container/chroot etc
> Precompiling assets...
> Starting GitLab Unicorn
> St
tag 863267 pending
thanks
Hello,
Bug #863267 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:
https://anonscm.debian.org/cgit/python-modules/packages/python-django.git/commit/?id=53f0ab6
---
commit 53f0ab6240f3
Processing commands for cont...@bugs.debian.org:
> tag 863267 pending
Bug #863267 [src:python-django] Miscalculates MigrationHistory dependencies
between multiple django apps - regression from 1.8
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Hey,
> During a rebuild of all packages in stretch (in a stretch chroot, not a
> sid chroot), your package failed to build on i386.
>
> Note that the build node has a lot of RAM, so if memory is really
> exhausted, it could mean that it can no longer be built on i386.
Well the memory consumptio
Your message dated Fri, 02 Jun 2017 09:33:44 +
with message-id
and subject line Bug#863937: fixed in faustworks 0.5~repack0-3
has caused the Debian Bug report #863937,
regarding faustworks: FTBFS: RCC: Error in 'Resources/i18n.qrc': Cannot find
file 'translations/i18n_ru.qm'
to be marked as d
Your message dated Fri, 2 Jun 2017 11:30:24 +0200
with message-id <20170602093024.ga13...@fatal.se>
and subject line Re: Bug#863269: usrmerge is not yet ready for a stable release
has caused the Debian Bug report #863269,
regarding usrmerge is not yet ready for a stable release
to be marked as done
tag 863937 pending
thanks
Hello,
Bug #863937 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:
http://anonscm.debian.org/git/pkg-multimedia/faustworks.git/commit/?id=bd4aebe
---
commit bd4aebe9364a5fa1b3f2b08315
Processing commands for cont...@bugs.debian.org:
> tag 863937 pending
Bug #863937 [src:faustworks] faustworks: FTBFS: RCC: Error in
'Resources/i18n.qrc': Cannot find file 'translations/i18n_ru.qm'
Ignoring request to alter tags of bug #863937 to the same tags previously set
> thanks
Stopping proc
Control: tags -1 pending
On 02/06/17 03:05, Lucas Nussbaum wrote:
> Source: faustworks
> Version: 0.5~repack0-2
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20170601 qa-ftbfs
> Justification: FTBFS in stretch on amd64
>
> Hi,
>
> During a rebuil
Processing control commands:
> tags -1 pending
Bug #863937 [src:faustworks] faustworks: FTBFS: RCC: Error in
'Resources/i18n.qrc': Cannot find file 'translations/i18n_ru.qm'
Added tag(s) pending.
--
863937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863937
Debian Bug Tracking System
Conta
Processing commands for cont...@bugs.debian.org:
> retitle 863929 falcon: FTBFS: Test failures ("Task Node(0-rawreads/job_0001)
> failed with exit-code=256")
Bug #863929 [src:falcon] falcon: FTBFS: Test failures
Changed Bug title to 'falcon: FTBFS: Test failures ("Task
Node(0-rawreads/job_0001)
Your message dated Fri, 02 Jun 2017 09:04:08 +
with message-id
and subject line Bug#863902: fixed in pjproject 2.5.5~dfsg-6
has caused the Debian Bug report #863902,
regarding pjproject: AST-2017-003: Crash in PJSIP multi-part body parser
to be marked as done.
This means that you claim that t
Processing commands for cont...@bugs.debian.org:
> retitle 863934 node-dateformat: FTBFS: Test failures ("AssertionError:
> '1:19:44 PM GMT+' === '1:19:44 PM UTC")
Bug #863934 [src:node-dateformat] node-dateformat: FTBFS: Test failures
Changed Bug title to 'node-dateformat: FTBFS: Test failur
Your message dated Fri, 02 Jun 2017 09:04:08 +
with message-id
and subject line Bug#863901: fixed in pjproject 2.5.5~dfsg-6
has caused the Debian Bug report #863901,
regarding AST-2017-002: Buffer Overrun in PJSIP transaction layer
to be marked as done.
This means that you claim that the prob
Processing commands for cont...@bugs.debian.org:
> retitle 863926 fxt: FTBFS: Test failures ("*** stack smashing detected ***")
Bug #863926 [src:fxt] fxt: FTBFS: Test failures
Changed Bug title to 'fxt: FTBFS: Test failures ("*** stack smashing detected
***")' from 'fxt: FTBFS: Test failures'.
>
Processing commands for cont...@bugs.debian.org:
> merge 863950 863951
Bug #863950 [gitlab] gitlab: Fresh install does not start
Bug #863951 [gitlab] gitlab: Fresh install does not start
Merged 863950 863951
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
863950:
Processing commands for cont...@bugs.debian.org:
> tags 863933 - unreproducible
Bug #863933 [src:pspp] pspp: FTBFS: | ./conftest.c:67: undefined reference to
`shl_load'
Bug #850457 [src:pspp] pspp: FTBFS randomly (testsuite: 247 failed)
Removed tag(s) unreproducible.
Removed tag(s) unreproducible
Package: gitlab
Severity: serious
Version: 8.13.11+dfsg1-7
Dear Maintainer,
installed gitlab on a fresh stretch system. Its doing lots of stuff in
its postinst, until finally:
Precompiling assets...
Starting GitLab Unicorn
Starting GitLab Sidekiq
Could not find gem 'mysql2 (~> 0.3.16)' in any of
Package: gitlab
Severity: serious
Version: 8.13.11+dfsg1-7
Dear Maintainer,
installed gitlab on a fresh stretch system. Its doing lots of stuff in
its postinst, until finally:
Precompiling assets...
Starting GitLab Unicorn
Starting GitLab Sidekiq
Could not find gem 'mysql2 (~> 0.3.16)' in any of
Processing commands for cont...@bugs.debian.org:
> forcemerge 863933 850457
Bug #863933 [src:pspp] pspp: FTBFS: | ./conftest.c:67: undefined reference to
`shl_load'
Bug #863933 [src:pspp] pspp: FTBFS: | ./conftest.c:67: undefined reference to
`shl_load'
Added tag(s) unreproducible.
Bug #850457 [
It wasn't there this morning when I fetched the sources and attempted
to produce the NMU.
All is good then. Thanks!
2017-06-02 10:53 GMT+03:00 Emilio Pozuelo Monfort :
> On 02/06/17 09:07, Martin-Éric Racine wrote:
>> Greetings,
>>
>> I've tried merging this patch to submit an NMU.
>>
>> This fai
On 02/06/17 09:07, Martin-Éric Racine wrote:
> Greetings,
>
> I've tried merging this patch to submit an NMU.
>
> This fails miserably because the existing patches are not applied in a
> known order and dpkg complains loudly that patches are either fuzzy or
> cannot be applied as-is.
>
> To guar
Your message dated Fri, 02 Jun 2017 07:18:43 +
with message-id
and subject line Bug#863547: fixed in magnum 3.1.1-5
has caused the Debian Bug report #863547,
regarding CVE-2016-7404
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Greetings,
I've tried merging this patch to submit an NMU.
This fails miserably because the existing patches are not applied in a
known order and dpkg complains loudly that patches are either fuzzy or
cannot be applied as-is.
To guarantee that patches are always applied in the same order, their
87 matches
Mail list logo
