Debian installer build overview
---
Failed or old builds:
* FAILED BUILD: amd64 Mar 12 21:25 debian-cd@pettersson 1sidamd64
http://cdbuilder.debian.org/cdimage-log/1sidamd64
* FAILED BUILD: amd64 Mar 12 21:25 debian-cd@pettersson 2sidamd64
Hi Adam,
On Mon, 2012-03-12 at 19:47 +, Adam D. Barratt wrote:
> Hi,
>
> On Sun, 2012-03-11 at 14:55 -0300, Otavio Salvador wrote:
> > I'd like to propose following timeline for alpha1 of installer:
>
> Thanks for this.
>
> > * until 03/14 get all translation-only changed udebs uploaded
>
There are disparities between your recently accepted upload and the
override file for the following file(s):
cdebconf-gtk_0.159_amd64.deb: package says priority is extra, override says
optional.
Please note that a list of new sections were recently added to the
archive: cli-mono, database, debu
Accepted:
cdebconf-gtk-udeb_0.159_amd64.udeb
to main/c/cdebconf/cdebconf-gtk-udeb_0.159_amd64.udeb
cdebconf-gtk_0.159_amd64.deb
to main/c/cdebconf/cdebconf-gtk_0.159_amd64.deb
cdebconf-newt-udeb_0.159_amd64.udeb
to main/c/cdebconf/cdebconf-newt-udeb_0.159_amd64.udeb
cdebconf-priority_0.159
cdebconf_0.159_amd64.changes uploaded successfully to localhost
along with the files:
cdebconf_0.159.dsc
cdebconf_0.159.tar.gz
cdebconf-priority_0.159_all.udeb
cdebconf_0.159_amd64.deb
cdebconf-gtk_0.159_amd64.deb
libdebconfclient0_0.159_amd64.deb
libdebconfclient0-dev_0.159_amd64.deb
Your message dated Mon, 12 Mar 2012 19:47:19 +
with message-id
and subject line Bug#537535: fixed in cdebconf 0.159
has caused the Debian Bug report #537535,
regarding other missing utilities for debconf replacement
to be marked as done.
This means that you claim that the problem has been dea
Hi,
On Sun, 2012-03-11 at 14:55 -0300, Otavio Salvador wrote:
> I'd like to propose following timeline for alpha1 of installer:
Thanks for this.
> * until 03/14 get all translation-only changed udebs uploaded
> * until 03/14 get pending fixes commited uploaded
> * on 03/17 try to get the p
On Mon, Mar 12, 2012 at 12:04:52AM +, Miguel Figueiredo wrote:
> Hi all,
>
> Add the mount option 'discard' for ext4 filesystems so, during
> partitioning, TRIM can be activated for SSDs in the installed
> system.
I enabled that on ext4 on my SSD, and had two lockups in 24 hours.
No lockups s
Colin Watson wrote:
> How about, if grub-mount is used, we use grub-probe to find out which
> GRUB filesystem driver is in use, and stash that somewhere so that
> individual tests can get at it? That ought to be just as reliable as
> the existing OS filesystem type checks.
Yes please. I've CCed t
Samuel Thibault wrote:
> Mmm, why not looking for io.sys at the root? In all the versions of DOS
> that I know there has to be one for the partition to be bootable.
According to http://en.wikipedia.org/wiki/IO.SYS , some of the DOS
clones did not use io.sys, which may be why I don't remember it w
Package: os-prober
Version: 1.49
Severity: normal
A while ago, os-prober was made to try to mount filesystems with
grub-mount. This means that $type cannot be used to test
the filesystem type. Various commits have been made since
to let through $type=fuse|fuseblk in various tests.
But, I've notic
On Mon, Mar 12, 2012 at 11:14:07AM -0400, Joey Hess wrote:
> These checks don't try to avoid false positives like a /dos or /windows,
> because the code earlier checks that the mounted filesystem is one of ntfs,
> vfat, or msdos. To which list was semi-recently added fuse, and I suspect
> that migh
Joey Hess, le Mon 12 Mar 2012 11:14:07 -0400, a écrit :
> The particular OS string we see here comes from:
>
> # MS-DOS
> if [ -z "$found" ] && item_in_dir -q dos "$2" &&
> [ -d "$2"/"$(item_in_dir dos "$2")" ]; then
> long="MS-DOS 5.x/6.x/Win3.1"
> short=MS-DOS
>
> f
Michael Tokarev wrote:
> So a more naive approach at determining the filesystem type is to
> check first 512 bytes, and if MS-DOS signature is found there,
> report that it is MS-DOS. This is, apparently, what os-prober is
> currently doing.
os-prober does not look at fragile magic numbers in fil
Floris Bos / Maxnet wrote:
> Hmm, and to make things more complicated.
> The RELEASE-NOTES that come with the e2fsprogs source say that the
> default is what you put in mke2fs.conf
That's for an older version.
int discard = 1;/* attempt to discard device before fs creation */
Miguel Figueiredo wrote:
> On 12-03-2012 04:55, Joey Hess wrote:
>
> >I had the impression that there was going to be some sort of automatic
> >detection in the kernel of appropriate devices and that trim would be
> >automatically enabled for them. Is it not going to play out that way?
>
> Just a
On 12.03.2012 08:57, Harald Dunkel wrote:
> Package: os-prober
> Version: 1.49
>
> os-prober finds some MSDOS partition on my laptop:
[os-prober says /dev/sda2 is MSDOS,
while parted and blkid identifies it as ext4]
I understand that, due to the fact that other utils correctly identifies
this f
Hi,
On 12-03-2012 04:55, Joey Hess wrote:
I had the impression that there was going to be some sort of automatic
detection in the kernel of appropriate devices and that trim would be
automatically enabled for them. Is it not going to play out that way?
Just adds the mount option to partman.
On 03/12/2012 07:58 AM, Floris Bos / Maxnet wrote:
On 03/12/2012 07:51 AM, Joey Hess wrote:
Floris Bos / Maxnet wrote:
In addition to that, it would also be nice if the "-E discard"
option is passed to mkfs.ext4, so that it TRIMs the entire disk
partition prior to creating the file system struc
19 matches
Mail list logo
