Are you using encryption or compression in MariaDB which
percona-xtrabackup does not support? In that case you need
mariabackup: https://mariadb.com/kb/en/library/mariadb-backup-overview/
Otherwise I am not aware of any reasons percona-xtrabackup would not
work, it should.
Oh, noticed that I forgot to put "(closes: # 903065)" in the change log.
On Fri, Jul 6, 2018 at 12:16 AM Tong Sun
wrote:
> Hi Helmut,
>
> I've done the update and upload:
>
> $ dput ftp-master ../dbab_1.3.2-2_source.changes
> Checking signature on .changes
> gpg: ../dbab_1.3.2-2_source.changes:
Control: retitle -1 mercurial: CVE-2018-13346 CVE-2018-13347 CVE-2018-13348
Control: found -1 3.1.2-1
Hi,
On Fri, Jun 08, 2018 at 02:31:50PM +0200, Salvatore Bonaccorso wrote:
> Source: mercurial
> Version: 4.6-2
> Severity: grave
> Tags: security upstream
>
> For tracking purposes: mercurial
Helmut,
Thanks so much for the heads up. I’ll fix that now!
Stephen
> On Jul 5, 2018, at 1:18 PM, Helmut Grohne wrote:
>
> Source: git-lfs
> Version: 2.4.2-1
> Severity: serious
>
> Since ronn got split out of ruby-ronn, git-lfs fails to build from
> source. It was not possible to have
Processing control commands:
> retitle -1 mercurial: CVE-2018-13346 CVE-2018-13347 CVE-2018-13348
Bug #901050 {Done: Julien Cristau } [src:mercurial]
mercurial: New security fixes release (4.6.1)
Changed Bug title to 'mercurial: CVE-2018-13346 CVE-2018-13347 CVE-2018-13348'
from 'mercurial: New
Hi Helmut,
I've done the update and upload:
$ dput ftp-master ../dbab_1.3.2-2_source.changes
Checking signature on .changes
gpg: ../dbab_1.3.2-2_source.changes: Valid signature from 885FDAB331FED834
Checking signature on .dsc
gpg: ../dbab_1.3.2-2.dsc: Valid signature from 885FDAB331FED834
Processing commands for cont...@bugs.debian.org:
> block 895411 by 902263
Bug #895411 [anki] anki: Anki raises exception instead of starting (Exception:
Qt 5.10 is known to be buggy.)
895411 was not blocked by any bugs.
895411 was not blocking any bugs.
Added blocking bug(s) of 895411: 902263
>
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package
> src:golang-github-kardianos-osext
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package ruby-json-jwt
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:astroid
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Your message dated Fri, 06 Jul 2018 00:34:53 +
with message-id
and subject line Bug#903057: fixed in espeak-ng 1.49.2+dfsg-3
has caused the Debian Bug report #903057,
regarding espeak-ng FTBFS: update Build-Depends: ruby-ronn -> ronn
to be marked as done.
This means that you claim that the
Processing control commands:
> severity -1 normal
Bug #900181 [src:camp] camp: FTBFS on 32bit big endian: check
metaclass->function("f4").call(object, camp::Args(1, 4, 15)).to() == 20 has failed
Severity set to 'normal' from 'serious'
> tag -1 ftbfs
Bug #900181 [src:camp] camp: FTBFS on 32bit
Control: severity -1 normal
Control: tag -1 ftbfs
camp has been removed from mips and powerpc ... downgrading the severity
accordingly
Andreas
Processing commands for cont...@bugs.debian.org:
> severity 902827 normal
Bug #902827 [src:agda] FTBFS: GHC OOM on armel/armhf
Severity set to 'normal' from 'serious'
> quit
Stopping processing here.
Please contact me if you need assistance.
--
902827:
Processing commands for cont...@bugs.debian.org:
> tags 903057 + pending
Bug #903057 [src:espeak-ng] espeak-ng FTBFS: update Build-Depends: ruby-ronn ->
ronn
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
903057:
On Fri, 06 Jul 2018 at 00:51:02 +0200, Korbinian Demmel wrote:
> I played around with the 'lvm2' script. Support to get the mangled
> source device (LG/LV) for an given LV UUID is quite simple to add.
It's not the LV UUID that we need here, but the LUKS UUID. And the
script doesn't know which
Hello Guilhem,
thank you very much for the detailed response.
Not forever, though. It drops to a debug shell after ‘rootdelay’
(default 180) seconds, [...]
Right. Too long to wait ;)
I read through your mail, but obviously lack some context.
I played around with the 'lvm2' script. Support
Control: tag -1 pending
Hello,
Bug #902800 in glibc 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 #902800 [src:glibc] glibc FTBFS: dh_installdocs: Cannot find (any matches
for) "BUGS" (tried in .)
Added tag(s) pending.
--
902800: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902800
Debian Bug Tracking System
Contact
Your message dated Thu, 05 Jul 2018 21:39:29 +
with message-id
and subject line Bug#903073: fixed in unburden-home-dir 0.4.1.1
has caused the Debian Bug report #903073,
regarding unburden-home-dir FTBFS: update Build-Depends: ruby-ronn -> ronn
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> limit source php-symfony-polyfill
Limiting to bugs with field 'source' containing at least one of
'php-symfony-polyfill'
Limit currently set to 'source':'php-symfony-polyfill'
> tags 895604 + pending
Bug #895604 [src:php-symfony-polyfill]
Your message dated Thu, 05 Jul 2018 21:22:28 +
with message-id
and subject line Bug#903068: fixed in shapelib 1.4.1-2
has caused the Debian Bug report #903068,
regarding shapelib FTBFS: update Build-Depends: ruby-ronn -> ronn
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 05 Jul 2018 21:19:41 +
with message-id
and subject line Bug#903067: fixed in duc 1.4.3-4
has caused the Debian Bug report #903067,
regarding duc FTBFS: update Build-Depends: ruby-ronn -> ronn
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> tags 903067 + pending
Bug #903067 [src:duc] duc FTBFS: update Build-Depends: ruby-ronn -> ronn
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
903067:
Control: tags -1 pending
The issue is fixed in git and a new upload to unstable will follow shortly.
Kind Regards,
Bas
Processing control commands:
> tags -1 pending
Bug #903068 [src:shapelib] shapelib FTBFS: update Build-Depends: ruby-ronn ->
ronn
Added tag(s) pending.
--
903068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> tags 903073 + pending
Bug #903073 [src:unburden-home-dir] unburden-home-dir FTBFS: update
Build-Depends: ruby-ronn -> ronn
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
903073:
Processing commands for cont...@bugs.debian.org:
> retitle 903047 Netinst image unable to load some modules critical for install
Bug #903047 [installation-reports] Netinst image cannot load e1000e, ixgbe, igb
eth. drivers
Changed Bug title to 'Netinst image unable to load some modules critical
Processing commands for cont...@bugs.debian.org:
> # *sigh*
> tags 903073 + confirmed
Bug #903073 [src:unburden-home-dir] unburden-home-dir FTBFS: update
Build-Depends: ruby-ronn -> ronn
Added tag(s) confirmed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Your message dated Thu, 05 Jul 2018 19:34:56 +
with message-id
and subject line Bug#902516: fixed in python-matplotlib-venn 0.11.5-5
has caused the Debian Bug report #902516,
regarding python-matplotlib-venn: FTBFS in buster/sid (failing tests)
to be marked as done.
This means that you claim
I just discovered that other modules seem to be affected as well, for example
dm-mod does not load for the same reason, so it's not possible to partition with
anything that requires devicemapper...
signature.asc
Description: signature
Your message dated Thu, 05 Jul 2018 21:08:34 +0200
with message-id
and subject line Re: Cannot install, depends on non-existant yubico-piv-tool
>=1.4.3
has caused the Debian Bug report #875719,
regarding Cannot install, depends on non-existant yubico-piv-tool >=1.4.3
to be marked as done.
This
Thank you Helmut for explaining the reason and the fix.
Will do tonight...
On Thu, Jul 5, 2018 at 2:45 PM Helmut Grohne wrote:
> Package: dbab
> Version: 1.3.2-1
> Severity: serious
>
> Since ronn got split out of ruby-ronn, dbab fails to build from source.
> It was not possible to have
Source: ledger-wallets-udev
Version: 0.1
Severity: serious
Since ronn got split out of ruby-ronn, ledger-wallets-udev fails to
build from source. It was not possible to have ruby-ronn temporarily
depend on ronn, because that would have created a dependency cycle.
Please update Build-Depends and
Source: r10k
Version: 2.6.2-2
Severity: serious
Since ronn got split out of ruby-ronn, r10k fails to build from source.
It was not possible to have ruby-ronn temporarily depend on ronn,
because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn with ronn
Source: brutespray
Version: 1.6.0-1
Severity: serious
Since ronn got split out of ruby-ronn, brutespray fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace
Source: haproxyctl
Version: 1.3.0-2
Severity: serious
Since ronn got split out of ruby-ronn, haproxyctl fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace
Source: unburden-home-dir
Version: 0.4.1
Severity: serious
Since ronn got split out of ruby-ronn, unburden-home-dir fails to build
from source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and
Source: foodcritic
Version: 13.1.1-1
Severity: serious
Since ronn got split out of ruby-ronn, foodcritic fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace
Source: seqprep
Version: 1.3.2-2
Severity: serious
Since ronn got split out of ruby-ronn, seqprep fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn
Source: qiime
Version: 1.9.1+dfsg-2
Severity: serious
Since ronn got split out of ruby-ronn, qiime fails to build from source.
It was not possible to have ruby-ronn temporarily depend on ronn,
because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn
Source: ruby-coveralls
Version: 0.8.21-1
Severity: serious
Since ronn got split out of ruby-ronn, ruby-coveralls fails to build
from source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and
Source: python-base58
Version: 1.0.0-1
Severity: serious
Since ronn got split out of ruby-ronn, python-base58 fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace
Source: git-extras
Version: 4.5.0-1
Severity: serious
Since ronn got split out of ruby-ronn, git-extras fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace
Package: coquelicot
Version: 0.9.6-1
Severity: serious
Since ronn got split out of ruby-ronn, coquelicot fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace
Source: duc
Version: 1.4.3-3
Severity: serious
Since ronn got split out of ruby-ronn, duc fails to build from source.
It was not possible to have ruby-ronn temporarily depend on ronn,
because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn with ronn
Source: slt
Version: 0.0.git20140301-4
Severity: serious
Since ronn got split out of ruby-ronn, slt fails to build from source.
It was not possible to have ruby-ronn temporarily depend on ronn,
because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn
Source: espeak-ng
Version: 1.49.2+dfsg-2
Severity: serious
Since ronn got split out of ruby-ronn, espeak-ng fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace
Source: foremancli
Version: 1.0-2
Severity: serious
Since ronn got split out of ruby-ronn, foremancli fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn
Source: shapelib
Version: 1.4.1-1
Severity: serious
Since ronn got split out of ruby-ronn, shapelib fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn
Source: git-lfs
Version: 2.4.2-1
Severity: serious
Since ronn got split out of ruby-ronn, git-lfs fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn
Package: curvedns
Version: 0.87-4
Severity: serious
Since ronn got split out of ruby-ronn, curvedns fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn
Source: decopy
Version: 0.2.3-2
Severity: serious
Since ronn got split out of ruby-ronn, decopy fails to build from
source. It was not possible to have ruby-ronn temporarily depend on
ronn, because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn with
Package: dbab
Version: 1.3.2-1
Severity: serious
Since ronn got split out of ruby-ronn, dbab fails to build from source.
It was not possible to have ruby-ronn temporarily depend on ronn,
because that would have created a dependency cycle. Please update
Build-Depends and replace ruby-ronn with
Your message dated Thu, 05 Jul 2018 17:07:35 +
with message-id
and subject line Bug#892993: fixed in sphinx-rtd-theme 0.4.0+dfsg-1
has caused the Debian Bug report #892993,
regarding sphinx-rtd-theme CSS is not properly rebuilt from source
to be marked as done.
This means that you claim that
On Thursday, 5 July 2018 08:09:50 AEST Andreas Tille wrote:
> Control: tags -1 help
>
> Hi,
>
> I can confirm this problem in a pbuilder environment. Unfortunately I
> have no idea about the cause of the issue nor how to fix it. Any hint
> from the Debian Python team?
Looks a lot like at
Your message dated Thu, 5 Jul 2018 19:41:59 +0300
with message-id <20180705164159.ga22...@mitya57.me>
and subject line Re: Bug#901567: unburden-home-dir: FTBFS: No such file or
directory:
'/usr/lib/python3/dist-packages/mkdocs/themes/readthedocs/fonts/fontawesome-webfont.woff'
has caused the
Your message dated Thu, 5 Jul 2018 19:41:59 +0300
with message-id <20180705164159.ga22...@mitya57.me>
and subject line Re: Bug#901567: unburden-home-dir: FTBFS: No such file or
directory:
'/usr/lib/python3/dist-packages/mkdocs/themes/readthedocs/fonts/fontawesome-webfont.woff'
has caused the
close 899324
thanks
Processing commands for cont...@bugs.debian.org:
> forcemerge 899124 899324
Bug #899124 {Done: Pirate Praveen } [fonts-font-awesome]
fonts-font-awesome: completely breaks web applications, with no notice
Bug #899124 {Done: Pirate Praveen } [fonts-font-awesome]
fonts-font-awesome: completely
Hi Ansgar,
On Mon, Jun 25, 2018 at 3:00 PM Ansgar Burchardt wrote:
>
> Package: blacs-pvm-test
> Version: 1.1-21+b1
> Severity: serious
>
> blacs-pvm-test depends on blacs-test-common which was just removed
> (#886711).
>
> I wonder if blacs-pvm is still useful? pvm was orphaned (#824403) and I
Processing commands for cont...@bugs.debian.org:
> reassign 899324 fonts-font-awesome
Bug #899324 [ruby-font-awesome-rails] ruby-font-awesome-rails: broken with
fonts-font-awesome 5
Bug reassigned from package 'ruby-font-awesome-rails' to 'fonts-font-awesome'.
No longer marked as found in
Processing commands for cont...@bugs.debian.org:
> close 899324
Bug #899324 [fonts-font-awesome] ruby-font-awesome-rails: broken with
fonts-font-awesome 5
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
899324:
Package: src:linux
Version: 4.9.82-1+deb9u3
Dear Maintainer,
while we were investigating a problem, we found that we are affected by this
bug.
We found some information you might find useful:
Another workaround than using an older kernel is to set the EnableSendFile
directive to on.
Package: installation-reports
Version: testing
Severity: critical
Justification: Unable to install debian with netinst image on systems with these
NICs
With the latest weekly Debian testing netinst image (06-25 and 07-02 tested),
the e1000e, ixgbe, and igb modules cannot load.
Attempting to do
Your message dated Thu, 05 Jul 2018 15:37:53 +
with message-id
and subject line Bug#902898: fixed in libreoffice 1:6.1.0~rc1-1
has caused the Debian Bug report #902898,
regarding libreoffice: missing versioned dependency to uno-libs3 >= 6.1
to be marked as done.
This means that you claim
Your message dated Thu, 05 Jul 2018 15:22:46 +
with message-id
and subject line Bug#902515: fixed in python-ghdiff 0.4-2
has caused the Debian Bug report #902515,
regarding python-ghdiff: FTBFS in buster/sid (Could not find suitable
distribution for Requirement.parse('chardet'))
to be marked
Your message dated Thu, 05 Jul 2018 15:22:29 +
with message-id
and subject line Bug#901243: fixed in mate-indicator-applet 1.20.1-1
has caused the Debian Bug report #901243,
regarding mate-indicator-applet got removed from buster due to ido build
dependency
to be marked as done.
This means
Package: percona-xtrabackup
Version: 2.2.3-2.1
Severity: grave
OS: Debian Stretch 4.9.88-1+deb9u1
Hi,
since the installation of the lastest version of mariadb-server
(10.1.26-0+deb9u1) the backup is broken.
"innobackupex: Error: Unsupported server version: '10.1.26-MariaDB-0+deb9u1'"
On Thu, 2018-07-05 at 15:06 +0200, Andreas Beckmann wrote:
> But the upgrade path from stretch is not clean:
>
> Selecting previously unselected package python3-cliapp.
> Preparing to unpack .../python3-cliapp_1.20170827-1_all.deb ...
> Unpacking python3-cliapp (1.20170827-1) ...
> dpkg:
Your message dated Thu, 05 Jul 2018 13:38:18 +
with message-id
and subject line Bug#903018: fixed in intel-microcode 3.20180703.1
has caused the Debian Bug report #903018,
regarding intel-microcode: Update intel-microcode to 20180703
to be marked as done.
This means that you claim that the
Your message dated Thu, 5 Jul 2018 15:30:04 +0200
with message-id
and subject line Re: Bug#900352: new xorg-server version causes a random
freezes in plasmashell
has caused the Debian Bug report #900352,
regarding xserver 1.20 must ensure it gets installed with a working mesa
to be marked as
On 2018-07-05 11:50, Lars Wirzenius wrote:
> On Wed, Jul 04, 2018 at 06:34:41PM +0300, Lars Wirzenius wrote:
>> (Also, the advice to use Replaces+Breaks is just wrong for this
>> package. The bug is that the same file is in both the python2 and
>> python3 versions of the package. The correct
Your message dated Thu, 05 Jul 2018 13:00:12 +
with message-id
and subject line Bug#896622: fixed in julia 0.6.3-1
has caused the Debian Bug report #896622,
regarding FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'
to be marked as done.
This means that you claim that the
Hi,
On Tue, Jul 03, 2018 at 03:59:01PM +0200, Andreas Tille wrote:
> the bug log of #790196[1] shows that rasmol in its current state will
> not be distributable with Buster. Upstream is dead so if we want to
> keep it in Debian we have the option:
>
>1) Port it to Gtk+ 3 (see porting guide
Your message dated Thu, 05 Jul 2018 12:24:08 +
with message-id
and subject line Bug#903003: fixed in soapaligner 2.20-3
has caused the Debian Bug report #903003,
regarding soapaligner should be limited to any-amd64 x32
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 05 Jul 2018 12:24:15 +
with message-id
and subject line Bug#902644: fixed in upower 0.99.8-2
has caused the Debian Bug report #902644,
regarding upower: no longer emits plug/unplug events after upgrade to 0.99.8
to be marked as done.
This means that you claim that the
Your message dated Thu, 05 Jul 2018 12:19:55 +
with message-id
and subject line Bug#902454: fixed in bochs 2.6-6
has caused the Debian Bug report #902454,
regarding bochs: FTBFS in buster/sid ('AmlCode' undeclared)
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 05 Jul 2018 12:06:19 +
with message-id
and subject line Bug#903029: fixed in network-manager 1.12.0-4
has caused the Debian Bug report #903029,
regarding network-manager-dev: nm-setting.h refers to nonexistent nm-version.h
to be marked as done.
This means that you
Processing control commands:
> tag -1 pending
Bug #892993 [src:sphinx-rtd-theme] sphinx-rtd-theme CSS is not properly rebuilt
from source
Added tag(s) pending.
--
892993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #892993 in sphinx-rtd-theme 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:
Your message dated Thu, 05 Jul 2018 12:06:04 +
with message-id
and subject line Bug#901859: fixed in libtcod 1.7.0+dfsg-2
has caused the Debian Bug report #901859,
regarding libtcod ftbfs on ppc64el
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing commands for cont...@bugs.debian.org:
> forwarded 902989 https://gitlab.gnome.org/GNOME/pyatspi2/issues/1
Bug #902989 [python3-pyatspi] python3-pyatspi: fresh installation breaks
Set Bug forwarded-to-address to
'https://gitlab.gnome.org/GNOME/pyatspi2/issues/1'.
> thanks
Stopping
On Wed, 4 Jul 2018 12:04:54 -0400 PICCORO McKAY Lenz wrote:
> Package: live-build
> Version: 1:20171207
> Severity: grave
>
> we need a mechanish to avoid bad or abuse of recommends in apt, this
> problem avoit the automatization of the process
>
> if we list the package subversion-tools, that
Processing commands for cont...@bugs.debian.org:
> tags 903018 + pending
Bug #903018 [intel-microcode] intel-microcode: Update intel-microcode to
20180703
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
903018:
On Thu, 05 Jul 2018, Markus Schade wrote:
> Intel has released a new microcode version which includes the prerequisites
> for SSBD patches
>
> https://downloadcenter.intel.com/download/27945/Linux-Processor-Microcode-Data-File
>
> Contrary to what the download page says, this is the most recent
Processing commands for cont...@bugs.debian.org:
> reopen 902990 =
Bug #902990 {Done: Ole Streicher } [src:python-fitsio]
FTBFS: bus error, alignment problems
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add
Your message dated Thu, 05 Jul 2018 11:04:08 +
with message-id
and subject line Bug#902990: fixed in python-fitsio 0.9.11+dfsg-2
has caused the Debian Bug report #902990,
regarding FTBFS: bus error, alignment problems
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> owner 902454 !
Bug #902454 [src:bochs] bochs: FTBFS in buster/sid ('AmlCode' undeclared)
Owner recorded as Stephen Kitt .
> tags 902454 + pending
Bug #902454 [src:bochs] bochs: FTBFS in buster/sid ('AmlCode' undeclared)
Added tag(s) pending.
>
Your message dated Thu, 5 Jul 2018 12:56:58 +0200
with message-id
and subject line Re: [Pkg-utopia-maintainers] Bug#903029: network-manager-dev:
nm-setting.h refers to nonexistent nm-version.h
has caused the Debian Bug report #903029,
regarding network-manager-dev: nm-setting.h refers to
Package: network-manager-dev
Version: 1.10.8-1
Severity: grave
Dear Maintainer,
The file /usr/include/NetworkManager/nm-setting.h contains “#include
"nm-version.h"” but the file “nm-version.h” is not installed.
Best,
C.
-- System Information:
Debian Release: buster/sid
APT prefers testing
Processing commands for cont...@bugs.debian.org:
> forwarded 903028 https://github.com/processone/ejabberd-contrib/issues/251
Bug #903028 [src:ejabberd-contrib] ejabberd-contrib: FTBFS with ejabberd >=
18.06
Set Bug forwarded-to-address to
Source: ejabberd-contrib
Severity: grave
Tags: upstream
ejabberd 18.06 is the first release to ship without jlib.hrl and
ejabberd.hrl, causing ejabberd-contrib to FTBFS because several modules
have not been updated yet.
Upstream report: https://github.com/processone/ejabberd-contrib/issues/251
Your message dated Thu, 05 Jul 2018 10:20:26 +
with message-id
and subject line Bug#902998: fixed in systemd 239-5
has caused the Debian Bug report #902998,
regarding libpam-systemd: breaks installing build depends e.g. gnupg2
to be marked as done.
This means that you claim that the problem
Package: virtualbox
Version: 5.2.14-dfsg-1
Followup-For: Bug #902897
Same here. Corresponding upstream bug report seems to be:
https://www.virtualbox.org/ticket/17851
VBox.log:
--
VirtualBox VM 5.2.14_Debian r122571 linux.amd64 (Jul 2 2018 17:50:29) release
log
00:00:00.504801 Log opened
Processing control commands:
> severity -1 important
Bug #902946 [systemd] Fails to load autofs module through autofs4 alias
Severity set to 'important' from 'serious'
--
902946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902946
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: severity -1 important
Am 03.07.2018 um 23:08 schrieb Michael Biebl:
> Am 03.07.2018 um 20:11 schrieb Ben Hutchings:
>> Package: systemd
>> Version: 239-1
>> Severity: serious
>>
>> Starting with Linux 4.18, the autofs4 kernel module is renamed
>> to autofs, but retaining an 'autofs4'
On Wed, Jul 04, 2018 at 06:34:41PM +0300, Lars Wirzenius wrote:
> (Also, the advice to use Replaces+Breaks is just wrong for this
> package. The bug is that the same file is in both the python2 and
> python3 versions of the package. The correct solution is to have it in
> at most one package. I
Your message dated Thu, 05 Jul 2018 09:37:54 +
with message-id
and subject line Bug#900109: fixed in xserver-xorg-video-savage 1:2.3.9-2
has caused the Debian Bug report #900109,
regarding xserver-xorg-video-savage: FTBFS with xserver 1.20
to be marked as done.
This means that you claim that
Your message dated Thu, 05 Jul 2018 09:37:49 +
with message-id
and subject line Bug#900110: fixed in xserver-xorg-video-r128 6.10.2-2
has caused the Debian Bug report #900110,
regarding xserver-xorg-video-r128: FTBFS with xserver 1.20
to be marked as done.
This means that you claim that the
1 - 100 of 113 matches
Mail list logo
