Hi Sebastian,
On 05-02-2020 20:35, Sebastian Ramacher wrote:
> libstk bumped its SOAME. So please schedule rebuilds for its reverse
> dependencies:
>
> nmu csound_1:6.13.0~dfsg-3 . ANY . unstable . -m "Rebuild against
> libstk-4.6.1"
> dw csound_1:6.13.0~dfsg-3 . ANY . -m "libstk0-dev (>= 4.6.1)
Control: reassign -1 ftp.debian.org
Hi kpcyrd,
On 30-01-2020 17:24, Paul Gevers wrote:
> I assume you actually want the removal from unstable? Than the bug
> should be reassigned to ftp.debian.org.
I went ahead and reassigned. Please reassign back if you really only
want it removed from testing,
Processing control commands:
> reassign -1 ftp.debian.org
Bug #950255 [release.debian.org] RM: rust-pcap -- ROM; no longer in use
Bug reassigned from package 'release.debian.org' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #950255 to the same values
previously set
Ignorin
Processing control commands:
> tags -1 moreinfo
Bug #950342 [release.debian.org] RM: volatility/2.6.1-1
Added tag(s) moreinfo.
--
950342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 moreinfo
Hi Sandro,
On 31-01-2020 16:02, Sandro Tosi wrote:
> Please remove volatility from testing; volatility is the last reverse
> dependency of python-openpyxl, which can then be dropped.
>
> I've already filed an RC bug against src:volatility to keep it out of testing.
Bu
Your message dated Thu, 6 Feb 2020 11:31:10 +0100
with message-id <9d18f060-900c-f039-051f-668b3f874...@debian.org>
and subject line Re: release.debian.org: unblock: ltsp/19.11-1
has caused the Debian Bug report #945815,
regarding release.debian.org: unblock: ltsp/19.11-1
to be marked as done.
Thi
Your message dated Thu, 6 Feb 2020 11:37:58 +0100
with message-id <56629f6a-5278-b1fa-3622-f5873d659...@debian.org>
and subject line Re: Bug#948589: nmu: file_1:5.38-3
has caused the Debian Bug report #948589,
regarding nmu: file_1:5.38-3
to be marked as done.
This means that you claim that the pr
Your message dated Thu, 6 Feb 2020 11:41:48 +0100
with message-id <4f240378-deab-eee4-3553-57d5d9db2...@debian.org>
and subject line Re: Bug#946119: binNMU for gudhi, openems, and pygalmesh
has caused the Debian Bug report #946119,
regarding binNMU for gudhi, openems, and pygalmesh
to be marked as
Your message dated Thu, 6 Feb 2020 11:45:03 +0100
with message-id
and subject line Re: Bug#941793: nmu:
libimobiledevice_1.2.1~git20181030.92c5462-1
has caused the Debian Bug report #941793,
regarding nmu: libimobiledevice_1.2.1~git20181030.92c5462-1
to be marked as done.
This means that you cla
Your message dated Thu, 6 Feb 2020 11:48:19 +0100
with message-id
and subject line Re: dw: irssi-plugin-otr_1.0.2-4 irssi-plugin-robustirc_0.6-4
irssi-plugin-xmpp_0.54-2
has caused the Debian Bug report #904545,
regarding nmu: irssi-plugin-otr_1.0.2-4 against new irssi-dev
to be marked as done.
Hi Paul,
On Sat, 15 Jun 2019 01:17:51 +0800 Paul Wise wrote:
> In order to implement the request below (hide some suggestions from
> tracker.d.o during the freeze (and possibly other things)), we need a
> machine-readable information source about the current stage of the
> freeze and what that me
On Thu, 2020-02-06 at 12:02 +0100, Paul Gevers wrote:
> We already have a maintained agenda for the team [1]. Would it make
> sense to use that somehow?
That doesn't appear to have enough info right now, it contains only the
unblock deadline and not the other freeze data.
> I fear that having an
Your message dated Thu, 6 Feb 2020 12:54:47 +0100
with message-id <20200206115444.ga4...@debian.org>
and subject line Re: britney crashes when trying removal multiple times
has caused the Debian Bug report #945471,
regarding britney crashes when trying removal multiple times
to be marked as done.
Hi,
On 06-02-2020 12:25, Paul Wise wrote:
> On Thu, 2020-02-06 at 12:02 +0100, Paul Gevers wrote:
>
>> We already have a maintained agenda for the team [1]. Would it make
>> sense to use that somehow?
>
> That doesn't appear to have enough info right now, it contains only the
> unblock deadline
Hi Otto, kodi maintainers,
On 02-02-2020 11:56, Otto Kekäläinen wrote:
> Ok, I will amend the changelog and re-upload today 1:10.3.22-0... to
> buster updates.
The autopkgtest of kodi fails on ppc64el (twice) with the p-u version of
MariaDB, while it passes with the old MariaDB version. I'll retr
> tail: cannot open '/home/debci/.kodi/temp/kodi.log' for reading: No such file
> or directory
> tail: no files remaining
This is the only output in the test log, otherwise it is installing
packages and everything else seemed to go fine.
Test source says it just starts the app, but now it does n
Hi Otto,
On 06-02-2020 14:10, Otto Kekäläinen wrote:
>> tail: cannot open '/home/debci/.kodi/temp/kodi.log' for reading: No such
>> file or directory
>> tail: no files remaining
>
> This is the only output in the test log, otherwise it is installing
> packages and everything else seemed to go fi
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The proposed update will fix CVE-2019-16770 (#946312) for Buster users. The
security team marked the issue no-dsa and asked to schedu
Processing commands for cont...@bugs.debian.org:
> forwarded 950716 https://release.debian.org/transitions/html/ruby2.7.html
Bug #950716 [release.debian.org] transition: ruby2.7
Set Bug forwarded-to-address to
'https://release.debian.org/transitions/html/ruby2.7.html'.
> forwarded 950490 https://
Hi all,
On 06-02-2020 15:11, Paul Gevers wrote:
> Yes, and I am worried about that. If the MariaDB upgrade causes kodi to
> not run, that's a bad regression, don't you think?
>
> kodi has a pretty good history in Ubuntu on ppc64el, so I don't expect
> it to be flaky at first sight.
I'm unhappy w
Hi All,
Paul Gevers ezt írta (időpont: 2020. febr. 6., Cs, 20:17):
>
> Hi all,
>
> On 06-02-2020 15:11, Paul Gevers wrote:
> > Yes, and I am worried about that. If the MariaDB upgrade causes kodi to
> > not run, that's a bad regression, don't you think?
> >
> > kodi has a pretty good history in U
On Thu, 2020-02-06 at 13:32 +0100, Paul Gevers wrote:
> That is mostly because they have not been settled 100% yet.
Sorry, I meant for the buster release, which is done now. There is
still data for the last wheezy point release but nothing for the freeze
for buster or bullsye; I thought the freez
Control: tags -1 -moreinfo
> But it still has a reverse dependency. I think that package should get
> time drop the dependency first, don't you think (it seems to me that
> it's a meta-package that could easily do that)?
`forensics-all` is a metapackage from `src:forensics-all`, and i
thought we
Processing control commands:
> tags -1 -moreinfo
Bug #950342 [release.debian.org] RM: volatility/2.6.1-1
Removed tag(s) moreinfo.
--
950342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
24 matches
Mail list logo
