Processing commands for cont...@bugs.debian.org:
> # Currently testing my implementation locally
> tags 972749 + pending
Bug #972749 [xen-tools] xen-tools: bullseye: /updates -> -security
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Package: linux-image-5.10.0-trunk-arm64-unsigned
Version: 5.10.1-1~exp1
Severity: grave
Justification: renders package unusable
Dear Debian kernel maintainers,
This is somewhat similar to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977645
but I assume this is a different issue as booting
On 2020-12-18, at 15:32:01 +0100, Andreas Tille wrote:
> I tried no override_dh_shlibdeps in shasta debian/rules, which has
> lead to:
>
> dpkg-shlibdeps: error: cannot find library
> /usr/lib/python3/dist-packages/shasta.cpython-39-x86_64-linux-gnu.so
> needed by debian/shasta/usr/bin/shasta (ELF
Processing control commands:
> tag -1 moreinfo
Bug #977647 [src:linux] 5.10.1 Debian kernel does not boot on amd64 with btrfs
rootfs
Added tag(s) moreinfo.
> severity -1 important
Bug #977647 [src:linux] 5.10.1 Debian kernel does not boot on amd64 with btrfs
rootfs
Severity set to 'important'
Control: tag -1 moreinfo
Control: severity -1 important
Justification: does not affect all users
Hi,
Ryutaroh Matsumoto writes:
> Package: linux-image-5.10.0-trunk-amd64-unsigned
> Version: 5.10.1-1~exp1
> Severity: grave
> Justification: renders package unusable
>
I just confirmed that
Processing commands for cont...@bugs.debian.org:
> forcemerge 844141 976933
Bug #844141 [src:libsys-cpuaffinity-perl] libsys-cpuaffinity-perl: FTBFS:
Failed test 'bind to all processors successful 18446744073709551615 ==
18446744073709551616-1'
Bug #844141 [src:libsys-cpuaffinity-perl]
Your message dated Fri, 18 Dec 2020 22:36:07 +
with message-id
and subject line Bug#977677: fixed in node-babel7 7.12.11+~cs150.141.84-2
has caused the Debian Bug report #977677,
regarding node-babel7: versioning missing for virtual package node-babel-runtime
to be marked as done.
This means
Hi Christoph,
Thanks for the feedback!
I just generated a new symbols-file. Can you recommend
a better fix for that?
Regards
Anton
Le 18/12/2020 à 23:16, Jonas Smedegaard a écrit :
> Quoting Xavier (2020-12-18 22:59:06)
>> Le 18/12/2020 à 22:28, Jonas Smedegaard a écrit :
>>> Source: node-jest
>>> Version: 26.6.3+repack+~cs61.38.31-3
>>> Severity: serious
>>>
>>> By accident I noticed that a release of node-jest with only
Quoting Xavier (2020-12-18 22:59:06)
> Le 18/12/2020 à 22:28, Jonas Smedegaard a écrit :
> > Source: node-jest
> > Version: 26.6.3+repack+~cs61.38.31-3
> > Severity: serious
> >
> > By accident I noticed that a release of node-jest with only changes to
> > package relations changed size from 8.5
Re: Anton Gladky
> Dear maintainer,
>
> I have prepared an NMU (versioned as dds_2.9.0-8.1) and
> uploaded to DELAYED/5.
>
> Please feel free to tell me if I should delay it longer, cancel
> or reschedule.
Hi Anton,
thanks for your help with fixing this.
However I think your "update symbols
Your message dated Fri, 18 Dec 2020 22:59:06 +0100
with message-id <4e827dba-2d2c-ba6a-df36-ff294183c...@debian.org>
and subject line Re: [Pkg-javascript-devel] Bug#977685: node-jest: build
routines are too brittle: build failures go undetected
has caused the Debian Bug report #977685,
regarding
Your message dated Fri, 18 Dec 2020 22:00:09 +
with message-id
and subject line Bug#972050: fixed in ndpi 3.4-1
has caused the Debian Bug report #972050,
regarding CVE-2020-11939 CVE-2020-11940 CVE-2020-15471 CVE-2020-15472
CVE-2020-15473 CVE-2020-15474 CVE-2020-15475 CVE-2020-15476
to be
Le 18/12/2020 à 22:28, Jonas Smedegaard a écrit :
> Source: node-jest
> Version: 26.6.3+repack+~cs61.38.31-3
> Severity: serious
>
> By accident I noticed that a release of node-jest with only changes to
> package relations changed size from 8.5 megabytes to 500 kilobytes.
>
> A closer
Your message dated Fri, 18 Dec 2020 21:49:55 +
with message-id
and subject line Bug#977677: fixed in pkg-js-tools 0.9.58
has caused the Debian Bug report #977677,
regarding node-babel7: versioning missing for virtual package node-babel-runtime
to be marked as done.
This means that you claim
Your message dated Fri, 18 Dec 2020 21:49:45 +
with message-id
and subject line Bug#977624: fixed in libxstream-java 1.4.15-1
has caused the Debian Bug report #977624,
regarding libxstream-java: CVE-2020-26259: XStream is vulnerable to an
Arbitrary File Deletion on the local host when
Control: tag -1 pending
Hello,
Bug #977677 in pkg-js-tools 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:
Processing control commands:
> tag -1 pending
Bug #977677 [pkg-js-tools] node-babel7: versioning missing for virtual package
node-babel-runtime
Added tag(s) pending.
--
977677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977677
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Source: node-jest
Version: 26.6.3+repack+~cs61.38.31-3
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
By accident I noticed that a release of node-jest with only changes to
package relations changed size from 8.5 megabytes to 500 kilobytes.
A closer examination of build logs
Processing commands for cont...@bugs.debian.org:
> reassign 977677 pkg-js-tools
Bug #977677 [node-babel7] node-babel7: versioning missing for virtual package
node-babel-runtime
Bug reassigned from package 'node-babel7' to 'pkg-js-tools'.
Ignoring request to alter found versions of bug #977677 to
Your message dated Fri, 18 Dec 2020 21:04:01 +
with message-id
and subject line Bug#957499: fixed in logtools 0.13e+nmu1
has caused the Debian Bug report #957499,
regarding logtools: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 18 Dec 2020 21:00:12 +
with message-id
and subject line Bug#975588: fixed in openms 2.6.0+cleaned1-1
has caused the Debian Bug report #975588,
regarding openms: FTBFS against boost_1.74
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 18 Dec 2020 21:00:09 +
with message-id
and subject line Bug#957256: fixed in gauche 0.9.10-1
has caused the Debian Bug report #957256,
regarding gauche: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Le 18/12/2020 à 21:37, Xavier a écrit :
> Le 18/12/2020 à 20:09, Jonas Smedegaard a écrit :
>> Quoting Xavier (2020-12-18 18:45:30)
>>> Please launch autopkgtest before uploading such changes to avoid
>>> problems.
>>
>> Yes, I fully agree.
>>
>> I generally run autopkgtest at every build +
Le 18/12/2020 à 20:09, Jonas Smedegaard a écrit :
> Quoting Xavier (2020-12-18 18:45:30)
>> Please launch autopkgtest before uploading such changes to avoid
>> problems.
>
> Yes, I fully agree.
>
> I generally run autopkgtest at every build + compare with debdiff
> against previous package
Source: bouncycastle
Version: 1.65-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Hi,
The following vulnerability was published for bouncycastle, it affects
1.65 and 1.66 and is fixed in 1.67.
CVE-2020-28052[0]:
Hi Valentin,
I just received the bug below. It seems that the manpage duplication is
actually upstream:
-
https://github.com/containers/common/blob/master/docs/containers-mounts.conf.5.md
-
https://github.com/containers/podman/blob/master/docs/source/markdown/containers-mounts.conf.5.md
They
Control: forwarded -1 https://github.com/smarty-php/smarty/issues/621
Hi Wolfgang, (hi Uwe),
On Do 17 Dez 2020 17:48:20 CET, Wolfgang Schweer wrote:
Package: smarty3
Version: 3.1.36-1
Severity: critical
Justification: breaks unrelated software
User: debian-...@lists.debian.org
Usertags:
Processing commands for cont...@bugs.debian.org:
> tags 977229 +pending +patch
Bug #977229 [src:kcollectd] kcollectd FTBFS with Boost 1.74
Added tag(s) pending.
Bug #977229 [src:kcollectd] kcollectd FTBFS with Boost 1.74
Added tag(s) patch.
> user team+bo...@tracker.debian.org
Setting user to
Processing commands for cont...@bugs.debian.org:
> retitle 977677 node-babel7: versioning missing for virtual package
> node-babel-runtime
Bug #977677 [node-babel7] FTBFS: dependency to node-babel-runtime >=7 isn't
understood by deb tools
Changed Bug title to 'node-babel7: versioning missing
tags 977229 +pending +patch
user team+bo...@tracker.debian.org
usertag 977229 +boost174
thanks
Dear maintainer,
I have prepared an NMU (versioned as 0.11.99.0-1.1) and
uploaded to DELAYED/5.
Please feel free to tell me if I should delay it longer, cancel
or reschedule.
Diff is attached. MR is
Quoting Xavier (2020-12-18 18:45:30)
> Please launch autopkgtest before uploading such changes to avoid
> problems.
Yes, I fully agree.
I generally run autopkgtest at every build + compare with debdiff
against previous package release.
I certainly intended to do here as well, but see now that
Processing commands for cont...@bugs.debian.org:
> affects 977677 node-i18next-xhr-backend node-i18next-browser-languagedetector
> node-i18next node-matrix-js-sdk
Bug #977677 [node-babel7] FTBFS: dependency to node-babel-runtime >=7 isn't
understood by deb tools
Added indication that 977677
Forgotten diff.
Anton
nmu.debdiff
Description: Binary data
tags 977265 +pending +patch
user team+bo...@tracker.debian.org
usertag 977265 +boost174
thanks
Dear maintainer,
I have prepared an NMU (versioned as dds_2.9.0-8.1) and
uploaded to DELAYED/5.
Please feel free to tell me if I should delay it longer, cancel
or reschedule.
Diff is attached. MR is
Processing commands for cont...@bugs.debian.org:
> tags 977265 +pending +patch
Bug #977265 [src:dds] dds ftbfs with boost1.74
Added tag(s) pending.
Bug #977265 [src:dds] dds ftbfs with boost1.74
Added tag(s) patch.
> user team+bo...@tracker.debian.org
Setting user to team+bo...@tracker.debian.org
Your message dated Fri, 18 Dec 2020 18:49:52 +
with message-id
and subject line Bug#957996: fixed in xppaut 6.11b+1.dfsg-1.1
has caused the Debian Bug report #957996,
regarding xppaut: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing control commands:
> reassign -1 node-babel7
Bug #977677 [node-regenerator-transform] FTBFS: dependency to
node-babel-runtime >=7 isn't understood by deb tools
Bug reassigned from package 'node-regenerator-transform' to 'node-babel7'.
No longer marked as found in versions 0.14.5-2.
Control: reassign -1 node-babel7
Control: affects -1 node-regenerator-transform
Quoting Jonas Smedegaard (2020-12-18 19:13:01)
> Quoting Xavier Guimard (2020-12-18 18:38:50)
> > Since 0.14.5-2, dependency to node-babel7 was replaced by a dependency to
> > node-babel-runtime (>= 7) which is
Hi,
On 18-12-2020 16:47, Dominic Hargreaves wrote:
> pkg-perl standard practice is to keep dual-lived packages in unstable
> for a release cycle to make it easier to bring back when they
> become newer than the version in perl again, which happens from time
> to time.
Ack. gregoa explained the
On Fri, Dec 18, 2020 at 04:07:50PM +0100, Andreas Tille wrote:
> On Fri, Dec 18, 2020 at 07:37:12PM +0500, Andrey Rahmatullin wrote:
> > On Fri, Dec 18, 2020 at 03:32:01PM +0100, Andreas Tille wrote:
> > > I tried no override_dh_shlibdeps in shasta debian/rules, which has lead
> > > to:
> > >
> >
Quoting Xavier Guimard (2020-12-18 18:38:50)
> Since 0.14.5-2, dependency to node-babel7 was replaced by a dependency to
> node-babel-runtime (>= 7) which is provided by:
> * node-babel-runtime (src node-babel 6)
> * virtual node-babel-runtime provided by node-babel7
That's wrong: a _versioned_
Your message dated Fri, 18 Dec 2020 17:56:37 +
with message-id
and subject line Bug#966184: fixed in xfractint 20.4.10-2.1
has caused the Debian Bug report #966184,
regarding xfractint: FTBFS with GCC 10: multiple definition of ... due to
-fno-common
to be marked as done.
This means that
Le 18/12/2020 à 18:38, Xavier Guimard a écrit :
> Package: node-regenerator-transform
> Version: 0.14.5-2
> Severity: serious
> Tags: ftbfs
>
> Since 0.14.5-2, dependency to node-babel7 was replaced by a dependency to
> node-babel-runtime (>= 7) which is provided by:
> * node-babel-runtime (src
Package: node-regenerator-transform
Version: 0.14.5-2
Severity: serious
Tags: ftbfs
Since 0.14.5-2, dependency to node-babel7 was replaced by a dependency to
node-babel-runtime (>= 7) which is provided by:
* node-babel-runtime (src node-babel 6)
* virtual node-babel-runtime provided by
Your message dated Fri, 18 Dec 2020 16:19:26 +
with message-id
and subject line Bug#950058: fixed in python-flask-cors 3.0.9-1
has caused the Debian Bug report #950058,
regarding python-flask-cors FTBFS with flask 1.1.1
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 18 Dec 2020 16:19:26 +
with message-id
and subject line Bug#969362: fixed in python-flask-cors 3.0.9-1
has caused the Debian Bug report #969362,
regarding python-flask-cors: CVE-2020-25032
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 18 Dec 2020 17:10:22 +0100
with message-id <20201218161022.GA63644@pisco.westfalen.local>
and subject line Re: Time to close this ?
has caused the Debian Bug report #921952,
regarding Don't include in buster without proper commitment to update in stable
to be marked as
Your message dated Fri, 18 Dec 2020 16:06:46 +
with message-id
and subject line Bug#975791: fixed in system-config-printer 1.5.13-1
has caused the Debian Bug report #975791,
regarding system-config-printer: FTBFS: dh_auto_test: error: make -j4 check
VERBOSE=1 returned exit code 2
to be
Your message dated Fri, 18 Dec 2020 16:06:40 +
with message-id
and subject line Bug#964688: fixed in sigviewer 0.6.4-1
has caused the Debian Bug report #964688,
regarding sigviewer: FTBFS: src/file_handling_impl/biosig_reader.cpp:142:10:
error: ‘QFile’ has not been declared
to be marked as
Processing commands for cont...@bugs.debian.org:
> notfixed 936805 19.0~alpha3+dfsg1-1
Bug #936805 {Done: Vasyl Gello } [src:kodi] kodi:
Python2 removal in sid/bullseye
The source 'kodi' and version '19.0~alpha3+dfsg1-1' do not appear to match any
binary packages
No longer marked as fixed in
On 12/18/20 4:49 PM, Andreas Tille wrote:
>> Well, the test is obviously broken and upstream currently can't be bothered
>> to fix
>> it on non-x86 targets. He will certainly have to do it at some point given
>> that ARM64
>> is replacing more and more x86_64 systems, but I wouldn't bother,
Ok, in that case, I think that a comment in the d/rules files is enough in
order to keep in mind that we have this issue with ppc64el.
Your message dated Fri, 18 Dec 2020 15:48:30 +
with message-id
and subject line Bug#976927: fixed in cimg 2.9.4+dfsg-2
has caused the Debian Bug report #976927,
regarding cimg: FTBFS on ppc64el (arch:all-only src pkg): g++: error:
unrecognized argument in option ‘-mtune=generic’
to be marked
On Fri, Dec 18, 2020 at 04:44:04PM +0100, John Paul Adrian Glaubitz wrote:
> >
> > so it does not fit with our policy: do not hide problems ;)
Well, we do not need to *hide* the problem. We can exclude the test and
*document* the problem - say in a README.Debian on the affected
architecture.
> Well, the test is obviously broken and upstream currently can't be bothered
> to fix
> it on non-x86 targets. He will certainly have to do it at some point given
> that ARM64
> is replacing more and more x86_64 systems, but I wouldn't bother, personally.
so what is the best solution in order
On Thu, Dec 17, 2020 at 10:17:24PM +0100, Paul Gevers wrote:
> Hi Dominic,
>
> On Fri, 22 May 2020 16:15:31 +0100 Dominic Hargreaves
> wrote:
> > Package: libhttp-tiny-perl
> > Version: 0.076-1
> > Severity: serious
> > Justification: maintainer
> >
> > libhttp-tiny-perl at this version should
On 12/18/20 4:42 PM, PICCA Frederic-Emmanuel wrote:
>> Yes, good catch. The spec file for the openSUSE package has this [1]:
>
> so it does not fit with our policy: do not hide problems ;)
>
> The problem is that I do not have enougt time to investigate... on a porter
> box
Well, the test is
> Yes, good catch. The spec file for the openSUSE package has this [1]:
so it does not fit with our policy: do not hide problems ;)
The problem is that I do not have enougt time to investigate... on a porter box
Hi Frederic!
On 12/18/20 4:00 PM, PICCA Frederic-Emmanuel wrote:
> looking at the Opensuze log, I can find this
>
> [ 93s] + pytest-3.8 --ignore=_build.python2 --ignore=_build.python3
> --ignore=_build.pypy3 -v -k 'not speed and not (test_model_nan_policy or
> test_shgo_scipy_vs_lmfit_2)'
>
Processing control commands:
> forwarded -1 https://github.com/smarty-php/smarty/issues/621
Bug #977604 [smarty3] smarty3: broken internal parsetree code
Set Bug forwarded-to-address to
'https://github.com/smarty-php/smarty/issues/621'.
--
977604:
On Fri, Dec 18, 2020 at 07:37:12PM +0500, Andrey Rahmatullin wrote:
> On Fri, Dec 18, 2020 at 03:32:01PM +0100, Andreas Tille wrote:
> > I tried no override_dh_shlibdeps in shasta debian/rules, which has lead
> > to:
> >
> > dpkg-shlibdeps: error: cannot find library
> >
Hello
looking at the Opensuze log, I can find this
[ 93s] + pytest-3.8 --ignore=_build.python2 --ignore=_build.python3
--ignore=_build.pypy3 -v -k 'not speed and not (test_model_nan_policy or
test_shgo_scipy_vs_lmfit_2)'
[ 97s] = test session starts
On Sun, 28 Jul 2019 19:26:12 +0530 Pirate Praveen
wrote:
> It stalled for a long time and we restarted work on it recently. We
are in the process of getting server space to setup dak.
Just adding this information here,
Debian FastTrack is live for some time and instructions to install
On Fri, Dec 18, 2020 at 03:41:58PM +0100, John Paul Adrian Glaubitz wrote:
> On 12/18/20 3:19 PM, Andreas Tille wrote:
> > I wonder whether we could get some help from PowerPC team to solve this
> > issue. If we can not get that test working I see only two options:
> >
> >1. Skip this
Processing control commands:
> severity -1 important
Bug #977590 [freeradius] freeradius: After upgrade to buster, freeradius
doesn't talk over the network anymore
Severity set to 'important' from 'critical'
> tags -1 moreinfo
Bug #977590 [freeradius] freeradius: After upgrade to buster,
Control: severity -1 important
Control: tags -1 moreinfo
Hi Harald,
I'm going to downgrade this because
- it does not break unrelated software ... The radius server not running
might cause other software not to be able to authenticate anymore, but
Radius can be easily made redundant.
- this is
On 12/18/20 3:19 PM, Andreas Tille wrote:
> I wonder whether we could get some help from PowerPC team to solve this
> issue. If we can not get that test working I see only two options:
>
>1. Skip this specific test
>2. Exclude ppc64el from architecture list
>
> Any help would be really
On Fri, Dec 18, 2020 at 03:32:01PM +0100, Andreas Tille wrote:
> Hi,
>
> I tried no override_dh_shlibdeps in shasta debian/rules, which has lead
> to:
>
> dpkg-shlibdeps: error: cannot find library
> /usr/lib/python3/dist-packages/shasta.cpython-39-x86_64-linux-gnu.so needed
> by
Hi,
I tried no override_dh_shlibdeps in shasta debian/rules, which has lead
to:
dpkg-shlibdeps: error: cannot find library
/usr/lib/python3/dist-packages/shasta.cpython-39-x86_64-linux-gnu.so needed by
debian/shasta/usr/bin/shasta (ELF format: 'elf64-x86-64' abi:
'0201003e';
Control: tags -1 -upstream
Control: tags -1 help
Hi,
I wonder whether we could get some help from PowerPC team to solve this
issue. If we can not get that test working I see only two options:
1. Skip this specific test
2. Exclude ppc64el from architecture list
Any help would be really
Processing control commands:
> tags -1 -upstream
Bug #976952 [src:lmfit-py] lmfit-py: FTBFS on ppc64el (arch:all-only src pkg):
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9
returned exit code 13
Removed tag(s) upstream.
> tags -1 help
Bug #976952 [src:lmfit-py]
Package: src:sbc
Version: 1.5-1
Severity: serious
Tags: sid bullseye ftbfs
/usr/bin/ld: /usr/bin/ld: sbc/.libs/libsbc-private.a(sbc_primitives.o): in
function `sbc_init_primitives_x86':
./sbc/sbc_primitives.c:596: undefined reference to `__builtin_cpu_init'
Processing commands for cont...@bugs.debian.org:
> severity 969530 grave
Bug #969530 [src:rsync] rsync: CVE-2020-14387
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
969530:
Package: gprename
Followup-For: Bug #912880
X-Debbugs-Cc: witold.bary...@gmail.com
Hi all.
Hi Christoph.
Yes, that was me that ported it upstream, specifically because I was sad
it gone from Debian!
The upstream version 20201214 was specifically developed and tested on
Debian, and fully
Processing commands for cont...@bugs.debian.org:
> tags 977657 + ftbfs upstream
Bug #977657 [swi-prolog] swi-prolog: FTBFS with OpenSSL 1.1.1i
Added tag(s) ftbfs and upstream.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
977657:
Processing commands for cont...@bugs.debian.org:
> tags 977655 + ftbfs upstream
Bug #977655 [m2crypto] m2crypto: FTBFS with OpenSSL 1.1.1i
Added tag(s) ftbfs and upstream.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
977655:
Processing commands for cont...@bugs.debian.org:
> reassign 977645 src:linux 5.10.1-1~exp1
Bug #977645 [linux-image-5.10.0-trunk-arm64-unsigned] 5.10.1 Debian kernel does
not boot on raspi 4 with ext4 rootfs and sdcard
Bug reassigned from package 'linux-image-5.10.0-trunk-arm64-unsigned' to
Hi Andreas,
On Fri, 18 Dec 2020 at 15:53, Andreas Tille wrote:
> Control: tags -1 help
>
> Hi,
>
> I tried to fix the issue by making dh_shlibdeps work. In
>
>
> https://salsa.debian.org/med-team/shasta/-/commit/366edd672be428cc553b34b99bc614aa698175d6
>
> I documented what I tried but all
Updated debdiff, due to some functions not yet implemented in ~beta3
G.
On Fri, 18 Dec 2020 09:34:11 + Debian FTP Masters
wrote:
> Source: luajit
> Source-Version: 2.1.0~beta3+dfsg-5.2
> Done: Gianfranco Costamagna
>
> We believe that the bug you reported is fixed in the latest version
Processing commands for cont...@bugs.debian.org:
> tags 977657 + confirmed
Bug #977657 [swi-prolog] swi-prolog: FTBFS with OpenSSL 1.1.1i
Added tag(s) confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
977657:
Hi Georg,
On Tue, Dec 15, 2020 at 12:03:46AM +, Georg Faerber wrote:
> I'm well aware and will handle this accordingly once there is a new
> upstream release, which should happen soon.
Thanks for the info, I'll wait for that.
I have a few unrelated packaging improvements that I wrote when
Processing control commands:
> tags -1 help
Bug #977308 [src:shasta] shasta: hardcoded dependencies on boost 1.71
Added tag(s) help.
--
977308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 help
Hi,
I tried to fix the issue by making dh_shlibdeps work. In
https://salsa.debian.org/med-team/shasta/-/commit/366edd672be428cc553b34b99bc614aa698175d6
I documented what I tried but all failed and I think the key to this bug
is just making it work.
Any idea?
Kind
Your message dated Fri, 18 Dec 2020 10:20:27 +
with message-id
and subject line Bug#960120: fixed in node-yarnpkg 1.22.4-6
has caused the Debian Bug report #960120,
regarding node-yarnpkg: build with node-babel-loader 8.x (babel 7) fails
to be marked as done.
This means that you claim that
Package: swi-prolog
Version: 8.2.3+dfsg-1
Severity: serious
Forwarded: https://github.com/SWI-Prolog/packages-ssl/issues/159
Tag: patch
Hi,
Swi-prolog is failing to build using OpenSSL 1.1.1i. I've attached
a patch that fixes it.
Kurt
--- packages/ssl/test_ssl.pl.orig 2020-12-18
Package: m2crypto
Version: 0.36.0-1
Severity: serious
Forwarded: https://gitlab.com/m2crypto/m2crypto/-/issues/289
Hi,
m2crypto is failing to build since the 1.1.1i version of OpenSSL,
see the upstream bug report for more details.
Kurt
Your message dated Fri, 18 Dec 2020 09:52:00 +
with message-id
and subject line Bug#977621: fixed in murasaki 1.68.6-11
has caused the Debian Bug report #977621,
regarding murasaki: autopkgtest armhf regression: 6660 Bus error mbfa $f
--fasta > testfile
to be marked as done.
This means that
Processing control commands:
> severity -1 serious
Bug #977156 [screenkey] Please switch to Ayatana AppIndicator
Severity set to 'serious' from 'normal'
--
977156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: kde-spectacle
Version: 20.12.0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: christophercorm...@protonmail.com
Dear Maintainer,
Spectacle is unable to start after the libkimageannotator0 package updated to
0.4.0-1
When attempting to start it, it crashes with
Your message dated Fri, 18 Dec 2020 09:34:11 +
with message-id
and subject line Bug#908137: fixed in luajit 2.1.0~beta3+dfsg-5.2
has caused the Debian Bug report #908137,
regarding luajit: lightuserdata problem with > 47 bit address space on arm64
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> found 977649 kimageannotator/0.4.0-1
Bug #977649 [src:kimageannotator] bumped SONAME without name change
Marked as found in versions kimageannotator/0.4.0-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing control commands:
> tags -1 patch pending
Bug #908137 [src:luajit] luajit: lightuserdata problem with > 47 bit address
space on arm64
Added tag(s) pending and patch.
--
908137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908137
Debian Bug Tracking System
Contact
control: tags -1 patch pending
NMU uploaded in sid
G.
On Mon, 5 Oct 2020 13:57:12 +0200 Santiago Ruano =?iso-8859-1?Q?Rinc=F3n?=
wrote:
> Control: tags -1 fixed-upstream
>
> On Thu, 06 Sep 2018 16:54:30 +0300 Adrian Bunk wrote:
> > Source: luajit
> > Version: 2.0.4+dfsg-1
> > Severity:
Processing commands for cont...@bugs.debian.org:
> tags 919058 - pending
Bug #919058 [itstool] its-tools: crashes when freeing xmlDocs
Bug #948781 [itstool] debmake-doc: FTBFS: Segmentation fault
Removed tag(s) pending.
Removed tag(s) pending.
> thanks
Stopping processing here.
Please contact me
Your message dated Fri, 18 Dec 2020 09:04:53 +
with message-id
and subject line Bug#971933: fixed in rheolef 7.1-2
has caused the Debian Bug report #971933,
regarding src:rheolef: rheolef FTBFS: ...cut-bisector.eps: No such file or
directory
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> tags 665334 + bullseye-ignore
Bug #665334 [fontforge] non-DFSG postscript embedded in fontforge (currently
August 2014
Added tag(s) bullseye-ignore.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
665334:
Processing commands for cont...@bugs.debian.org:
> tags 694320 + bullseye-ignore
Bug #694320 [gsfonts] [gsfonts] Fonts include copyrighted adobe fragment all
right reserved
Bug #694321 [gsfonts] [gsfonts] Fonts include copyrighted adobe fragment all
right reserved
Added tag(s) bullseye-ignore.
On Fri, Dec 18, 2020 at 01:53:22PM +0900, Takatsugu Nokubi wrote:
> https://salsa.debian.org/debian/uim/-/merge_requests/9
>
> This is the fix request.
> Could you review the patch?
Thank you for your works. Reviewed and merged.
--
Regards,
dai
GPG Fingerprint = 0B29 D88E 42E6 B765
Processing commands for cont...@bugs.debian.org:
> reassign 977649 src:kimageannotator
Bug #977649 [kde-spectacle] kde-spectacle: Spectacle no longer starts after an
update to libkimageannotator0
Bug reassigned from package 'kde-spectacle' to 'src:kimageannotator'.
No longer marked as found in
1 - 100 of 103 matches
Mail list logo
