Package: virtualbox
Version: 5.0.4-dfsg-3
Severity: grave
Certain virtualbox packages seem to have vanished from sid with the
latest update.
I noticed two packages being held back when performing an upgrade on a
sid host - virtualbox and virtualbox-qt (5.0.4-dfsg-2 -> 5.0.4-dfsg-3).
When doing a
Package: libstdc++6
Version: 5.2.1-14
A bunch of packages are being withheld from being upgraded via apt on
my Sid install. These seem to relate to the gcc5 transition. One
reported dependency breakage that is holding most/all back is from
libstdc++6 against libboost-date-time1.55.0.
Bug #777805
Control: severity -1 critical
Control: tag -1 + security
This dependency issue is now blocking installation of security updates
on Sid (which many people use instead of stable, whether they should or
not), specifically the emergency patch to iceweasel (CVE-2015-4495) in
version 38.1.1esr-1.
--
table->testing transitions). It would be very much appreciated if
devs/maintainers would please keep this in mind in order to not cause
problems like this for such users.
On Sat, 2015-08-08 at 00:35 +0200, Matthias Klose wrote:
> Control: severity -1 important
>
> On 08/07/2015 09:11
Control: severity -1 critical
Control: tags -1 + security
As described in the bug report, the libboost-date-time1.55.0 package is
incompatible with GCC5 and will not be fixed, requiring a transition to
1.57 or 1.58. Unfortunately the GCC5 transition has already been taking
place on Sid (with libst
Control: severity -1 critical
Control: tags -1 + security
As described in the bug report, the libboost-date-time1.55.0 package is
incompatible with GCC5 and will not be fixed, requiring a transition to
1.57 or 1.58. Unfortunately the GCC5 transition has already been taking
place on Sid (with libst
Hey. Although there may not be security issues within this package
itself, and while the descriptions of severity [1] may not perfectly
cover this unfortunate scenario, an update to this package (and others)
is urgently needed in order for Sid users to be able to install
critical security patches (
Hey. Although there may not be security issues within this package
itself, and while the descriptions of severity [1] may not perfectly
cover this unfortunate scenario, an update to this package (and others)
is urgently needed in order for Sid users to be able to install
critical security patches (
On Sat, 2015-08-08 at 07:30 +0200, Matthias Klose wrote:
> You may have missed
>
> https://lists.debian.org/debian-devel-announce/2015/07/msg0.html
> https://lists.debian.org/debian-devel-announce/2015/08/msg0.html
> https://lists.debian.org/debian-devel-announce/2015/08/msg2.html
I d
c389bf6c04b7bbac133808b754eb83648f41f9d8 Mon Sep 17 00:00:00 2001
From: jnqnfe
Date: Sat, 22 Nov 2014 19:32:45 +
Subject: [PATCH] Fix creation of config/package-lists/live.list.chroot in
cases where --clean parameter used with lb config command and the directory
is empty.
---
scripts/build
ccd3cc003a6e83e102c3ddfcce6f8 Mon Sep 17 00:00:00 2001
From: jnqnfe
Date: Sat, 22 Nov 2014 21:20:29 +
Subject: [PATCH] Fix broken calls to Get_conffiles() from Read_conffiles() and
Print_conffiles().
---
functions/conffile.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -
:00 2001
From: jnqnfe
Date: Mon, 24 Nov 2014 06:36:09 +
Subject: [PATCH] Fix typo in variable name (LH_LINUX_FLAVOURS instead of
LB_LINUX_FLAVOURS) in installer_debian-installer script, affecting the armel
architecture.
---
scripts/build/installer_debian-installer | 2 +-
1 file changed, 1
From: jnqnfe
Date: Mon, 24 Nov 2014 19:40:30 +
Subject: [PATCH] Address "should check that we're building on debian through
e.g. a 'derivative-is-based-on' variable or somesuch" fixme.
---
functions/defaults.sh| 1 +
scripts/build/chroot
se
packages back and forth for later parts of the build process that use the
packages.binary cache also slows down the build process a little.
From 2fc67f16e0bef68613e9b3d0d0db23beaf7d2c14 Mon Sep 17 00:00:00 2001
From: jnqnfe
Date: Tue, 25 Nov 2014 19:28:13 +
Subject: [PATCH] Fix chroot_packa
Control: reopen -1
It's happening again.
On Sun, 2015-05-17 at 15:08 +0100, jnqnfe wrote:
> Control: close -1
> Control: archive -1
>
> Update: To my surprise, the problem seems to have disappeared.
>
> What changed?
> 1) A handful of minor package updates since
Package: sane
Version: 1.0.24-10
Install errors updating Sid amd64 installation:
> tester@testPC:~$ sudo aptitude upgrade
> Resolving dependencies...
> The following NEW packages will be installed:
> libnuma1{a} libx265-51{a}
> The following packages will be upgraded:
> ffmp
On Fri, 2015-05-15 at 04:58 +0200, Cyril Brulebois wrote:
> Control: tag -1 pending
>
> jnqnfe (2015-01-15):
> > Package: debootstrap
> > Severity: important
> > Tags: security patch
> >
> > In the event of a GPG keyring not being found, debootstrap may f
Package: linux-image-4.0.0-1-amd64
Version: 4.0.2-1
For the past few days I have noticed that my keyboard is non-functional
for about 60 seconds during boot of a Sid install. I was initially
writing up a report specifically about that, but I have found some info
in dmesg about the underlying cause
Control: close -1
Control: archive -1
Update: To my surprise, the problem seems to have disappeared.
What changed?
1) A handful of minor package updates since it last occurred, nothing
jumps out at me as something that might affect this.
2) Having noticed that one of the fans on my GPU has stoppe
Package: live-build
Version: 5.0~a2-1
Tags: patch
The new file 'functions/chroot_bind_path.sh' added in v5.0~a2-1 has the
wrong permission mode - 644 instead of 755.
The attached patch corrects this.
commit e64c30dfc4d23fd7df39a4bd53d2cac5342dec72
Author: jnqnfe
Date: Thu Feb 5 03:
Control: retitle -1 autorun.inf improvements
thanks
Updated patch, rebased on latest changes in git
commit 1f1ad6a6aba20a0fc0938198c0a24fb85e7c6cc8
Author: jnqnfe
Date: Wed Dec 10 05:24:53 2014 +
Improve autorun.inf
diff --git a/tools/boot/jessie/boot-hurd b/tools/boot/jessie/boot
Rebased copy attached.
Specifically this was just done to take into account the bug #774200
improvement (using same trace file download logic in binary_disk as in
source_disk). So only that small piece of code in binary_disk should
have changed since the last upload (excluding hashs/timestamps obv
Reworked patch, removing the change/addition in keyrings used for
verification. (Leaving that up to Daniel to deal with if/as necessary).
So this just brings some general code improvements now.
(Note, patches still built upon secure-wget work).
773775_v3.tar.gz
Description: GNU Zip compressed da
Package: live-build
When generating the autorun.inf file, live-build is appending rather
than replacing the file contents. I have a test image that I've rebuilt
several times in doing LB dev work, which has ended up with this file
having multiple repeat copies of the correct content. I expect user
> can somone with a with a windows system find out?
I have a Windows 8.1 install to hand, and it seems to be happy with it
as is (autorun is disabled for security reasons, but the icon is shown).
I have no idea about older versions though.
Microsoft documentation [1] says nothing about line endin
On 08/02/2015 01:28, Richard Nelson wrote:
> For live-medium-install I changed my dependecy from
> syslinx-themes-debian to desktop-base which happens to include
> /usr/share/images/desktop-base/lines-grub.png. Perhaps this could be
> just copied to isolinux.png since I am using it and it appears
On 09/02/2015 04:24, Richard Nelson wrote:
> First forgive me for not taking the time to say "Thank you" to
> Juliette for the very, very nice theme!
Indeed!
> To me it seems very redundent to have multiple backgrounds for boot
> loaders. I am sure there is some technical reason, but the menuing
Package: live-config
Version: 4.0.4-1
With a Debian sid amd64 live image, based on the gnome-desktop
live-image config, I cannot load gnome terminal. It turns out that this
is due to the locale not being set correctly.
The workaround is to click on the locale in the gnome control center (to
actua
Package: debian-installer
Severity: important
As already described in the users mailing list [1], I have a Debian sid
amd64 install in a VM, using EFI, GPT, btrfs and luks, which after
installation is left broken.
So far, I have identified:
1) that the initrd of this install is lacking at least c
I have tried to do an identical install using (graphical) expert mode
this time, leaving initrd on 'generic'. This results in the same problem:
[0.00 ] tsc: Fast TSC calibration failed
Loading, please wait...
Gave up waiting for root device. Common problems:
ALERT! /dev/mapper/sda3_crypt
> So far, I have identified:
> 1) that the initrd of this install is lacking at least cryptsetup.
> 2) that an identical install, with the exception of using ext4 instead
> of btrfs, works perfectly fine (at least in terms of booting, I have not
> checked issue #3 from the mailing list discussion).
control: reassign -1 initramfs-tools
control: retitle -1 initramfs-tools: fails to work with btrfs
control: severity -1 grave
I think that my issues might all stem from initramfs-tools, so reassigning.
Firstly, I cannot run update-initramfs within a chroot via a live CD against
this btrfs based
On 11/02/2015 05:05, Ben Hutchings wrote:
> On Wed, 2015-02-11 at 03:04 +0000, jnqnfe wrote:
>> I think that my issues might all stem from initramfs-tools, so
>> reassigning.
> I don't think so - other packages hook into initramfs-tools and are
> quite capable of br
On 11/02/2015 19:06, Daniel Baumann wrote:
> nothing, only the svg was missing, thanks.
>
> Regards,
> Daniel
Why are we now using the simple black syslinux theme instead of the
official install disc theme?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
On 11/02/2015 18:42, Ben Hutchings wrote:
> So the root (no pun intended) of the problem is that btrfs-tools was
> not installed. Ben.
Ah ha, you're absolutely right, I assumed it was but it is indeed not
installed. Thanks for that.
Yep, now it boots successfully :D
--
To UNSUBSCRIBE, email
Control: close -1
Control: archive -1
As identified in bug #777578, btrfs-tools was not installed during the
installation, which was the real cause of the issues I was experiencing.
So on the assumption that a resolution to that issue would successfully
allow cryptsetup to be added to the initrd w
Just ftr, so people don't think I'm a total idiot, I'd read in several
places that there was no fsck for btrfs, so I was deliberately ignoring
the missing btrfs.fsck warning and assuming it had been installed.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject o
On 12/02/2015 04:27, Daniel Baumann wrote:
> On 02/11/15 20:19, jnqnfe wrote:
>> Why are we now using the simple black syslinux theme instead of the
>> official install disc theme?
> it's the one Juliette provided in her tarball.
Right, but Juliette is only going by the st
On 13/02/2015 14:08, Michal Suchanek wrote:
> the build still fails when multiple kernel flavours are installed and
> multiple kernels of the same flavour are installed. Live-build contains
> this code:
> mv binary/${_INITRAMFS}/vmlinuz-*-${_FLAVOUR}
> binary/${_INITRAMFS}/vmlinuz${_NUMBER}
> Obv
On 13/02/2015 14:21, Michal Suchanek wrote:
> When you change the live architecture and don't delete the cache
> directory bootstrap of the old architecture is restored from cache and
> image of the old architecture is built.
>
> This is trivially solved by including the architecture name in the
>
On 13/02/2015 15:53, Michal Suchanek wrote:
> Man page says:
>
>lb_build(1)
> alias for all stages
>
> lb build says:
>
> [2015-02-13 15:12:21] lb build
> W: No config/ directory; using defaults for all options
> P: live-build 4.0.5
>
> This is clearly not true.
>
> lb co
Package: partman-lvm
Severity: important
Partitioning froze up during LVM creation in the following scenario.
Using a virtualbox VM I attempted an installation of Debian sid amd64.
For this I used the installer in a live CD I built with a dev copy of
live-build (I have been working on adding EFI
Package: libparted
After creating a RAID0 device via motherboard firmware, and installing
mdadm, applying a partition table using gparted (gpt) resulted in
gparted issuing an error.
The error reads:
Title: Libparted bug found!
Message: Invalid argument during seek for read on /dev/sdb
Note, It w
Package: gparted
When trying to create a partition table on a RAID0 device I encountered
a glitch in the rendering of the device drop down. See attached image.
Error reoccurs upon reopening gparted if you shut down gparted after the
failed creation of a gpt partition table.
If you successfully create an msdos partition table and reopen, no error
from the previous gpt failure (I don't know whether creating an msdos
partition table wipes any gpt table, so
Forgot to mention, glitch is corrected upon moving the mouse over it.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
No problem, and thanks for taking care of that :)
On Tue, 2015-02-17 at 21:45 +0100, juliette Belin wrote:
> Hi,
>
>
> i'm very busy this month, sorry for the delay!
>
>
> I assume I am correct in thinking that you had no intention
> for any of
> the boot screen (grub/s
Package: libparted2
Severity: grave
With a 'fake RAID' RAID0 device constructed using motherboard firmware,
which has a GPT partitioning table setup using fdisk (gparted failed me
- see #778683), opening gparted now results in errors in relation to the
RAID member disks.
Specifically, I firstly g
Investigating with fdisk I discovered that after this the second disk in
the array was reported to have the following issue: 'MBR/GPT
mismatches'.
I managed to get things fixed and the partition table created
successfully with fdisk instead.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@
Package: gnome-system-monitor
Version: 3.14.1-1
Gnome system monitor is reporting inaccurate disk usage information.
Example (1TB HDD):
total: 984.4GB
available: 46.7 GB
used: 887.7 GB
95% full
887.7 + 46.7 = 934.4, not 984.4
The used amount is correct, as is the total (I believe), but the amou
These errors actually disappeared after a reboot :/ ...
I guess that means I should have refreshed something, or fdisk should
have refreshed something, and thus this can be closed?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Co
Control: close -1
thanks
(resending, forgot to cc bug)
On Wed, 2015-02-18 at 13:14 -0500, Phillip Susi wrote:
> tags 778683 + moreinfo
> thanks
>
> I can't really follow your very well, but it sounds like you did
> simply select the wrong device in gparted. If you can reproduce this
> using jus
Package: libparted2
Version: 3.2-6
Severity: grave
libparted2 breaks my RAID GPT header!
There appears to be a disagreement between parted and fdisk as to the
correct size. fdisk is happy after creating a GPT partition table, but
parted is not and seems to be forcibly applying what it believes to
On Wed, 2015-02-18 at 16:35 -0500, Phillip Susi wrote:
> On 2/18/2015 4:05 PM, jnqnfe wrote:
> > Background = I have a 'fake-raid' RAID0 array,
> > created from two HDDs using my motherboard firmware. This is not
> > used for root, just data.
>
&
On Tue, 2015-02-17 at 06:34 +, Steve McIntyre wrote:
> Control: tag -1 +pending
>
> On Thu, Feb 05, 2015 at 07:16:22PM +0000, jnqnfe wrote:
> >Control: retitle -1 autorun.inf improvements
> >thanks
> >
> >Updated patch, rebased on latest changes in git
I had a quick look over your patch. You're building it against
live-build 3.x, but since it's a feature improvement not a "critical
bug in core functionality", I believe I'm right in saying that you must
build against live-build 4.x, preferably the debian-next branch, if you
want to get it accepte
6_64)
>
> Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
> Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages live-build depends on:
> ii debootstrap 1.0.64~bpo70+1
>
> Versions of packages live-bui
You're right, LB_INITRAMFS looks to be a much better variable to base
this on. Updated patch attached.
commit 4b7113a839e263ce679f117057f56c6eee75cd9a
Author: jnqnfe
Date: Tue Dec 9 04:42:26 2014 +
Fix broken ability to build casper based images due to generating live-boot
spe
and in lines 1062 to 1083 issues a
warning if syslinux is selected with a fat/ntfs/ext[2/3/4]/btrfs fs
format, and an error if the hdd image type is selected along with grub
(but not grub2) as the bootloader. Nothing more.
commit 9351f9f4536e310f00f9792d9be05db5035b706f
Author: jnqnfe
Date: Tue
red on the disk somewhere in .ico format (and my patch expanded
with the appropriate additional entries).
[1]
http://msdn.microsoft.com/en-us/library/windows/desktop/cc144200%28v=vs.85%29.aspx#icon
commit 4f8b0c1f7abd265af1819e1dc564a0b83978fcb5
Author: jnqnfe
Date: Wed Dec 10 05:24:53
Apologies, I forgot to remove the logos archive that I initially
attached to the report but then decided to send to the mailing list
separately. Please ignore it here in this bug report. I thought I better
send this to explain why it's there.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@
Control: reopen -1
Control: notfixed -1 4.0.4-1
Still broken due to typo, the patch applied in 4.0.4-1 uses
'includs.chroot' instead of 'includes.chroot' (missing 'e').
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listma
e
restructuring work.
commit cfb644e22512dc693e682d52532d57e4d3064edc
Author: jnqnfe
Date: Sat Nov 29 02:22:25 2014 +
Temporarily disable early exit in 'chroot_archives remove'.
diff --git a/scripts/build/chroot_archives b/scripts/build/chroot_archives
index 4c51cd7..8c2e192 1
-live/2015/01/msg00192.html
commit 0d38493e85f616b32a28e8971146991f64b317a0
Author: jnqnfe
Date: Thu Jan 22 12:39:22 2015 +
Ensure chroot/root/packages.chroot package list is removed
diff --git a/scripts/build/chroot_archives b/scripts/build/chroot_archives
index 8c2e192..82810c2 100755
Package: live-build
Version: 4.0.4-1
Creating this bug to have a written record and bug number for this
problem area.
The chroot_archives script, which is used in toggling the chroot between
'chroot' (build) and 'binary' (live) apt archive configuration, does an
imperfect job in toggling between
Package: live-images
The live-build configs offered in the live-images debian-next git branch
(for use with live-build 5.x) need to be updated based on changes to
live-build that are being implemented under bug #775322 (Assuming that
work is to get merged).
I will attach the necessary patches her
of
v3.x, and presumably should have been changed in v4.x.
Patch attached based on v5.x.
commit 4707b8e32a721e1769ddba8937c0da872d6c8f69
Author: jnqnfe
Date: Sun Jan 25 03:51:45 2015 +
Update distribution defaults
diff --git a/functions/defaults.sh b/functions/defaults.sh
index ffec3b5
I'm not familiar enough with what packages should or should not be
listed in these, so I didn't touch them and didn't even notice therefore
the wheezy specific if blocks. Perhaps I should have worded it 'patch
attached to update the bootloader config files'. :)
On Sun, 25 Jan 2015 09:17:12 +0100 D
Control: close -1
thanks
Closing since superseded by #775322
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: debian-cd
When an official Debian disc image is loaded on a system with EFI, the
bootloader is displayed at at size of 800x600, larger than that used on
BIOS systems (640x480). The disc images include a bootloader splash
image (found in the syslinux directory) which has dimensions of 640x
ry to sort this out sometime soon if someone else
doesn't in the meantime.
commit 9befabb39f820f7ba9b3fba65d25df76b32b9b97
Author: jnqnfe
Date: Thu Jan 29 02:52:44 2015 +
Add missing use of chroot_dpkg in binary stage (Closes: #776532)
diff --git a/scripts/build/binary b/scripts/bui
Package: live-build
Version: 5.0~a2-1
The binary stage script is missing chroot_dpkg in the list of chroot
'prep' scripts that are executed against the chroot filesystem.
I'm not certain if it was deliberately left out or not (the remove entry
is indeed there), and use of syslinux as the selected
Control: retitle -1 Use of depreciated graphics param with grub2
Control: close -1
Control: archive -1
I made a mistake, see related bug #775317 for the explanation.
Looking at the debian-cd code I see that there are only two uses of
VGA=, both of which are used with loadlin, so this problem does
Control: retitle -1 Use of depreciated graphics param with grub2
To reclarify the problem, now that I have investigated and solved it in
live-build: I noticed a message from grub2 about VGA=788 being a
depreciated graphics param, and being relatively new to linux I
mistakenly thought this was a ke
24x768 being the default. Unless
you're happy with the blurry image, either the default needs switching
down to 800x600 in this patch, or the image needs replacing with a
higher res copy.
commit 364b428be604a25064f90bb9146c62e962b2c8c5
Author: jnqnfe
Date: Fri Jan 30 04:04:41 2015 +
I
Updated patch, forgot to update the changelog.
commit 19b474c6ba60314bc8a0dcfb7dfdcb328ad14310
Author: jnqnfe
Date: Fri Jan 30 19:19:47 2015 +
Implement use of grub gfxpayload setting instead of 'vga=' param
diff --git a/build/config/amd64.cfg b/build/config/amd64.cfg
ind
I can only assume that no-one has tried to actually execute the new code
here yet apart from myself, since no-one has pointed out the file
permissions error I have made...
I've been doing a weird thing of developing on Windows, then copying the
files to a Debian VM for testing, and although I've b
Small mistake: Somehow in mulling over the possibility of also adding
gpg & gpg2 to the list of possible tools to use (which I ditched), I
mistakenly came under the impression that the --no-default-keyring
parameter was available on gpgv/gpgv2, but it's not, so it needs
removing from the patch I su
Package: live-build
Version: 4.0.4-1
There are one or more issues with the code in the
installer_debian-installer script where it obtains vmlinuz and initrd
files for sparc netboot builds.
Issue #1 - Wrong path
--
On line 290, it uses the path ${URL}/mini.iso, where ${
Package: live-build
Version: 4.0.4-1
There are one or more issues with the code in the
installer_debian-installer script where it obtains vmlinuz and initrd
files for sparc netboot builds.
Issue #1 - Wrong path
--
On line 290, it uses the path ${URL}/mini.iso, where ${
Issue #4 - Location of files within mini.iso
---
In addition to issue #1, upon examining the contents of a mini.iso file,
I can see that lines 295 and 296 are looking in the wrong location for
files from within it.
They are looking for boot/vmlin
Package: live-build
Version: 4.0.4-1
Lines 82-86 of the binary_disk script download a simply archive trace file from
the parent bootstrap mirror. The source_disk script on the other hand has more
complex logic that takes into account derivatives (lines 82-98).
Surely they should both be using t
Package: live-build
Version: 4.0.4-1
The installer_debian-installer script, on line 67, tries to ensure that the
wget package is installed and available by using the custom dependency manager
facilities built into live-build. However, this check is insufficient.
Live-build's custom dependency c
Control: tags -1 patch
Patch attached
commit 4547cbfc84ef291d108f11445dc59e3e7178a243
Author: jnqnfe
Date: Wed Dec 31 19:30:09 2014 +
Fix wget dependency (Closes: #774326)
diff --git a/debian/control b/debian/control
index b921960..0645c46 100644
--- a/debian/control
+++ b/debian
Control: tags -1 patch
Might as well directly attach the patch for issues #1 and #4 here...
commit 642dd065377c95b254b11779a742f2088a143335
Author: jnqnfe
Date: Tue Dec 30 04:09:19 2014 +
Fix sparc-netboot mini.iso (installer file) download location and content
paths (#774196 Issues
Package: live-build
Version: 4.0.4-1
The binary_package-lists script on lines 56-82 has a flexible dependency
check for the apt-ftparchive and grep-aptavail utilities, applying a
different check whether configured to work within chroot or not.
However, all work in the script is actually done from
Package: live-build
Version: 4.0.4-1
Certain binary utilities used in live-build could do with a check for
existence of their binaries, being done at the Check_defaults() level.
This applies particularly to cases where the user configuration can
change which binary is used, e.g. for compression, o
Package: live-build
Version: 4.0.4-1
One or more Check_package dependency checks are missing for binaries
executed under chroot.
This includes, but is not limited to the use of the xargs in
chroot_install-packages.
This bug report can be updated once a thorough review has been done to
come up wi
Package: live-build
Version: 4.0.4-1
In addition to bug #774326 (wget dependency) and the existing
dependencies of debootstrap and cpio, I believe that several other
packages should also be listed as live-build dependencies.
This includes the following, for which binaries are used (at host level)
Package: live-build
Version: 4.0.4-1
I am not currently familiar with what the debian/live-build.bug-script
file is used for exactly, but it needs updating. It currently still
contains a load of 'cruft' that was removed from the control file in
v4.0_a31-1. Also, if my bug #774339 patch is accepted
this could later be improved to gpgv | gpgv2
(which my bug #718225 solution, not yet provided, almost complete,
already supports).
commit 78e5c2d4daceeb6588e267327fb99ce43b2326e0
Author: jnqnfe
Date: Thu Jan 1 02:52:37 2015 +
Expand LB package dependencies to cover more binaries used (Clos
will need to be added to this file.
commit 125d113a64da0bfeffed154845c259115973f3f9
Author: jnqnfe
Date: Thu Jan 1 03:22:32 2015 +
Update dependencies in live-build.bug-script file (Closes: #774340)
diff --git a/debian/live-build.bug-script b/debian/live-build.bug-script
index 8a68d30
Sorry, fixed patch attached. I'd left the arch restriction of the
sparc-utils package in there, meaning to check how to specify that to
dpkg if necessary, but got distracted and forgot.
commit a7a02c10264087b5c5849cf93f8d95deca649a9d
Author: jnqnfe
Date: Thu Jan 1 03:22:32 2015
Package: live-build
Version: 4.0.4-1
Severity: important
The installer_debian-installer and chroot_firmware scripts both download
a Contents-[arch].gz file in order to get a list of firmware packages to
then download and include. The URL compiled for download of the contents
file is {MIRROR}/dists
Package: live-build
Version: 4.0.4-1
Running LB in Ubuntu mode, it fails during the
installer_debian-installer script, stating that package 'busybox' has no
installation candidate, but pointing out that package 'busybox-static'
replaces it.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@l
Dist was set to 'precise' for this btw!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Having tried running LB in Ubuntu mode now, it did fail but due to other
issues (reported separately), and did make it past the chroot_firmware
script, so clearly its failing to download the file and just continuing
without (additional?) firmware.
--
To UNSUBSCRIBE, email to debian-bugs-dist-req
Package: live-build
Version: 4.0.4-1
Running LB in Ubuntu mode, with dist set to utopic, it crashed in
'bootstrap_archives binary' with the following:
Preparing to replace dkpg 1.16.1.2ubuntu7 (using
.../dpkg_1.17.13ubuntu1_amd64.deb) ...
Unpacking replacement dpkg ...
dpkg: error: configuration
Package: live-build
Version: 5.0~a1-1
Severity: wishlist
A possible improvement for the future, submitting now ahead of time.
(Can be ignored for the time being).
Taking a que from the current installer_debian-installer cache, which
uses URLs (with forward slashes replaced with underscores) in th
Control: severity -1 critical
Raising the severity of this, considering I am almost completely done
with building the patch for it, I'd really like to see this get into
Jessie, and considering that it allows complete compromise of a live
image and any installations from it, unless the user actuall
1 - 100 of 329 matches
Mail list logo
