Hello Rebecca,
>Running just the affected test files (in installed -6) produced no
>failures in ~350 attempts. The build of -7 succeeded on amd64; it
>failed on ppc64, but as the log isn't available yet, I don't know if
>it's this bug.
I don't think so, when log is not available it might mea
Hi Eric,
any idea when you might find some time to comment on this build issue.
Its really urgent now and since we are basically two years in an
unchanged situation that the package does not build I have no idea
what to tell the release team.
Kind regards
Andreas.
On Fri, Sep 06, 2019 at
Hi,
On Fri, Sep 20, 2019 at 11:55:03PM +0200, Moritz Mühlenhoff wrote:
> On Fri, Sep 20, 2019 at 06:41:05PM -0300, Lisandro Damián Nicanor Pérez Meyer
> wrote:
> > I've created a WIP merge request at
> >
> > https://salsa.debian.org/med-team/sofa-framework/merge_requests/1
> >
> > I could sol
Source: openconnect
Version: 8.02-1
Severity: grave
Tags: security upstream
Justification: user security hole
Control: found -1 7.08-1
Hi,
The following vulnerability was published for openconnect.
CVE-2019-16239[0]:
| process_http_response in OpenConnect before 8.05 has a Buffer Overflow
| when
Processing control commands:
> found -1 7.08-1
Bug #940871 [src:openconnect] openconnect: CVE-2019-16239: Fix buffer overflow
with chunked HTTP handling
Marked as found in versions openconnect/7.08-1.
--
940871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940871
Debian Bug Tracking System
Your message dated Sat, 21 Sep 2019 05:05:29 +
with message-id
and subject line Bug#940721: Removed package(s) from unstable
has caused the Debian Bug report #899687,
regarding ruby-haikunator: Invalid maintainer address
pkg-azure-t...@lists.alioth.debian.org
to be marked as done.
This means
Your message dated Sat, 21 Sep 2019 05:06:36 +
with message-id
and subject line Bug#940722: Removed package(s) from unstable
has caused the Debian Bug report #899686,
regarding ruby-timeliness: Invalid maintainer address
pkg-azure-t...@lists.alioth.debian.org
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> # These bugs have been open for years. While I may not, I may try to
> # get guile-2.0 removed as soon as a month or two from now -- it's
> # unfortunate that we had to keep it in buster. Please do something
> # soon if you can.
> # Broken Depen
Hello Laszlo,
what should we do here? tg2 depends on python-repoze.tm2 which is no
longer installable due to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938133#10 (probably
the binary package is still around as cruft, but could be removed
anytime).
I'm still slightly in favor of removing tg2
Moritz Mühlenhoff writes:
> Hi Maitland,
> per upstream issue 98 it doesn't sound as if it's going to be fixed,
> should be remove it or are you planning to port it yourself?
I was just talking to the upstream author at the gnuradio conference.
Our plan going forward is to just remove the GUI el
Yes, that's one possible fix.
But if you grab a newer version from upstream, pointer_deref_comparison.patch
isn't necessary at all. The change from '\0' to NULL was already made 2018-09-19
as I described above in message #5 on this report.
I suppose grabbing the newer version make sense in the lo
Modifying pointer_deref_comparison.patch as follows works for me.
--- a/debian/patches/pointer_deref_comparison.patch
+++ b/debian/patches/pointer_deref_comparison.patch
@@ -5,7 +5,7 @@
}
if (alvec) {
-if ((alvecp = *alvec) != '\0') {
-+if (*(alvecp = *alvec) != '\0') {
++
Processing control commands:
> severity -1 serious
Bug #933057 [csh] csh: bsd-csh eval command always dies with segmentation fault
Severity set to 'serious' from 'important'
> found -1 csh/20110502-3
Bug #933057 [csh] csh: bsd-csh eval command always dies with segmentation fault
Marked as found in
Processing control commands:
> tags -1 + patch
Bug #875207 [src:tipp10] [tipp10] Future Qt4 removal from Buster
Added tag(s) patch.
--
875207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
Hi Christoph,
I attached a patch that builds tipp10 with Qt5.
I tested building with pbuilder and did a few tests of the program,
and it looks to me like everything is working.
As porting the download modules would have been a bit more effort,
as QHttp is no longer avail
Processing commands for cont...@bugs.debian.org:
> block 937893 with 915895
Bug #937893 [src:python-limits] python-limits: Python2 removal in sid/bullseye
937893 was not blocked by any bugs.
937893 was not blocking any bugs.
Added blocking bug(s) of 937893: 915895
> thanks
Stopping processing here
On Thu, Aug 15, 2019 at 11:10:37PM +0500, Andrey Rahmatullin wrote:
> Control: reassign -1 src:redis-py-cluster/1.3.3-1
> Control: severity -1 grave
> Control: forwarded -1 https://github.com/Grokzen/redis-py-cluster/issues/295
> Control: affects -1 src:python-limits
>
> On Sat, Feb 09, 2019 at 06
Your message dated Fri, 20 Sep 2019 22:19:48 +
with message-id
and subject line Bug#939868: fixed in slirp4netns 0.4.1-1
has caused the Debian Bug report #939868,
regarding slirp4netns: CVE-2019-15890
to be marked as done.
This means that you claim that the problem has been dealt with.
If thi
On Wed, Aug 21, 2019 at 11:38:18PM +0300, Dmitry Shachnev wrote:
> Control: severity -1 serious
>
> On Sun, Mar 26, 2017 at 04:05:54PM +0200, Sebastian Niehaus wrote:
> > when I call modes_gui it fails:
> >
> > users@liquid:~$ modes_gui
> > Traceback (most recent call last):
> > File "/usr/bin/
On Fri, Sep 20, 2019 at 06:41:05PM -0300, Lisandro Damián Nicanor Pérez Meyer
wrote:
> I've created a WIP merge request at
>
> https://salsa.debian.org/med-team/sofa-framework/merge_requests/1
>
> I could solve TinyXML (at least in the aspect of finding it, I might need to
> adjust something e
I've created a WIP merge request at
https://salsa.debian.org/med-team/sofa-framework/merge_requests/1
I could solve TinyXML (at least in the aspect of finding it, I might need to
adjust something else later on) but came across libgtest-dev... It ships static
libraries!
I would have to check ho
Control: tags -1 unreproducible
Running just the affected test files (in installed -6) produced no
failures in ~350 attempts. The build of -7 succeeded on amd64; it
failed on ppc64, but as the log isn't available yet, I don't know if
it's this bug.
While both tests involve time-related dtyp
Processing control commands:
> tags -1 unreproducible
Bug #940679 [src:pandas] pandas: random test crashes
Added tag(s) unreproducible.
--
940679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940679
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> limit source linux
Limiting to bugs with field 'source' containing at least one of 'linux'
Limit currently set to 'source':'linux'
> tags 940105 + pending
Bug #940105 [src:linux] linux: serious corruption issue with btrfs
Added tag(s) pending.
>
Processing commands for cont...@bugs.debian.org:
> tags 940105 + fixed-upstream
Bug #940105 [src:linux] linux: serious corruption issue with btrfs
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
940105: https://bugs.debian.org/cgi-bin/
Your message dated Fri, 20 Sep 2019 20:43:11 +
with message-id
and subject line Bug#940316: fixed in zope.testing 4.6.2-3
has caused the Debian Bug report #940316,
regarding zope.testing autopkgtest failure.
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Fri, 20 Sep 2019 20:43:17 +
with message-id
and subject line Bug#940315: fixed in zope.testrunner 4.4.9-4
has caused the Debian Bug report #940315,
regarding zope.testrunner autopkgtest failure.
to be marked as done.
This means that you claim that the problem has been dealt
Hi Simon,
On Mon, May 06, 2019 at 10:28:09PM +0200, Simon Richter wrote:
> Hi,
>
> On 06.05.19 21:35, Simon Richter wrote:
>
> > I can probably test intermediate versions and/or changes in setup, but this
> > is difficult to automate because "bad" runs require manual file system
> > repairs and
Hi Robert,
On Mon, Nov 12, 2018 at 05:08:56PM +0100, Salvatore Bonaccorso wrote:
> hi Robert,
>
> On Sun, Sep 09, 2018 at 03:38:53PM +0200, Salvatore Bonaccorso wrote:
> > Control: tags -1 + moreinfo
> >
> > Hi Robert,
> >
> > If you downgrate to 4.9.107-1 (which was only in
> > stretch-propose
Hi,
On Thu, Sep 19, 2019 at 09:15:30PM +, Sophie Loewenthal wrote:
> Package: src:linux
> Version: 4.19.37-5+deb10u2
> Severity: normal
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
>* What
Processing commands for cont...@bugs.debian.org:
> reassign 940802 xtables-addons-source
Bug #940802 [src:linux] linux-image-4.19.0-5-amd64: Build of xt_ACCOUNT.ko
failed for: 4.19.0-5-amd64 (x86_64)
Bug reassigned from package 'src:linux' to 'xtables-addons-source'.
No longer marked as found in
Hi Christoph,
I will try to port it in the next few days.
I had a short look and noticed that it uses QHttp,
which might be a bit trickier to port, but it should
be doable.
Kind regards,
Reiner
signature.asc
Description: PGP signature
Processing commands for cont...@bugs.debian.org:
> severity 940106 normal
Bug #940106 [python3-webpy] python3-webpy: Does not work with static content
Severity set to 'normal' from 'grave'
> merge 940106 940107
Bug #940106 [python3-webpy] python3-webpy: Does not work with static content
Bug #94010
On Thu, 19 Sep 2019, Mark Hindley wrote:
> On irc he also said there was little point in adding the Breaks: as apt
> doesn't
> rexec itself.
Yes, even a Pre-Depends would not achieve anything TTBOMK.
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.d
Your message dated Fri, 20 Sep 2019 14:39:23 +
with message-id
and subject line Bug#934269: fixed in lavacli 0.9.8-1
has caused the Debian Bug report #934269,
regarding lavacli: default_flow_style changed in newer pyyaml
to be marked as done.
This means that you claim that the problem has bee
close 933919
thanks
As per the discussion above, this bug is a false positive. I will also mark
#934269 as RC.
Processing commands for cont...@bugs.debian.org:
> severity 934269 serious
Bug #934269 [lavacli] lavacli: default_flow_style changed in newer pyyaml
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
934269: https://bugs.debian
Processing commands for cont...@bugs.debian.org:
> close 933919
Bug #933919 [src:lavacli] src:lavacli: Unsafe use of yaml.load()
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
933919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933919
Deb
Your message dated Fri, 20 Sep 2019 13:05:20 +
with message-id
and subject line Bug#940220: fixed in postgresql-common 207
has caused the Debian Bug report #940220,
regarding postgresql-common: pg_ctlcluster segfault
to be marked as done.
This means that you claim that the problem has been de
Your message dated Fri, 20 Sep 2019 13:05:20 +
with message-id
and subject line Bug#940220: fixed in postgresql-common 207
has caused the Debian Bug report #940220,
regarding postgresql-client-common: infinite recusion in installed versions
search
to be marked as done.
This means that you cl
Processing commands for cont...@bugs.debian.org:
> reassign 940220 postgresql-client-common
Bug #940220 [postgresql-common] postgresql-common: pg_ctlcluster segfault
Bug reassigned from package 'postgresql-common' to 'postgresql-client-common'.
No longer marked as found in versions postgresql-comm
Laurent,
On Fri, Sep 20, 2019 at 01:29:43PM +0200, Laurent Bigonville wrote:
> Can't this be stubbed or mocked on the elogind side?
I presume you mean slices here? (I am not sure that slices are the only
difference in implementation, but let's ignore that for now).
To be honest, I am not sure. P
Processing control commands:
> tag -1 pending
Bug #940220 [postgresql-common] postgresql-common: pg_ctlcluster segfault
Added tag(s) pending.
--
940220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #940220 in postgresql-common reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/postgresql/postgresql-common/commit/6b6490447bf7
Processing commands for cont...@bugs.debian.org:
> forcemerge 940220 940276
Bug #940220 [postgresql-common] postgresql-common: pg_ctlcluster segfault
Unable to merge bugs because:
package of #940276 is 'postgresql-client-common' not 'postgresql-common'
Failed to forcibly merge 940220: Did not alte
Processing control commands:
> forcemerge 939754 940808
Bug #939754 {Done: Jeremy Bicha } [gimp] gimp: Crashes when
I try to open an image or create a new one
Bug #939768 {Done: Jeremy Bicha } [gimp] gimp: After the
last upgrade, GIMP crashes when creating a new image or opening an existing one.
On 20/09/19 11:16, Mark Hindley wrote:
On Fri, Sep 20, 2019 at 09:06:57AM +0200, Laurent Bigonville wrote:
[...]
Bottom line, is libelogind even needed in the archive to achieve your goal
of having an implementation of the login1 D-Bus API not requiring systemd as
PID1?
Thanks.
I think you are
Processing commands for cont...@bugs.debian.org:
> tags 940821 + upstream
Bug #940821 [src:linux] linux-image-5.2.0-2-amd64: file cache corruption with
nfs4
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
940821: https://bugs.debian.org/cgi
Processing commands for cont...@bugs.debian.org:
> forwarded 940821
> https://lore.kernel.org/linux-nfs/ce4e1e84-50a1-c40b-a0bc-fa8ac4d76...@kot-begemot.co.uk/
Bug #940821 [src:linux] linux-image-5.2.0-2-amd64: file cache corruption with
nfs4
Set Bug forwarded-to-address to
'https://lore.kernel
Package: src:linux
Version: 5.2.9-2
Severity: critical
Justification: breaks unrelated software
Dear Maintainer,
NFSv4 caching is completely broken on SMP.
How to reproduce:
Option 1. clone openwrt, run while make clean && make -j `nproc` ; do true ;
done
It will break depending on number of
On Fri, Sep 20, 2019 at 09:06:57AM +0200, Laurent Bigonville wrote:
> Hello,
>
> When I looked I elogind a while back I was able to build a package without
> having a public libelogind0, I basically had that in my debian/rules file:
>
> # We only build the libelogind0 and libelogind-dev if we are
Control: reassign -1 src:abinit
> or do you want to reassign it back?
yes
Processing control commands:
> reassign -1 src:abinit
Bug #925624 [gfortran-9] abinit: ftbfs with GCC-9
Bug reassigned from package 'gfortran-9' to 'src:abinit'.
Ignoring request to alter found versions of bug #925624 to the same values
previously set
Ignoring request to alter fixed versions of b
Hi Aurelien,
thanks for the quick reply!
>> 7.8 of the policy requires that I have an ‘=‘ version relation on the
>> package listed in ‘Built-Using' — I am not even sure how I would determine
>> that for the source package since it’s not even used in the build?
>
> Quoting the corresponding se
On Fri, Sep 20, 2019 at 09:06:57AM +0200, Laurent Bigonville wrote:
> When I looked I elogind a while back I was able to build a package without
> having a public libelogind0, I basically had that in my debian/rules file:
>
> # We only build the libelogind0 and libelogind-dev if we are building fo
On 2019-09-19 22:56, Sascha Steinbiss wrote:
>
>
> > On 19. Sep 2019, at 11:29, Aurelien Jarno wrote:
> >
> > Package: augustus
> > Version: 3.3.3+dfsg-1
> > Severity: serious
> >
> > On 2019-09-18 23:34, Debian FTP Masters wrote:
> >> augustus_3.3.3+dfsg-1_mips64el.deb: Built-Using refers to
On Mon, 07 Jan 2019 15:54:46 +0200 Adrian Bunk wrote:
Source: check
Version: 0.12.0-0.1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=check
...
FAIL: check_check_export
FAIL: check_check
PASS: test_output.sh
PASS: test_check_nofork.sh
PASS: test_check_nofork_tear
Hello,
When I looked I elogind a while back I was able to build a package
without having a public libelogind0, I basically had that in my
debian/rules file:
# We only build the libelogind0 and libelogind-dev if we are building for
# Devuan or its derivatives
ifneq ($(shell dpkg-vendor --deriv
58 matches
Mail list logo
