Re: Kernel version for stretch
Hi, On 2016-02-02 08:34, Niels Thykier wrote: Based on the current 9 week upstream release cycle, the longterm branch for 2017 will presumably be based on Linux 4.10, released at the end of week 3 (22nd January 2017). That's well after the planned stretch freeze date so I don't see how it can be included. Indeed that is a bit unfortunate. With the freeze date already announced, I am very hesitant to move it. I wouldn't consider it a fail if we decided to shift the freeze date by two months [1], especially if this move helps project members to integrate better supported versions for their packages. Eventually, it would help us to have a better quality release and enhance its supportability over the years. Having that said, it would be nice to hear from Ben if it would be doable to go with 4.9 or with a 4.10rc for some time. [1] only a few persons seem to have noted those dates anyway (imho). -- Mehdi
Re: Bug#771208: unblock: busybox/1:1.22.0-14
On Wed, Feb 18, 2015 at 10:30:50PM +0100, Cyril Brulebois k...@debian.org wrote: Mehdi Dogguy me...@dogguy.org (2015-02-18): On Thu, Dec 11, 2014 at 08:52:05AM +0100, Ivo De Decker iv...@debian.org wrote: Could you do a new upload with only the security fix? I just did so and uploaded 1:1.22.0-9+deb8u1 to t-p-u. Please push both your jessie branch and tag to git. I don't have write access to d-i repos. I'd rather let someone else import the .dsc and push it back to alioth. -- Mehdi Dogguy -- 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/2015021821.gh1...@dogguy.org
Re: Bug#771208: unblock: busybox/1:1.22.0-14
On Thu, Dec 11, 2014 at 08:52:05AM +0100, Ivo De Decker iv...@debian.org wrote: Could you do a new upload with only the security fix? I just did so and uploaded 1:1.22.0-9+deb8u1 to t-p-u. Regards, -- Mehdi Dogguy -- 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/20150218212311.gf1...@dogguy.org
Re: Bug#778366: unblock: kfreebsd-10/10.1~svn274115-2
Le 2015-02-17 18:14, Cyril Brulebois a écrit : Control: tag -1 confirmed Hi, Steven Chamberlain ste...@pyro.eu.org (2015-02-14): Michael Gilbert wrote: Please consider unblocking kfreebsd-10. It fixes 2 security issues: https://security-tracker.debian.org/kfreebsd-10 When I saw this request come in, I meant to ask one of the maintainers to confirm they were happy with getting this into testing… A debdiff is attached. The other change is to limit the arch-dep packages to kfreebsd-any (which was forgotten in the previous upload). … which seems to be the case, so no objections from a d-i point of view. Hint added. Thanks. -- Mehdi -- 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/5e90e597e50157a59ead4d1a9dbfd...@dogguy.org
Bug#691334: task-gnome-desktop: Recommends obsolete system-config-printer
On 28/10/2012 19:06, Christian PERRIER wrote: I'm reluctant to upload tasksel as of now, because of that change, which I'm unsure if it's inline with the freeze policy I has been reverted before previous uploads… and committed back after that. I guess you could do the same this time as well. Regards, -- Mehdi -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/508d8b80.4080...@debian.org
Re: Please unblock/unblock-udeb/urgent netcfg/1.98
On 07/10/2012 18:58, Cyril Brulebois wrote: Hi folks, we delayed d-i wheezy beta 3 because of that nasty netcfg bug, and we had some buildd fun on powerpc; builds are here now, so please review push it to wheezy ASAP. Done. Cheers. -- Mehdi Dogguy مهدي الدڤي -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5071bad5.1020...@dogguy.org
Bug#674060: Doesn't support reading InRelease files
On 31/05/12 12:17, Bastian Blank wrote:
On Fri, May 25, 2012 at 11:01:57AM +0200, Mehdi Dogguy wrote:
index 67aa412..0b0f802 100644
--- a/src/parser_rfc822.c
+++ b/src/parser_rfc822.c
@@ -60,6 +60,7 @@ int di_parser_rfc822_read (char *begin, size_t size,
di_parser_info *info, di_pa
di_rstring field_modifier_string;
di_rstring value_string;
void *act = NULL;
+ int pgp_mode = 0;
cur = begin;
end = begin + size;
@@ -81,6 +82,25 @@ int di_parser_rfc822_read (char *begin, size_t size,
di_parser_info *info, di_pa
while (1)
{
+ if (!strncmp(cur, -BEGIN PGP SIGNED MESSAGE-, 34))
Please don't use magic numbers.
| const char pgp_begin = …;
| if (!strncmp(cur, pgp_begin, strlen(pgp_begin))
or something like that. The strlen call should be optimized away.
Also this string may only appear at the beginning of the file, not
somewhere in between. So this should be done before the large loop.
Also the end of the preamble can be searched with \n\n.
+ else if (pgp_mode !strncmp(cur, -BEGIN PGP SIGNATURE-, 29))
+ {
+// Let's exit, the rest of the file is not interesting
+cur += size;
+break;
+ }
Okay.
Thanks for the review! Please find attached an updated patch taking
into consideration your remarks.
Cheers,
--
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/
From c0b6669243e2282e0010d74790373764fe77b5ab Mon Sep 17 00:00:00 2001
From: Mehdi Dogguy me...@debian.org
Date: Wed, 23 May 2012 13:18:59 +0200
Subject: [PATCH] Add support for InRelease files (Closes: #674060)
---
src/parser_rfc822.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/src/parser_rfc822.c b/src/parser_rfc822.c
index 67aa412..eca63c6 100644
--- a/src/parser_rfc822.c
+++ b/src/parser_rfc822.c
@@ -60,6 +60,9 @@ int di_parser_rfc822_read (char *begin, size_t size, di_parser_info *info, di_pa
di_rstring field_modifier_string;
di_rstring value_string;
void *act = NULL;
+ int pgp_mode = 0;
+ const char *pgp_begin_msg = -BEGIN PGP SIGNED MESSAGE-;
+ const char *pgp_begin_sig = -BEGIN PGP SIGNATURE-;
cur = begin;
end = begin + size;
@@ -72,6 +75,15 @@ int di_parser_rfc822_read (char *begin, size_t size, di_parser_info *info, di_pa
continue;
}
+if (!strncmp(cur, pgp_begin_msg, strlen(pgp_begin_msg)))
+{
+ // Enable pgp_mode
+ pgp_mode = 1;
+ // Skip PGP header
+ cur = strstr (cur, \n\n);
+ cur += 2;
+}
+
nr++;
if (entry_new)
@@ -81,6 +93,12 @@ int di_parser_rfc822_read (char *begin, size_t size, di_parser_info *info, di_pa
while (1)
{
+ if (pgp_mode !strncmp(cur, pgp_begin_sig, strlen(pgp_begin_sig)))
+ {
+// Let's exit, the rest of the file is not interesting
+cur += size;
+break;
+ }
field_begin = cur;
readsize = end - field_begin READSIZE ? end - field_begin : READSIZE;
if (!readsize)
--
1.7.10
Bug#674060: Doesn't support reading InRelease files
On 24/05/12 17:57, Mehdi Dogguy wrote:
On 22/05/12 21:36, Mehdi Dogguy wrote:
It seems that src/release.c:di_release_read_file can't read
InRelease files (yet) because it is not strictly an rfc822 file.
Please find attached a tentative patch to add support for InRelease
files to libd-i. It makes src/parser_rfc822.c:di_parser_rfc822_read
skip PGP signature and headers.
My first patch had a minor issue: PGP clearsign signatures may contain
one or more Hash fields. The PGP signature header and the signed data
are separated by an empty line (not included in the signed data). So it
seems more reasonable (if pgp_mode) to skip entries until a empty line
is reached. This is fixed in the new patch attached to this message. For
your convenience, I also attach changes.diff which gives the
difference between the two patches.
There is one missing check (to be fully RFC 2440 compliant), the data
needs to be dash-unescaped. While this could be mandatory in general, it
seems unnecessary in out specific case (where we read Release, Packages,
Sources, Contents and Translation files) as it means that the read file
doesn't follow its spec.
Comments are welcome.
Regards,
--
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/
--- a/src/parser_rfc822.c
+++ b/src/parser_rfc822.c
@@ -89,12 +89,18 @@ int di_parser_rfc822_read (char *begin, size_t size, di_parser_info *info, di_pa
// Let's skip this line
cur += 35;
}
- else if (!strncmp(cur, -BEGIN PGP SIGNATURE-, 29))
+ else if (pgp_mode !strncmp(cur, -BEGIN PGP SIGNATURE-, 29))
{
// Let's exit, the rest of the file is not interesting
cur += size;
break;
}
+ if (pgp_mode == 1 *cur == '\n') {
+// Skip this empty line (last line of PGP headers)
+cur++;
+// Do not skip more newlines
+pgp_mode++;
+ }
field_begin = cur;
readsize = end - field_begin READSIZE ? end - field_begin : READSIZE;
if (!readsize)
@@ -159,11 +165,9 @@ int di_parser_rfc822_read (char *begin, size_t size, di_parser_info *info, di_pa
}
value_size = value_end - value_begin;
- if (pgp_mode == 1 !strncmp(field_begin, Hash, field_size)) {
-// Do not skip more Hash fields
-pgp_mode++;
-// Skip this entry (4 == ':' + ' ' + '\n' + '\n')
-cur += field_size + value_size + 4;
+ if (pgp_mode == 1) {
+// Skip this entry (3 == ':' + ' ' + '\n')
+cur += field_size + value_size + 3;
continue;
}
From 415831b3aa2a18019c1777698b449c0a8f2aca05 Mon Sep 17 00:00:00 2001
From: Mehdi Dogguy me...@debian.org
Date: Wed, 23 May 2012 13:18:59 +0200
Subject: [PATCH] Add support for InRelease files (Closes: #674060)
---
src/parser_rfc822.c | 26 ++
1 file changed, 26 insertions(+)
diff --git a/src/parser_rfc822.c b/src/parser_rfc822.c
index 67aa412..0b0f802 100644
--- a/src/parser_rfc822.c
+++ b/src/parser_rfc822.c
@@ -60,6 +60,7 @@ int di_parser_rfc822_read (char *begin, size_t size, di_parser_info *info, di_pa
di_rstring field_modifier_string;
di_rstring value_string;
void *act = NULL;
+ int pgp_mode = 0;
cur = begin;
end = begin + size;
@@ -81,6 +82,25 @@ int di_parser_rfc822_read (char *begin, size_t size, di_parser_info *info, di_pa
while (1)
{
+ if (!strncmp(cur, -BEGIN PGP SIGNED MESSAGE-, 34))
+ {
+// Enable pgp_mode
+pgp_mode = 1;
+// Let's skip this line
+cur += 35;
+ }
+ else if (pgp_mode !strncmp(cur, -BEGIN PGP SIGNATURE-, 29))
+ {
+// Let's exit, the rest of the file is not interesting
+cur += size;
+break;
+ }
+ if (pgp_mode == 1 *cur == '\n') {
+// Skip this empty line (last line of PGP headers)
+cur++;
+// Do not skip more newlines
+pgp_mode++;
+ }
field_begin = cur;
readsize = end - field_begin READSIZE ? end - field_begin : READSIZE;
if (!readsize)
@@ -145,6 +165,12 @@ int di_parser_rfc822_read (char *begin, size_t size, di_parser_info *info, di_pa
}
value_size = value_end - value_begin;
+ if (pgp_mode == 1) {
+// Skip this entry (3 == ':' + ' ' + '\n')
+cur += field_size + value_size + 3;
+continue;
+ }
+
field_string.string = field_begin;
field_string.size = field_size;
value_string.string = value_begin;
--
1.7.10
Bug#674060: Doesn't support reading InRelease files
tags 674060 + patch
thanks
On 22/05/12 21:36, Mehdi Dogguy wrote:
It seems that src/release.c:di_release_read_file can't read
InRelease files (yet) because it is not strictly an rfc822 file.
Please find attached a tentative patch to add support for InRelease
files to libd-i. It makes src/parser_rfc822.c:di_parser_rfc822_read skip
PGP signature and headers.
Regards,
--
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/
From caeda32359b1f3cbff3da9777d646f92f8c6b479 Mon Sep 17 00:00:00 2001
From: Mehdi Dogguy me...@debian.org
Date: Wed, 23 May 2012 13:18:59 +0200
Subject: [PATCH] Add support for InRelease files (Closes: #674060)
---
src/parser_rfc822.c | 22 ++
1 file changed, 22 insertions(+)
diff --git a/src/parser_rfc822.c b/src/parser_rfc822.c
index 67aa412..7049223 100644
--- a/src/parser_rfc822.c
+++ b/src/parser_rfc822.c
@@ -60,6 +60,7 @@ int di_parser_rfc822_read (char *begin, size_t size, di_parser_info *info, di_pa
di_rstring field_modifier_string;
di_rstring value_string;
void *act = NULL;
+ int pgp_mode = 0;
cur = begin;
end = begin + size;
@@ -81,6 +82,19 @@ int di_parser_rfc822_read (char *begin, size_t size, di_parser_info *info, di_pa
while (1)
{
+ if (!strncmp(cur, -BEGIN PGP SIGNED MESSAGE-, 34))
+ {
+// Enable pgp_mode
+pgp_mode = 1;
+// Let's skip this line
+cur += 35;
+ }
+ else if (!strncmp(cur, -BEGIN PGP SIGNATURE-, 29))
+ {
+// Let's exit, the rest of the file is not interesting
+cur += size;
+break;
+ }
field_begin = cur;
readsize = end - field_begin READSIZE ? end - field_begin : READSIZE;
if (!readsize)
@@ -145,6 +159,14 @@ int di_parser_rfc822_read (char *begin, size_t size, di_parser_info *info, di_pa
}
value_size = value_end - value_begin;
+ if (pgp_mode == 1 !strncmp(field_begin, Hash, field_size)) {
+// Do not skip more Hash fields
+pgp_mode++;
+// Skip this entry (4 == ':' + ' ' + '\n' + '\n')
+cur += field_size + value_size + 4;
+continue;
+ }
+
field_string.string = field_begin;
field_string.size = field_size;
value_string.string = value_begin;
--
1.7.10
Bug#638682: Higher severity
tags 638682 + patch
thanks
On 20/05/12 12:20, Joerg Jaspert wrote:
at some point in the future we want to change to only use the new
InRelease file. Which debootstrap currently does not support.
This is not RC, so i set it to important only, but if we can have
debootstrap additionally deal with InRelease short after wheezy, it
would be nice.
It would be even nicer if we could get it in Wheezy so that we can use
it once Wheezy if released. Please find attached a preliminary patch
that adds support for InRelease files in debootstrap. Using the proposed
patch, I've been able to create unstable and squeeze chroots. It
makes debootstrap check for InRelease files first since they are
supposed to be the default some time in the future. Comments are welcome!
The patch can make use of gpg to extract the signed data from the
InRelease file. I'm not sure it is necessary since the rest works just
fine if given an InRelease file instead of a Release file. I kept that
part commented in the patch and leave this decision to the maintainer
since it would add a strong dependency on gnupg… which doesn't seem
necessary.
Regards,
--
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/
From 89531acfb77c9b7bc5aca57c361c48dd63465a5d Mon Sep 17 00:00:00 2001
From: Mehdi Dogguy me...@debian.org
Date: Tue, 22 May 2012 12:18:31 +0200
Subject: [PATCH] Add support for InRelease files (Closes: #638682)
---
debian/changelog |7
functions| 93 --
2 files changed, 70 insertions(+), 30 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 904f437..d437191 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+debootstrap (1.0.40+nmu1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * Add support for InRelease files (Closes: #638682)
+
+ -- Mehdi Dogguy me...@debian.org Tue, 22 May 2012 12:16:57 +0200
+
debootstrap (1.0.40) unstable; urgency=low
[ Joey Hess ]
diff --git a/functions b/functions
index ad7b211..89312af 100644
--- a/functions
+++ b/functions
@@ -480,57 +480,90 @@ get_release_checksum () {
done | head -n 1
}
+extract_release_components () {
+ local reldest=$1; shift
+ TMPCOMPONENTS=$(sed -n 's/Components: *//p' $reldest)
+ for c in $TMPCOMPONENTS ; do
+ eval
+ case \\$c\ in
+ $USE_COMPONENTS)
+ COMPONENTS=\\$COMPONENTS \$c\
+ ;;
+ esac
+
+ done
+ COMPONENTS=$(echo $COMPONENTS)
+ if [ -z $COMPONENTS ]; then
+ mv $reldest $reldest.malformed
+ error 1 INVALIDREL Invalid Release file, no valid components
+ fi
+}
+
download_release_sig () {
local m1=$1
local reldest=$2
- local relsigdest=$TARGET/$($DLDEST rel $SUITE $m1 dists/$SUITE/Release.gpg)
+ local relsigdest=$3
+ local release_file_variant=$4
if [ -n $KEYRING ] [ -z $DISABLE_KEYRING ]; then
- progress 0 100 DOWNRELSIG Downloading Release file signature
- progress_next 50
- get $m1/dists/$SUITE/Release.gpg $relsigdest nocache ||
- error 1 NOGETRELSIG Failed getting release signature file %s \
- $m1/dists/$SUITE/Release.gpg
- progress 50 100 DOWNRELSIG Downloading Release file signature
+ if [ $release_file_variant != IN ]; then
+ progress 0 100 DOWNRELSIG Downloading Release file signature
+ progress_next 50
+ get $m1/dists/$SUITE/Release.gpg $relsigdest nocache ||
+error 1 NOGETRELSIG Failed getting release signature file %s \
+$m1/dists/$SUITE/Release.gpg
+ progress 50 100 DOWNRELSIG Downloading Release file signature
+ fi
info RELEASESIG Checking Release signature
- # Don't worry about the exit status from gpgv; parsing the output will
- # take care of that.
- (gpgv --status-fd 1 --keyring $KEYRING --ignore-time-conflict \
- $relsigdest $reldest || true) | read_gpg_status
+ if [ $release_file_variant = IN ]; then
+ (gpgv --status-fd 1 --keyring $KEYRING --ignore-time-conflict \
+ $relsigdest || true) | read_gpg_status
+ else
+ # Don't worry about the exit status from gpgv; parsing the output will
+ # take care of that.
+ (gpgv --status-fd 1 --keyring $KEYRING --ignore-time-conflict \
+ $relsigdest $reldest || true) | read_gpg_status
+ fi
progress 100 100 DOWNRELSIG Downloading Release file signature
elif [ -z $DISABLE_KEYRING ] [ -n $KEYRING_WANTED ]; then
warning KEYRING Cannot check Release signature; keyring file not available %s $KEYRING_WANTED
fi
+ if [ $release_file_variant = IN ]; then
+ # In both cases, we have to extract a Release file from the InRelease file
+ mv $relsigdest $reldest
+ # We redirect the output of gpg to /dev/null as it is useless at this stage
+ #if ! gpg --version /dev/null 21; then
+ # error 1 NEEDGPGV gnupg not installed, but required for InRelease extraction
+ #else
+ # (gpg --output $reldest --keyring $KEYRING --ignore-time-conflict \
+ # $relsigdest || true ) 2/dev/null
+ #fi
+ fi
}
download_release_indices () {
local m1=${MIRRORS%% *}
local reldest=$TARGET/$($DLDEST rel $SUITE $m1 dists/$SUITE/Release)
+ local
Bug#638682: Higher severity
On 22/05/12 18:16, Joey Hess wrote:
Mehdi Dogguy wrote:
The patch can make use of gpg to extract the signed data from the
InRelease file. I'm not sure it is necessary since the rest works just
fine if given an InRelease file instead of a Release file. I kept that
part commented in the patch and leave this decision to the maintainer
since it would add a strong dependency on gnupg… which doesn't seem
necessary.
debootstrap runs inside d-i which does not have gpg, only gpgv.
It cannot use gpg.
That's what I guessed (that's why I took the mv approach).
+ if [ $release_file_variant = IN ]; then
+ # In both cases, we have to extract a Release file from the
InRelease file
Says both cases, but only runs in for the inRelease case?
I meant both cases wrt the previous if … elif block. Sorry if that
wasn't clear enough.
+ # We redirect the output of gpg to /dev/null as it is useless
at this stage
+ #if ! gpg --version/dev/null 21; then
+ # error 1 NEEDGPGV gnupg not installed, but required for
InRelease extraction
+ #else
+ # (gpg --output $reldest --keyring $KEYRING
--ignore-time-conflict \
+ #$relsigdest || true ) 2/dev/null
+ #fi
I'd be inclined to remove this dead code.
Sure.
- if [ -z $COMPONENTS ]; then
- mv $reldest $reldest.malformed
- error 1 INVALIDREL Invalid Release file, no valid components
+if get $m1/dists/$SUITE/InRelease $inreldest nocache; then
The above line is wrongly indented.
Heh. I spotted it after submitting the patch :)
Thanks a lot for the prompt review! Here's the updated patch taking into
account your remarks.
Regards,
--
Mehdi Dogguy مهدي الدڤي
http://dogguy.org/
From 7790976684ac5e943958a7d93f80c8dbcfa0f195 Mon Sep 17 00:00:00 2001
From: Mehdi Dogguy me...@debian.org
Date: Tue, 22 May 2012 12:18:31 +0200
Subject: [PATCH] Add support for InRelease files (Closes: #638682)
---
debian/changelog |7 +
functions| 85 +++---
2 files changed, 62 insertions(+), 30 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 904f437..d437191 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+debootstrap (1.0.40+nmu1) UNRELEASED; urgency=low
+
+ * Non-maintainer upload.
+ * Add support for InRelease files (Closes: #638682)
+
+ -- Mehdi Dogguy me...@debian.org Tue, 22 May 2012 12:16:57 +0200
+
debootstrap (1.0.40) unstable; urgency=low
[ Joey Hess ]
diff --git a/functions b/functions
index ad7b211..44f1cae 100644
--- a/functions
+++ b/functions
@@ -480,57 +480,82 @@ get_release_checksum () {
done | head -n 1
}
+extract_release_components () {
+ local reldest=$1; shift
+ TMPCOMPONENTS=$(sed -n 's/Components: *//p' $reldest)
+ for c in $TMPCOMPONENTS ; do
+ eval
+ case \\$c\ in
+ $USE_COMPONENTS)
+ COMPONENTS=\\$COMPONENTS \$c\
+ ;;
+ esac
+
+ done
+ COMPONENTS=$(echo $COMPONENTS)
+ if [ -z $COMPONENTS ]; then
+ mv $reldest $reldest.malformed
+ error 1 INVALIDREL Invalid Release file, no valid components
+ fi
+}
+
download_release_sig () {
local m1=$1
local reldest=$2
- local relsigdest=$TARGET/$($DLDEST rel $SUITE $m1 dists/$SUITE/Release.gpg)
+ local relsigdest=$3
+ local release_file_variant=$4
if [ -n $KEYRING ] [ -z $DISABLE_KEYRING ]; then
- progress 0 100 DOWNRELSIG Downloading Release file signature
- progress_next 50
- get $m1/dists/$SUITE/Release.gpg $relsigdest nocache ||
- error 1 NOGETRELSIG Failed getting release signature file %s \
- $m1/dists/$SUITE/Release.gpg
- progress 50 100 DOWNRELSIG Downloading Release file signature
+ if [ $release_file_variant != IN ]; then
+ progress 0 100 DOWNRELSIG Downloading Release file signature
+ progress_next 50
+ get $m1/dists/$SUITE/Release.gpg $relsigdest nocache ||
+error 1 NOGETRELSIG Failed getting release signature file %s \
+$m1/dists/$SUITE/Release.gpg
+ progress 50 100 DOWNRELSIG Downloading Release file signature
+ fi
info RELEASESIG Checking Release signature
- # Don't worry about the exit status from gpgv; parsing the output will
- # take care of that.
- (gpgv --status-fd 1 --keyring $KEYRING --ignore-time-conflict \
- $relsigdest $reldest || true) | read_gpg_status
+ if [ $release_file_variant = IN ]; then
+ (gpgv --status-fd 1 --keyring $KEYRING --ignore-time-conflict \
+ $relsigdest || true) | read_gpg_status
+ else
+ # Don't worry about the exit status from gpgv; parsing the output will
+ # take care of that.
+ (gpgv --status-fd 1 --keyring $KEYRING --ignore-time-conflict \
+ $relsigdest $reldest || true) | read_gpg_status
+ fi
progress 100 100 DOWNRELSIG Downloading Release file signature
elif [ -z $DISABLE_KEYRING ] [ -n $KEYRING_WANTED ]; then
warning KEYRING Cannot check Release signature; keyring file not available %s
Bug#674060: Doesn't support reading InRelease files
Source: libdebian-installer
Version: 0.80
Severity: important
Tags: d-i
Hi,
It seems that src/release.c:di_release_read_file can't read InRelease
files (yet) because it is not strictly an rfc822 file.
It would be nice to fix this in time for Wheezy so that we can
consider getting rid of Release{,.gpg} files after Wheezy release.
This issue blocks #673625.
Regards,
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120522193627.12051.79029.reportbug@potassium
Re: Wheezy release: CDs are not big enough any more...
On 16/05/12 13:41, Wookey wrote: is there any reason not to just upload this to Debian? There are ITPs filed for it: - http://bugs.debian.org/582884 - http://bugs.debian.org/576359 Regards, -- Mehdi -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fb3b89b.2030...@debian.org
Re: GSoC Project Idea: WPA2 support for the debian installer
On 07/03/12 11:17, Max Linke wrote: I would like to know if it is a appropriate project for GSoC to add WPA2 support for the debian installer. WPA2 is supported in Wheezy's installer, iirc. (as this installation report #637467 confirms). Best, -- Mehdi -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f573cf1.9000...@dogguy.org
Re: please unblock udev
On 16/04/2011 01:06, Marco d'Itri wrote: Unblocked (acked by otavio on IRC). Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dac5ca6.4080...@dogguy.org
Re: Squeeze can't fit on 512MiB
On 12/15/2010 07:02 PM, Joey Hess wrote: Samuel Thibault wrote: - Gnome grew from 1830MiB to 2409MiB, still can't fit on just CD1. This should fix itself once both tasksel 2.88 and gnome-core 1:2.30+7 reach testing. Should happen by monday, would appreciate any testing you can do. Both migrated during yesterday's britney run, fwiw. Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d09d911.9080...@dogguy.org
Re: Bug#606441: unblock: yaboot/1.3.13a-1squeeze1
On 12/11/2010 06:16 PM, Otavio Salvador wrote: On Fri, Dec 10, 2010 at 19:52, Mehdi Dogguy me...@dogguy.org wrote: On 12/09/2010 10:27 AM, Gaudenz Steinlin wrote: I sponsored an uploaded of yaboot to testing-proposed-updates with the following changes to fix RC bugs: yaboot (1.3.13a-1squeeze1) testing-proposed-updates; urgency=low . * Team upload. * Get scsi, sata, and firewire drive info from sysfs as legacy /proc/scsi interface does not exist anymore. (Closes: #572869, #377097, #342833, #289201) * Use persistent device naming symlinks, UUID and LABEL tags instead of unix block device names. (Closes: #580455) * debian/copyright: Add copyright notice from ofpath. The package has to go thourgh t-p-u because there is a newer upstream version already uploaded to sid. I'm ok to approve this upload but I prefer to have an ack from Otavio (or boot folks) first. Please accept it however in the yaboot case I would prefer to try to get a newer version into squeeze after this fix has been done. So in my opinion we ought: - accept the t-p-u upload; Done. - get those fixes into the sid one and if it proves stable get it into squeeze. I wonder how the if part will be checked in such short timeframe. Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d03bf19.9010...@dogguy.org
Re: Bug#606441: unblock: yaboot/1.3.13a-1squeeze1
On 12/09/2010 10:27 AM, Gaudenz Steinlin wrote: I sponsored an uploaded of yaboot to testing-proposed-updates with the following changes to fix RC bugs: yaboot (1.3.13a-1squeeze1) testing-proposed-updates; urgency=low . * Team upload. * Get scsi, sata, and firewire drive info from sysfs as legacy /proc/scsi interface does not exist anymore. (Closes: #572869, #377097, #342833, #289201) * Use persistent device naming symlinks, UUID and LABEL tags instead of unix block device names. (Closes: #580455) * debian/copyright: Add copyright notice from ofpath. The package has to go thourgh t-p-u because there is a newer upstream version already uploaded to sid. I'm ok to approve this upload but I prefer to have an ack from Otavio (or boot folks) first. (CC'ing Otavio and -boot). Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d02a122.8080...@dogguy.org
Re: Bug#606441: unblock: yaboot/1.3.13a-1squeeze1
On 12/10/2010 11:07 PM, Lennart Sorensen wrote: Of course if the new version currently in unstable that many people have asked for for years was used instead, a huge number of newer powerpc machines might actually work with Debian. 1.3.13a is simply useless for most modern powerpc machines. Well, Gaudenz and Milan worked on fixing the reported RC bugs against yaboot. And, I'd rather thank them for that. sid's version doesn't look like fixing the critical problems experienced by our users. Besides, I don't see any bugreport of yours explaining your issue. I had to move to grub2 instead with much manual tweaking and debuging (with upstream help) to get a working bootloader for squeeze. Any bugreport I could read? Regards, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d02ace9.9030...@dogguy.org
Re: Some bugfixes for LILO to go into Squeeze [new DM]
On 12/04/2010 10:28 PM, Joachim Wiedorn wrote: Hello Release Team, the CTTE disposed some days before, that I am allowed to be the new DM for the package LILO: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587886#158 Now it would be possible to update the LILO package (based on lilo 22.8-8.3) with some bugfixes to work better within Squeeze. My question: If I create an updated LILO package for testing/squeeze, would the release team accept this new package and let it go into squeeze? Yes. Sending us a debdiff before the upload would be appreciated. Have a nice day, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cfd6a0b.5030...@dogguy.org
Re: [RFC] disabled root account / distinct group for users with administrative privileges
On 20/10/2010 11:18, Petter Reinholdtsen wrote: So I would suggest to use a name that is more likely to be unique. unique wrt. what? admin seems unique since not used in Debian yet. Happy hacking, -- Mehdi Dogguy مهدي الدڤي http://dogguy.org/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cbec179.6030...@dogguy.org
Re: Freeze exception for busybox 1.17.1-2
On 0, Aurelien Jarno aurel...@aurel32.net wrote: Hi, I have just uploaded busybox version 1:1.17.1-2 into unstable (it was previously in experimental), which supports Hurd and GNU/kFreeBSD. As already agreed with Otavio, could you please unblock this package? Unblocked. Cheers, -- Mehdi Dogguy -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100807172815.gx20...@dogguy.org
Re: Intending to upload DHCP v4 to unstable (small transition necessary)
On 0, Andrew Pollock apoll...@debian.org wrote: I still await an ACK from the release team. an ACK :) Regards, -- Mehdi Dogguy -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100628220056.ga22...@dogguy.org
