On 19/04/12 02:16 PM, Daniel Ellison wrote:
Hopefully this will be it. I'll come back in a while to update all
concerned with the results.
A big thanks to Daniel Baumann and Ben Armstrong for persevering with
what must have been a very annoying thread. Also, thanks to Tim Gibbon
who suggested
On 19/04/12 11:36 AM, Daniel Ellison wrote:
On 19/04/12 10:09 AM, Daniel Baumann wrote:
included in live-config 3.0~a34-1.
3.0~a35-1 migrated on 2012-04-13, so wheezy is working out of the box
since then again.
Thanks, Daniel! So when building a wheezy ISO on a wheezy system, if I
pin like th
On 19/04/12 12:34 PM, Ben Armstrong wrote:
What are you guys talking about? Daniel said: "3.0~a35-1 migrated on
2012-04-13, so wheezy is working out of the box since then again" so I
don't understand why you think pinning is required ...
Yes, I've since realized that and have removed the sid pi
What are you guys talking about? Daniel said: "3.0~a35-1 migrated on
2012-04-13, so wheezy is working out of the box since then again" so I
don't understand why you think pinning is required ...
--
To UNSUBSCRIBE, email to debian-live-requ...@lists.debian.org
with a subject of "unsubscribe". Tro
On 19/04/12 12:20 PM, chals wrote:
If you want to pin packages from sid in wheezy I would recommend you
using a wildcard as explained in live-manual
Package: live-*
Instead of pinning packages by name. Because if you do not turn off apt
recommends it will also install live-tools from sid inste
On Thu, Apr 19, 2012 at 5:36 PM, Daniel Ellison wrote:
>
> Thanks, Daniel! So when building a wheezy ISO on a wheezy system, if I pin
> like this in chroot_apt/preferences:
>
>
> Package: live-boot live-boot-initramfs-tools live-config
> live-config-sysvinit
> Pin: release n=sid
> Pin-Priority: 1
Hi,
Is it possible to disable creating .disk directory in binary image or
replace it by predefined value? I found string "Debian GNU/Linux 7
"Wheezy" - Official Snapshot i386 LIVE Binary..." in ./disk/info and it is
wrong to leave such information because at least it isn't official snapshot.
On 19/04/12 10:09 AM, Daniel Baumann wrote:
included in live-config 3.0~a34-1.
3.0~a35-1 migrated on 2012-04-13, so wheezy is working out of the box
since then again.
Thanks, Daniel! So when building a wheezy ISO on a wheezy system, if I
pin like this in chroot_apt/preferences:
Package: liv
On 04/19/2012 12:37 PM, Daniel Ellison wrote:
Was this ever resolved?
this is the fix:
http://live.debian.net/gitweb?p=live-config.git;a=commitdiff;h=dc84ecc6ac52ab1265dc8a07c97d6f1e46e0750e;hp=0f3af5e5b178b134271fa63a1944977108e7f5df
included in live-config 3.0~a34-1.
3.0~a35-1 migrated on
sid build
If I don't include the 5 packages I mentioned, keeping my same wheezy
build platform to build a sid image, then it works. startpar does not
error and we are at the bash prompt
[i.e I change my script to add a
--distribution "sid" \
]
=
I've just
On 04/19/2012 08:10 AM, Tim Gibbon wrote:
> I think that was me using a sledgehammer to crack a nut. I simply
> built the live-boot, live-build and live-config packages from the git
> repositories, using the instructions from the manual.
Did it fail if you use live-* packages currently in sid?
I
Hello,
> That being said, as I composed this reply, I see Tim Gibbon has also
> replied that using particular versions of live-* packages made it work
> for him ... among those packages is the systemd backend for live-config.
> I'm puzzled by that suggestion because you state above that the proble
On 19/04/12 07:37 AM, Daniel Ellison wrote:
> Was this ever resolved? I've been staying away because it was too
> frustrating not being able to create a Wheezy ISO with default
> configuration.
>
> As it was determined that the problem occurred for me on three different
> computers using an ISO cre
Hello Daniel,
I had the same problem as you. I got it to work by copying the
following packages into config/packages.chroot:
live-boot_3.0~a27-1_all.deb
live-build_3.0~a46-1_all.deb
live-config-systemd_3.0~a37-1_all.deb
live-boot-initramfs-tools_3.0~a27-1_all.deb
live-config_3.0~a37
On 15/02/12 02:29 PM, Daniel Ellison wrote:
On 10/02/12 07:25 AM, Daniel Baumann wrote:
On 02/10/2012 12:34 PM, Daniel Ellison wrote:
So that rules out my specific laptop as being at fault.
ack.
Which means it is an actual bug? If so, do I need to file a bug report?
Or is that already taken
Tomorrow, the containers serving live.debian.net (and potentially
live-manual.debian.net[0]) will be offline for about an hour between
10:00 and 12:00 (UTC+2).
The container will be updated to squeeze, and move to another host
better suited for the debian-live stuff, hence the IP will change f
16 matches
Mail list logo
