Hi Raphaƫl,
Raphael Hertzog (2018-08-21):
> On Fri, 23 Mar 2018, Hideki Yamane wrote:
> > It's not a problem, but we can improve it, IMO (so severity is low).
>
> So you tried to fix a non-problem... and while doing so you introduced
> a real problem.
>
> While cleaning up the list of scripts
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 21 Aug 2018 17:50:31 +0200
Source: partman-auto-lvm
Binary: partman-auto-lvm
Architecture: source
Version: 70
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team
Changed-By: Philipp
partman-auto-lvm_70_source.changes uploaded successfully to localhost
along with the files:
partman-auto-lvm_70.dsc
partman-auto-lvm_70.tar.xz
partman-auto-lvm_70_amd64.buildinfo
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Your message dated Tue, 21 Aug 2018 16:19:29 +
with message-id
and subject line Bug#515607: fixed in partman-auto-lvm 70
has caused the Debian Bug report #515607,
regarding partman-auto-lvm: ask how much VG space to use
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 21 Aug 2018 16:19:29 +
with message-id
and subject line Bug#904184: fixed in partman-auto-lvm 70
has caused the Debian Bug report #904184,
regarding Partman(-lvm) claims all disk when it shouldn't
to be marked as done.
This means that you claim that the problem has
On 2018-08-20 00:44, Steve McIntyre wrote:
On Tue, Aug 14, 2018 at 02:08:06PM +0200, Philipp Kern wrote:
https://salsa.debian.org/installer-team/partman-auto-lvm/merge_requests/1/diffs?commit_id=ac7bdd5b4e3cbeec24c7ecdd5e96f8fcfa7b9ee1
aims to import a patch from Ubuntu to introduce an
Processing control commands:
> tag -1 pending
Bug #852646 [task-xfce-desktop] task-xfce-desktop should recommend atril rather
than evince
Added tag(s) pending.
--
852646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Hi,
I noticed that the latest upload of console-setup fails to
migrate to testing.
It claims being "uninstallable on amd64", while
https://buildd.debian.org/status/fetch.php?pkg=console-setup=all=1.185=1534275854=0
says that the build was successful.
How can I find out what is wrong here?
Hi,
On Fri, 23 Mar 2018, Hideki Yamane wrote:
> It's not a problem, but we can improve it, IMO (so severity is low).
So you tried to fix a non-problem... and while doing so you introduced
a real problem.
While cleaning up the list of scripts to keep, you decided to drop the
scripts for all
9 matches
Mail list logo