Processing control commands:
> tags -1 + patch
Bug #853034 [unar] unar: Fuzzer-generated crashing testcases for a dozen
identified file formats
Added tag(s) patch.
--
853034: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Package: unar
Followup-For: Bug #853034
Control: tags -1 + patch
Dear Maintainer,
I have refreshed the package repo's fix-crashes.patch to fully
include an upstream commit 59f5a49.
Then I have created two patches on top of those upstream fixes.
Now the uploaded files on the upstream issue page
Norbert Preining wrote:
Hi Norbert,
thanks for your feedback.
> > > # A call to 'mktexlsr' is needed to register the dblatex TeX files
> > > # in the TeX database '/var/lib/texmf/ls-R-TEXMFMAIN'.
>
> There is a simple bug here:
> * no dependency on
close 863545
thanks
Processing commands for cont...@bugs.debian.org:
> close 863545
Bug #863545 [src:mupdf] CVE-2016-8728
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
863545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863545
Debian Bug Tracking System
Hi all,
> If I read the upgrade log correct, dblatex got first deconfigured and
> later *removed* during the distupgrade. Actually most of the texlive
> stack seems to get removed (including texlive-binaries, which ships
> mktexlsr). Why did this happen? What was the actual command you used to
Umpf, morning Chris,
[...]
> Anyway, shall we all take a step back and try again with this bug? Perhaps
> try and explain your point of view to Michael in another way? I look
You should maybe have taken a look at the systemd bug, where there is
definitely more to do.
Thanks for your
Your message dated Sun, 04 Jun 2017 00:03:42 +
with message-id
and subject line Bug#863680: fixed in gobby 0.5.0-8.1
has caused the Debian Bug report #863680,
regarding gobby: fails to upgrade squeeze -> wheezy -> jessie -> stretch
to be marked as done.
Processing commands for cont...@bugs.debian.org:
> # Didn't notice that #860064 wasn't RC when force-merging them, but this
> having an RC-severity is valid from my PoV.
> severity 863896 serious
Bug #863896 {Done: Simon Kelley } [dnsmasq] dnsmasq:
systemd appends junk
Processing commands for cont...@bugs.debian.org:
> # seems to be the same bug, just one closed and the other not closed
> forcemerge 860064 863896
Bug #860064 {Done: Simon Kelley } [dnsmasq] [dnsmasq]
startup failue when dns-root-data installed
Bug #863896 [dnsmasq]
Processing commands for cont...@bugs.debian.org:
> # Regression is bad but not RC
> severity 862400 important
Bug #862400 [src:linux] failed to boot in HP Proliant DL380 G5, but previous
kernel does boot
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please
Adding Norbert (texlive maintainer) to the discussion, short summary:
There was a jessie->stretch upgrade issue reported regarding
dblatex: dblatex.postrm failed due to missing mktexlsr. See #863890
for the discussion and logs.
As I did not observe such a problem during my piuparts
Hi Norbert at al.,
> > this is a blatant violation of the Debian policy and such an RC bug.
> > I don't want to see stretch released with such a grave bug.
>
> It seems Michael Biebl has lost contact to reality and is playing
> irrelevant games.
Regardless of my own opinion here as a Debian
Hi Andreas,
> since Santiago explicitly addressed you: There is no point that you
> do another NMU - I'll care for it right now to safe you the work.
Thank you :)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Followup-For: Bug #862558
Dear maintainer,
I plan to NMU plasma-workspace if the release team approves the attached patch.
(Unblock request #864067)
Best regards,
Nobuhiro
2017-05-31 23:38 GMT+09:00 YOSHINO Yoshihito :
> Followup-For: Bug #862558
> Control: reassign
Processing commands for cont...@bugs.debian.org:
> tag 792841 pending
Bug #792841 {Done: Mike Gabriel } [mate-themes]
icon-theme.cache files don't get removed on package removal or deconfiguration
Ignoring request to alter tags of bug #792841 to the same tags previously set
tag 792841 pending
thanks
Hello,
Bug #792841 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/pkg-mate/mate-themes.git/commit/?id=9b6d3ff
---
commit
Steinar H. Gunderson wrote:
Hi release managers,
in order to fix an error that has happened on a number of systems when
dist-upgrading from jessie to stretch, I need to make a small change to
the postrm script of jessie dblatex: the call of the texlive command
"mktexlsr"
Hey,
> No, the fix would be to not produce 1 GB of debug info for this library:
> The build log [1] confirms that -g is used in the i386 build.
>
> -g0 instead of -g (or no -g option) would surely solve this problem.
>
> -g1 would likely be sufficient to fix the problem on i386,
> while still
Hi,
On Fri, May 19, 2017 at 01:58:31PM +0200, Arturo Borrero Gonzalez wrote:
> We managed to upgrade the BIOS (not the last one, though).
>
> Still no luck, kernel 4.9 doesn't boot while 4.7 does.
Does it work with 4.11 (available in experimental)?
Cheers,
Ivo
Processing commands for cont...@bugs.debian.org:
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 863267 stretch-can-defer
There were no usertags set.
Usertags are now: stretch-can-defer.
> tags 863267 +
Processing commands for cont...@bugs.debian.org:
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 863584 stretch-can-defer
There were no usertags set.
Usertags are now: stretch-can-defer.
> tags 863584 +
Processing commands for cont...@bugs.debian.org:
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 863650 stretch-can-defer
There were no usertags set.
Usertags are now: stretch-can-defer.
> tags 863650 +
Processing commands for cont...@bugs.debian.org:
> severity 863650 grave
Bug #863650 [libpam-pgsql] libpam-pgsql: SIGSEGV with invalid password stored
in the database
Severity set to 'grave' from 'critical'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
863650:
Processing commands for cont...@bugs.debian.org:
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 810158 stretch-can-defer
There were no usertags set.
Usertags are now: stretch-can-defer.
> tags 810158 +
Processing commands for cont...@bugs.debian.org:
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 863802 stretch-can-defer
There were no usertags set.
Usertags are now: stretch-can-defer.
> tags 863802 +
On Sat, Jun 03, 2017 at 07:27:10PM +0200, Andreas Hoenen wrote:
> Changing this in stretch dblatex is easy (with a new version 0.3.9-3),
> but I'm not sure how a corresponding change in jessie dblatex (with a
> new version 0.3.5-3) would reach the jessie installations out there: is
> there any
Processing commands for cont...@bugs.debian.org:
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 846548 stretch-can-defer
There were no usertags set.
Usertags are now: stretch-can-defer.
> tags 846548 +
Processing commands for cont...@bugs.debian.org:
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 863745 stretch-can-defer
There were no usertags set.
Usertags are now: stretch-can-defer.
> tags 863745 +
Processing commands for cont...@bugs.debian.org:
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 863545 stretch-can-defer
There were no usertags set.
Usertags are now: stretch-can-defer.
> tags 863545 +
Processing commands for cont...@bugs.debian.org:
> tags 863890 help
Bug #863890 [dblatex] postrm fails on jessie to stretch upgrade
Added tag(s) help.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
863890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863890
Steinar H. Gunderson wrote:
> Package: dblatex
> Version: 0.3.5-2
> Severity: serious
>
> Hi,
>
> When dist-upgrading from jessie to stretch, I've seen this happen on a number
> of systems:
>
> Removing dblatex (0.3.5-2) ...
> /var/lib/dpkg/info/dblatex.postrm: 44:
Processing commands for cont...@bugs.debian.org:
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 863586 stretch-can-defer
There were no usertags set.
Usertags are now: stretch-can-defer.
> tags 863586 +
Processing commands for cont...@bugs.debian.org:
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was ni...@thykier.net).
> usertags 863544 stretch-can-defer
There were no usertags set.
Usertags are now: stretch-can-defer.
> tags 863544 +
Your message dated Sat, 03 Jun 2017 17:04:11 +
with message-id
and subject line Bug#863020: fixed in lintian 2.5.50.4
has caused the Debian Bug report #863020,
regarding lintian: FTBFS: test failures
to be marked as done.
This means that you claim that
Your message dated Sat, 03 Jun 2017 17:04:11 +
with message-id
and subject line Bug#861958: fixed in lintian 2.5.50.4
has caused the Debian Bug report #861958,
regarding lintian: insecure YAML validation [CVE-2017-8829]
to be marked as done.
This means
Package: pasystray
Version: 0.6.0-1
Severity: serious
pasystray crashes on startup when running under gnome wayland:
#0 0xedc7 in x11_property_init () at x11-property.c:46
#1 0xb10a in init (settings=0x7fffdf10) at pasystray.c:65
#2 0x8f63 in main
Your message dated Sat, 03 Jun 2017 15:07:40 +
with message-id
and subject line Bug#864026: fixed in seqan2 2.3.1+dfsg-4
has caused the Debian Bug report #864026,
regarding seqan2: FTBFS when built with dpkg-buildpackage -A
to be marked as done.
This
martin f krafft - 03.06.17, 08:12:
> 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.
I agree to that, since a discussion
On Fri, Jun 02, 2017 at 11:32:39AM +0200, Sandro Knauß wrote:
>...
> I know this is not ideal but we can't fix this. If this is a nogo for the
> release than we need to remove the i386 packages, that used the fact, that
> debian buildds for i386 are running on amd64 systems.
No, the fix would
Hi Chris,
On Sat, Jun 03, 2017 at 11:33:24AM +, Santiago Vila wrote:
> Hello Chris.
>
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> but it failed:
since Santiago explicitly addressed you: There is no point that you
do another NMU - I'll care for it right now to
Processing commands for cont...@bugs.debian.org:
> tag 856027 pending
Bug #856027 {Done: Mike Gabriel } [mate-desktop]
mate-desktop: "solid color" for background does not work at all
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need
tag 856027 pending
thanks
Hello,
Bug #856027 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/pkg-mate/mate-desktop.git/commit/?id=8260d48
---
commit
On Fri, May 19, 2017 at 01:14:09PM +0200, Markus Koschany wrote:
> Am 19.05.2017 um 02:24 schrieb Steve Cotton:
> > But the ones in contrib using original artwork only have the DFSG
> > parts in contrib, the copy of the original artwork isn't in contrib.
>
> Exactly. But Pixbros has its own
Your message dated Sat, 03 Jun 2017 13:50:07 +
with message-id
and subject line Bug#856027: fixed in mate-desktop 1.16.2-1
has caused the Debian Bug report #856027,
regarding mate-desktop: "solid color" for background does not work at all
to be marked as
Package: flashplugin-nonfree
Version: 1:3.6.1+deb8u1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I install flashplugin-nonfree, but it cannot download relevant package from
Adobe. Gives 404 File not found.
Please substitute it with correct link.
Here is the example
Your message dated Sat, 03 Jun 2017 13:04:05 +
with message-id
and subject line Bug#863936: fixed in gecode 4.4.0-5
has caused the Debian Bug report #863936,
regarding gecode: FTBFS: mv: cannot stat 'gecode/flatzinc/parser.tab.hpp': No
such file or
> Am 03.06.2017 um 14:10 schrieb John Darrington :
>
> I presume this error is one that has just recently arisen? and so far as I'm
> aware, no uploads
> of pspp have recently occured in Debian (am I right Frederich?) If so, then
> I suggest that recent
>
Hi Christoph,
On Sat, Jun 03, 2017 at 12:27:12PM +0200, Christoph Berg wrote:
Re: John Darrington 2017-06-03 <20170603061903.GA30068@jocasta.intra>
> If I'm reading that log file correctly, the issue is simply that initdb
is dumping that
> message on stderr. Our test considers
Hi Lucas,
I guess the regression failure for postgresql here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863928
and for pspp here
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850457
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863933
which also fails when starting the psql
Package: src:seqan2
Version: 2.3.1+dfsg-3.1
Severity: serious
Tags: patch
Hello Chris.
I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:
[...]
dh_link
# Some binaries (eg.
Package: ganeti-instance-debootstrap
Severity: grave
Version: 0.16-2
Dear Maintainer,
stretch system with ganeti-2.15 and g-i-d, trying to setup a new debian
vm I get:
Sat Jun 3 13:21:27 2017 * running the instance OS create scripts...
Failure: command execution error:
Could not add os for
Processing commands for cont...@bugs.debian.org:
> unarchive 7314
Bug #7314 {Done: "FedEx SmartPost" }
[autoconf2.13] autoconf trips over on long file names
Unarchived Bug 7314
> reopen 7314
Bug #7314 {Done: "FedEx SmartPost" }
Re: John Darrington 2017-06-03 <20170603061903.GA30068@jocasta.intra>
> 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.
Processing commands for cont...@bugs.debian.org:
> forcemerge 861483 863930
Bug #861483 {Done: Onur Aslan } [src:ycmd] ycmd: FTBFS against
libclang with versioned symbols
Bug #861483 {Done: Onur Aslan } [src:ycmd] ycmd: FTBFS against
libclang with versioned symbols
Control: fixed -1 2.77-1
>
> This issue seems to be caused by the recent upgrade of the dns-root-data
> package. The root.ds file in this new package contains two records where
> the previous version (2015052300+h+1) only had one record.
It looks like the bug has been recently fixed in
Processing control commands:
> fixed -1 2.77-1
Bug #863896 [dnsmasq] dnsmasq: systemd appends junk to the dnsmasq commandline
Marked as fixed in versions dnsmasq/2.77-1.
--
863896: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863896
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing commands for cont...@bugs.debian.org:
> severity 863896 serious
Bug #863896 [dnsmasq] dnsmasq: systemd appends junk to the dnsmasq commandline
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
863896:
Package: dns-root-data
Version: 2017041101
Severity: serious
Upgraded dns-root-data should declare "Breaks: dnsmasq (<< 2.77-1~)",
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863896#15
Regards,
robert
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy:
Control: tags -1 moreinfo
Re: Lucas Nussbaum 2017-06-02 <20170602020100.unhbpb6fzyyfw...@xanadu.blop.info>
> > pg_regress: initdb failed
> > Examine /<>/build/src/test/regress/log/initdb.log for the
> > reason.
> > Command was: "initdb" -D
> > "/<>/build/src/test/regress/./tmp_check/data"
Processing control commands:
> tags -1 moreinfo
Bug #863928 [src:postgresql-9.6] postgresql-9.6: FTBFS: test failures
Added tag(s) moreinfo.
--
863928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> forwarded 862558 https://bugs.kde.org/show_bug.cgi?id=380495
Bug #862558 [plasma-workspace] plasma-workspace: Freezes during login with
fresh installed Stretch Japanese environment
Set Bug forwarded-to-address to
On Jun 02, Adrian Bunk wrote:
> No system running stable Debian only is supposed to have merged /usr,
Bullshit.
--
ciao,
Marco
signature.asc
Description: PGP signature
On Jun 03, Norbert Preining wrote:
> >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?
I think that I have
Processing commands for cont...@bugs.debian.org:
> tag 863969 pending
Bug #863969 [ncurses-term] ncurses-term: fails to upgrade from 'sid' - trying
to overwrite /usr/share/terminfo/d/dvtm
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
tag 863969 pending
thanks
Hello,
Bug #863969 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/collab-maint/ncurses.git/commit/?id=d5bc8bb
---
commit
Dear Chris,
> this is a blatant violation of the Debian policy and such an RC bug.
> I don't want to see stretch released with such a grave bug.
It seems Michael Biebl has lost contact to reality and is playing
irrelevant games.
He is answering to me raising a serious bug's attention,
where
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
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
71 matches
Mail list logo