Bug#778531: Patch

2015-08-04 Thread Cyril Brulebois
Hi,

Askar Safin  (2015-08-05):
> Patch for source package libdebian-installer 0.99+deb8u1.

Thanks for the patch, but you haven't really told us about your usecase
with c++ in a d-i context.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#762054: [Pkg-fonts-devel] Bug#762054: d-i.debian.org: investigate ttf-* vs. fonts-* for udebs?

2015-08-04 Thread Fabian Greffrath
Hi Christian,

sorry for the late reply!

Am Sonntag, den 26.07.2015, 09:19 +0200 schrieb Christian PERRIER:
> Guys, do you think we want to manage a transition for, say
> ttf-freefont-udeb->fonts-freefont-udeb (with transitional package,
> etc. as we did for the ttf->fonts transitions)or will we just
> replace the package (given that only the installer is using the udeb)
> ?

I think we should simply replace the package with the one following the
new naming scheme and just ping the d-i maintainers about it.

Cheers,

Fabian


signature.asc
Description: This is a digitally signed message part


Bug#794265: flash-kernel subsequent actions result in segfault

2015-08-04 Thread Martin Michlmayr
Are you saying the segfaults started after flash-kernel was run?
Without rebooting to the new kernel?

-- 
Martin Michlmayr
http://www.cyrius.com/


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150804170401.ga20...@jirafa.cyrius.com



Bug#778531: Patch

2015-08-04 Thread Askar Safin
Patch for source package libdebian-installer 0.99+deb8u1.

==
Askar Safin
http://vk.com/safinaskar

diff -Naur libdebian-installer-0.99+deb8u1/include/debian-installer/exec.h 
new/include/debian-installer/exec.h
--- libdebian-installer-0.99+deb8u1/include/debian-installer/exec.h 
2014-11-05 01:19:08.0 +
+++ new/include/debian-installer/exec.h 2015-08-04 20:54:55.335590329 +
@@ -20,6 +20,11 @@
 #ifndef DEBIAN_INSTALLER__EXEC_H
 #define DEBIAN_INSTALLER__EXEC_H
 
+#ifdef __cplusplus
+extern "C"
+{
+#endif
+
 #include 
 
 #include 
@@ -200,4 +205,9 @@
 }
 
 /** @} */
+
+#ifdef __cplusplus
+}
+#endif
+
 #endif
diff -Naur libdebian-installer-0.99+deb8u1/include/debian-installer/hash.h 
new/include/debian-installer/hash.h
--- libdebian-installer-0.99+deb8u1/include/debian-installer/hash.h 
2014-11-05 01:19:08.0 +
+++ new/include/debian-installer/hash.h 2015-08-04 20:54:55.339590329 +
@@ -21,6 +21,11 @@
 #ifndef DEBIAN_INSTALLER__HASH_H
 #define DEBIAN_INSTALLER__HASH_H
 
+#ifdef __cplusplus
+extern "C"
+{
+#endif
+
 #include 
 
 /** 
@@ -139,4 +144,9 @@
 di_ksize_t di_hash_table_size (di_hash_table *hash_table);
 
 /** @} */
+
+#ifdef __cplusplus
+}
+#endif
+
 #endif
diff -Naur libdebian-installer-0.99+deb8u1/include/debian-installer/list.h 
new/include/debian-installer/list.h
--- libdebian-installer-0.99+deb8u1/include/debian-installer/list.h 
2014-11-05 01:19:08.0 +
+++ new/include/debian-installer/list.h 2015-08-04 20:54:55.339590329 +
@@ -20,6 +20,11 @@
 #ifndef DEBIAN_INSTALLER__LIST_H
 #define DEBIAN_INSTALLER__LIST_H
 
+#ifdef __cplusplus
+extern "C"
+{
+#endif
+
 #include 
 
 typedef struct di_list di_list;
@@ -116,4 +121,9 @@
 void di_list_prepend_chunk (di_list *list, void *data, di_mem_chunk 
*mem_chunk) __attribute__ ((nonnull(1,3)));
 
 /** @} */
+
+#ifdef __cplusplus
+}
+#endif
+
 #endif
diff -Naur libdebian-installer-0.99+deb8u1/include/debian-installer/log.h 
new/include/debian-installer/log.h
--- libdebian-installer-0.99+deb8u1/include/debian-installer/log.h  
2014-11-05 01:19:08.0 +
+++ new/include/debian-installer/log.h  2015-08-04 20:54:55.343590329 +
@@ -20,6 +20,11 @@
 #ifndef DEBIAN_INSTALLER__LOG_H
 #define DEBIAN_INSTALLER__LOG_H
 
+#ifdef __cplusplus
+extern "C"
+{
+#endif
+
 #include 
 
 /**
@@ -104,4 +109,9 @@
   di_log_handler_syslog;
 
 /** @} */
+
+#ifdef __cplusplus
+}
+#endif
+
 #endif
diff -Naur libdebian-installer-0.99+deb8u1/include/debian-installer/mem.h 
new/include/debian-installer/mem.h
--- libdebian-installer-0.99+deb8u1/include/debian-installer/mem.h  
2014-11-05 01:19:08.0 +
+++ new/include/debian-installer/mem.h  2015-08-04 20:54:55.351590330 +
@@ -21,6 +21,11 @@
 #ifndef DEBIAN_INSTALLER__MEM_H
 #define DEBIAN_INSTALLER__MEM_H
 
+#ifdef __cplusplus
+extern "C"
+{
+#endif
+
 #include 
 
 #include 
@@ -87,4 +92,9 @@
   ((struct_type *) di_realloc ((mem), sizeof (struct_type) * (n_structs)))
 
 /** @} */
+
+#ifdef __cplusplus
+}
+#endif
+
 #endif
diff -Naur libdebian-installer-0.99+deb8u1/include/debian-installer/mem_chunk.h 
new/include/debian-installer/mem_chunk.h
--- libdebian-installer-0.99+deb8u1/include/debian-installer/mem_chunk.h
2014-11-05 01:19:08.0 +
+++ new/include/debian-installer/mem_chunk.h2015-08-04 20:54:55.355590330 
+
@@ -21,6 +21,11 @@
 #ifndef DEBIAN_INSTALLER__MEM_CHUNK_H
 #define DEBIAN_INSTALLER__MEM_CHUNK_H
 
+#ifdef __cplusplus
+extern "C"
+{
+#endif
+
 #include 
 
 typedef struct di_mem_chunk di_mem_chunk;
@@ -37,4 +42,9 @@
 size_t di_mem_chunk_size (di_mem_chunk *mem_chunk);
 
 /** @} */
+
+#ifdef __cplusplus
+}
+#endif
+
 #endif
diff -Naur libdebian-installer-0.99+deb8u1/include/debian-installer/package.h 
new/include/debian-installer/package.h
--- libdebian-installer-0.99+deb8u1/include/debian-installer/package.h  
2014-11-05 01:19:08.0 +
+++ new/include/debian-installer/package.h  2015-08-04 20:54:55.359590330 
+
@@ -20,23 +20,16 @@
 #ifndef DEBIAN_INSTALLER__PACKAGE_H
 #define DEBIAN_INSTALLER__PACKAGE_H
 
+#ifdef __cplusplus
+extern "C"
+{
+#endif
+
 #include 
 #include 
 #include 
 #include 
 
-typedef struct di_package di_package;
-typedef struct di_package_dependency di_package_dependency;
-typedef struct di_package_version di_package_version;
-
-typedef enum di_package_dependency_type di_package_dependency_type;
-typedef enum di_package_priority di_package_priority;
-typedef enum di_package_status di_package_status;
-typedef enum di_package_status_want di_package_status_want;
-typedef enum di_package_type di_package_type;
-
-#include 
-
 /**
  * @addtogroup di_package
  * @{
@@ -54,6 +47,8 @@
   di_package_priority_required,
 };
 
+typedef enum di_package_priority di_package_priority;
+
 /**
  * Status field, third part
  */
@@ -67,6 +62,8 @@
   di_package_status_config_files,
 };
 
+typedef enum di_package_status di_package_status;
+
 /**
  * Status field, first part
  */
@@ -79,6 +76,8 @

Re: proofreading the installation-guide

2015-08-04 Thread Justin B Rye
Holger Wansing wrote:
> Justin B Rye  wrote:
>> Holger Wansing wrote:
>>> No, not _all_ instances of &releasename; have to be capitalised in German,
>>> for example in URLs they will have to stay lowercase.
>>> But I can use &releasename; or &releasename-cap; in my translation,
>>> where &releasename; is used in English.
>> 
>> So all cases of &releasename-cap; in the English text are mistakes.
>> Really if it's only for use in German we should have called it
>> &Veroeffentlichungsname;!
> 
> No, it's not just for German!
> It gives _all_ translators the possibility, to spell the releasename as
> they want in their language.
> I just used German and how it's used in German, to explain the principle.
> 
> Not much translators use that possibility though.

Such as?  There *aren't* any other languages that have mandatory
initial capitalisation on nouns (and even German allows exceptions for
"brandnames" like "das iPhone" or "xkcd").  There's not much else that
you could automate, so I'd be interested to know who else finds it
useful.

Fortunately none of this should matter for a proofreading sweep of the
English.
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150804194756.ga12...@xibalba.demon.co.uk



Re: proofreading the installation-guide

2015-08-04 Thread Samuel Thibault
Justin B Rye, le Tue 28 Jul 2015 21:06:03 +0100, a écrit :
> Holger Wansing wrote:
> > Justin B Rye  wrote:
> >> An interesting idea, but one that seems unlikely to work, especially
> >> given the way it's used in the text.  For instance, there's a page
> >> "welcome/what-is-debian-linux.xml", which is full of sentences like
> >> "&debian; was the first Linux distribution to include a package
> >> management system".
> > 
> > It was mostly me changing Debian into &debian; that days in 2010.
> > If I remember correctly, it was initiated by a post of Frans Pop,
> > who proposed that change. And the rationale was in fact, to get a
> > manual, that can easily be turned from a "Debian installer manual" into
> > a "Ubuntu installer manual", for example.
> 
> Whoever it is that's reworking the manual for the derivative is still
> going to need to go through the whole text changing the content.

Yes, but most probably only once. The really-debian-specific text hasn't
really changed much over years.

> The &debian; entity seems liable to cost us more effort than it saves
> them (a single extra search-and-replace operation).

Yes, but once in place, merges become trivial. That's the whole point of
it.

> >>  The "&architecture;",
> >> "&arch-title;" and "&arch-kernel;" entities are slightly oddly named
> 
> Since I keep losing track and having to check again, I'll leave a note
> for myself here:
> "&architecture;" = "32-bit PC", "32-bit soft-float ARM", etc.
> "&arch-title;" = "i386", "armel", etc.
> "&arch-kernel; = "Linux", "KFreeBSD", etc.

This, and also:

Hendrik Boom wrote:
> So I suppose it would be reasonable to put a comment in the document
> source explaining this, perhaps where these macros are defined

can probably find its way to common.ent indeed, patches (or simply,
commits) welcome :)

Samuel


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150804192735.GG3954@type



Re: proofreading the installation-guide

2015-08-04 Thread Holger Wansing
Hi,

Justin B Rye  wrote:
> Holger Wansing wrote:
> > No, not _all_ instances of &releasename; have to be capitalised in German,
> > for example in URLs they will have to stay lowercase.
> > But I can use &releasename; or &releasename-cap; in my translation,
> > where &releasename; is used in English.
> 
> So all cases of &releasename-cap; in the English text are mistakes.
> Really if it's only for use in German we should have called it
> &Veroeffentlichungsname;!

No, it's not just for German!
It gives _all_ translators the possibility, to spell the releasename as
they want in their language.
I just used German and how it's used in German, to explain the principle.

Not much translators use that possibility though.


Holger

-- 

Created with Sylpheed 3.5.0 under
D E B I A N   L I N U X   8 . 0   " J E S S I E " .

Registered Linux User #311290 - https://linuxcounter.net/



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150804205051.0e86519a24091e175869c...@wansing-online.de



Re: proofreading the installation-guide

2015-08-04 Thread Justin B Rye
Holger Wansing wrote:
> No, not _all_ instances of &releasename; have to be capitalised in German,
> for example in URLs they will have to stay lowercase.
> But I can use &releasename; or &releasename-cap; in my translation,
> where &releasename; is used in English.

So all cases of &releasename-cap; in the English text are mistakes.
Really if it's only for use in German we should have called it
&Veroeffentlichungsname;!

But given that we're treating the name "jessie" as a special string
that's entitled to ignore the usual English capitalisation rules (so
that for instance it's still lowercase when it's sentence-initial),
it's not clear why this verbatim status wouldn't also licence it to
disregard the standard capitalisation rules of German.  Unless rules
stated in German are just intrinsically stricter!

Mind you, there's no obvious reason (apart from the stiffness of
developers' little fingers) for this habit of treating the lowercase
form of the release name as canonical in the first place.  "Jessie" is
after all named after something that had a capital J, and even the
announcement of the codename for Debian 8 spelled it that way:
https://lists.debian.org/debian-devel-announce/2012/07/msg4.html

Things would be a lot simpler if only we could standardise on the
*capitalised* form.  But then I suppose people would complain that
that isn't what's in /etc/os-release...
-- 
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20150804181120.ga10...@xibalba.demon.co.uk



Bug#794265: flash-kernel subsequent actions result in segfault

2015-08-04 Thread Michele Cane
Yes is segfaults just after flash-kernel is run without any reboot.
Rebooting solves the segfault issue.

On Tue, Aug 4, 2015 at 7:04 PM Martin Michlmayr  wrote:

> Are you saying the segfaults started after flash-kernel was run?
> Without rebooting to the new kernel?
>
> --
> Martin Michlmayr
> http://www.cyrius.com/
>
-- 
Michele Cane, Ph.D.


Bug#794526: busybox: testsuite is run iff DEB_BUILD_OPTIONS contains nocheck

2015-08-04 Thread Cyril Brulebois
Hi,

Helmut Grohne  (2015-08-04):
> Source: busybox
> Version: 1.22.0-15
> Severity: important
> Tags: patch
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> During a partial archive cross rebuild, I noticed that busybox FTCBFS,
> because it runs its test suite despite being told
> DEB_BUILD_OPTIONS=nocheck. This is surprising, because it actually tries
> to take care of that flag. Even more surprising (and the reason for
> flagging this bug as important) is that the test suite is not run during
> native buildd builds.
> 
> It turned out that the detection logic has an inversion flaw, so the
> test suite is run and only run when DEB_BUILD_OPTIONS contains nocheck.
> The attached patch might or might not fix the FTCBFS, but it fixes the
> logic inversion.

The non attached patch certainly might not fix anything. ;)

Mraw,
KiBi.


signature.asc
Description: Digital signature


Bug#794526: busybox: testsuite is run iff DEB_BUILD_OPTIONS contains nocheck

2015-08-04 Thread Helmut Grohne
On Tue, Aug 04, 2015 at 03:35:38PM +0200, Cyril Brulebois wrote:
> The non attached patch certainly might not fix anything. ;)

Sorry for the omission.

Helmut
diff -Nru busybox-1.22.0/debian/changelog busybox-1.22.0/debian/changelog
--- busybox-1.22.0/debian/changelog 2015-03-04 17:46:39.0 +0100
+++ busybox-1.22.0/debian/changelog 2015-08-04 15:45:44.0 +0200
@@ -1,3 +1,11 @@
+busybox (1:1.22.0-15.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix logic inversion in DEB_BUILD_OPTIONS=nocheck handling.
+(Closes: #794526)
+
+ -- Helmut Grohne   Tue, 04 Aug 2015 15:45:02 +0200
+
 busybox (1:1.22.0-15) unstable; urgency=medium
 
   [ Michael Gilbert ]
diff -Nru busybox-1.22.0/debian/rules busybox-1.22.0/debian/rules
--- busybox-1.22.0/debian/rules 2015-03-04 16:12:02.0 +0100
+++ busybox-1.22.0/debian/rules 2015-08-04 15:45:51.0 +0200
@@ -7,7 +7,7 @@
 PKGVERSION := $(shell dpkg-parsechangelog | sed -ne 's,^Version: 
*\(.*\)$$,\1,p')
 VENDOR := $(shell dpkg-vendor --query vendor)
 
-ifneq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
+ifeq (,$(filter nocheck,$(DEB_BUILD_OPTIONS)))
 RUN_TESTSUITE = y
 endif
 TESTSUITE_ENV = SKIP_KNOWN_BUGS=y VERBOSE=y


Bug#769406: Serial console not set up after serial install

2015-08-04 Thread Bernhard Schmidt
On Wed, Dec 03, 2014 at 11:29:00PM +0100, Samuel Thibault wrote:

Hi,

> Geert Stappers, le Wed 03 Dec 2014 22:30:39 +0100, a écrit :
> > Jan  1 21:50:07 kernel: [0.00] Command line: 
> > BOOT_IMAGE=http://alpaca.gpm.stappers.nl/d-i/jessie/amd64/linux vga=normal 
> > console=ttyS0,19200,n8 -- 
> > initrd=http://alpaca.gpm.stappers.nl/d-i/jessie/amd64/initrd.gz 
> 
> Options to be propagated to the installed kernel have to be put after
> --.  With the recent kernel change which lead to #764675, it's actually
> now ---, so it'd be something like
> 
> > vga=normal initrd=http://alpaca.gpm.stappers.nl/d-i/jessie/amd64/initrd.gz 
> > --- console=ttyS0,19200,n8 
> 
> How were this console= parameter added precisely?
> 
> I have added to the manual's Boot Parameters section an explicit mention
> of this.

I can confirm that both 

[...] console=ttyS0,115200n8 -- console=ttyS0,115200n8

and

[...] --- console=ttyS0,115200n8

work as expected. 

Part of the problems described here come from #764675. 

I think Florian's problems are actually a missing feature. For SysVinit
and upstart there is code in finish-install that enables a serial
console in inittab or upstart when it is detected (_not_ triggered by
the kernel command line)

http://sources.debian.net/src/finish-install/2.56/finish-install.d/90console/

systemd-enabled fresh systems do not have an inittab, so this entire
code is more or less a no-op. systemd systems get a serial console when
a serial console is specified on the kernel command line, which is most
likely either not done by virtinst or used in the wrong way (without
---, see above).

Takatsugu's comment is related to Bug #760947 .

Best Regards,
Bernhard


--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/20150804144047.ga6...@fliwatuet.svr02.mucip.net



partman does not accept lvm partition schema

2015-08-04 Thread S. Schauenburg
Good morning everyone,

after spending a lot of time trying to get partman to accept my LVM
(Logical Volume Manager) partitioning schema, I still remain unsuccessful.
Since this might very well be due my lack of experience with partman and
d-i (Debian Installer), I'd thought I'd put it onto the mailinglist
(already tried IRC) to ask for advice and/or feedback.

My goal:
 * get a Debian system installed (and partitioned) according to my
specifications with preseed
 * partitioning goal: /dev/sda1 as /boot, /dev/sda2 as PV (Physical Volume)
with one VG (Volume Group) which will contain several LV's (Logical Volume)

Status:
 * the preseeding mechanism works
 * partitioning does not work (using "partman-auto/method string lvm")
 * I tried a lot of variations of the "partman-auto/expert_recipe" recipe,
but none seem to work. I get messages like "No physical volume defined in
volume group"
 * Above leads me to assume either the recipe is still incorrect or the
wanted partition scheme is incompatible with partman

Is the partition schema I want even possible with partman? If not, can
partman be "fixed" or do I need to consider a workaround for this?

Thanks in advance.

Best regards,



Sebastian