[RFC] Packages that looks ready for uploading
Otavio Salvador
Hash: SHA1
Hello folks,
I've been finally able to take a more careful look at our repository and
make up a list of packages that I believe we ought to upload.
Please, if you're one of responsable by the package and you agree with
me please go ahead and upload it or comment why you believe it is not
ready.
Packages that looks OK for upload
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
apt-setup
arcboot-installer
auto-install
cdebconf
clock-setup
colo-installer
finish-install
grub-installer
installation-report
iso-scan
kickseed
libdebian-installer
lilo-installer
linux-kernel-di-alpha-2.6
linux-kernel-di-mips-2.6
linux-kernel-di-mipsel-2.6
linux-kernel-di-s390-2.6
linux-kernel-di-sparc-2.6
linux-modules-di-alpha-2.6
linux-modules-di-armel-2.6
linux-modules-di-hppa-2.6
linux-modules-di-ia64-2.6
linux-modules-di-mips-2.6
linux-modules-di-mipsel-2.6
linux-modules-di-powerpc-2.6
linux-modules-di-s390-2.6
linux-modules-di-sparc-2.6
live-installer
localechooser
lowmem
main-menu
mdcfg
mountmedia
nobootloader
partconf
partitioner # someone need to upload it after we've parted in
partman-auto
partman-auto-lvm
partman-base # i'll take it
partman-basicfilesystems
partman-crypto
partman-ext3
partman-jfs
partman-md
partman-partitioning
partman-reiserfs
partman-xfs
pkgsel
prep-installer
preseed
quik-installer
rescue
rootskel-gtk
sibyl-installer
silo-installer
yaboot-installer
zipl-installer
Packages that has translation-only or really trivial changes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
aboot-installer
anna
cdebconf-entropy
cdebconf-terminal
cdrom-checker
cdrom-detect
cdrom-retriever
efi-reader
elilo-installer
kbd-chooser
lvmcfg
media-retriever
net-retriever
netcfg
network-console
partman-auto-crypto
partman-basicmethods
partman-efi
partman-lvm
partman-palo
partman-prep
rootskel
s390-dasd
s390-netdevice
tzsetup
udpkg
user-setup
vmelilo-installer
I think we ought to do a full upload cycle. That will give us the
required feedback of what the real state of the installer and also give
to translators a good feeling of what is the real state of installer in
their language.
I believe we'll end up finding some bugs and will have few days of an
unstable installer but I think this early in cycle it is not a really
bad thing since it will allow us to really get those things deplyed and
receive feedback from users.
Even tough the minor changes and translation-only uploads aren't
/required/ now, I'd like to do those after the first set of packages has
been uploaded so we could do an installer upload and really start the
Alpha1 release preparation.
A very important thing is that porters need to upload their kernel
packages so we really have full installer using latest kernel and
discover problems on it as soon as possible.
Any comments? Objections?
Cheers,
- --
O T A V I O S A L V A D O R
- ---------------------------------------------
E-mail: ota...@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
- ---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>
iEYEARECAAYFAkoq4BUACgkQLqiZQEml+FUfXQCghYAJkFtDg5LldUFd/Zk6dQZu
kmgAni5mThCRzvo1cF+XVKG6znx++rbV
=+4w3
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-bo...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Martin Michlmayr
> Packages that looks OK for upload
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I uploaded the following packages:
> arcboot-installer
> colo-installer
> nobootloader
> sibyl-installer
These need some attention:
> linux-kernel-di-mips-2.6
> linux-kernel-di-mipsel-2.6
> linux-modules-di-mips-2.6
> linux-modules-di-mipsel-2.6
Would you mind massbuilding them?
> linux-modules-di-armel-2.6
linux-modules-extra-2.6 2.6.29 failed to build on armel, so uploading
this one doesn't make sense.
--
Martin Michlmayr
http://www.cyrius.com/
Christian Perrier
> localechooser
I have pending changes for the console-setup switch (patch attached),
which are basically aimed at installing c-s on the target system in
*all* cases where we were previously configuring the console with kbd
and kbd console fonts.
These are not the main change for the console-setup and are much less
invasive than the change where we'll replace kbd-config by
console-setup-udeb, but they could have unexpected consequences
(mostly extra questions as I reported elsewhere).
I would welcome comments about these changes before committing
them...and uploading localechooser.
PS: one should notice that, if we validate these changes, we could
soon drop a few hacks we currently have in finish-install and
unconditionnally install console-setup for all languages. That would
save some code in finish-install....and a few bytes in languagelist.
That would however mean installing c-s for languages for which we
currently install nothing specific for the console handling and don't
change the default console font (languages supported only in the
graphical installer, and CJK languages).
Otavio Salvador
On Sun, Jun 7, 2009 at 11:31 AM, Christian Perrier<bub...@debian.org> wrote:
> Quoting Otavio Salvador (ota...@debian.org):
> PS: one should notice that, if we validate these changes, we could
> soon drop a few hacks we currently have in finish-install and
> unconditionnally install console-setup for all languages. That would
> save some code in finish-install....and a few bytes in languagelist.
>
> That would however mean installing c-s for languages for which we
> currently install nothing specific for the console handling and don't
> change the default console font (languages supported only in the
> graphical installer, and CJK languages).
One thing that worries me is how we'll support it for Lenny'n Half?
I believe we'll need to move the logic to decide about c-s (in target)
to a lenny-support package and it would be nice if we could start
working on that at same time we prepare the c-s switch to avoid huge
delays later.
Commends?
--
Otavio Salvador O.S. Systems
E-mail: ota...@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
Otavio Salvador
On Sun, Jun 7, 2009 at 5:11 AM, Martin Michlmayr<t...@cyrius.com> wrote:
> * Otavio Salvador <ota...@debian.org> [2009-06-06 18:31]:
>> Packages that looks OK for upload
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> I uploaded the following packages:
>
>> arcboot-installer
>> colo-installer
>> nobootloader
>> sibyl-installer
Great and thanks :-)
> These need some attention:
>
>> linux-kernel-di-mips-2.6
>> linux-kernel-di-mipsel-2.6
>> linux-modules-di-mips-2.6
>> linux-modules-di-mipsel-2.6
>
> Would you mind massbuilding them?
Sure not; will do it today.
>> linux-modules-di-armel-2.6
>
> linux-modules-extra-2.6 2.6.29 failed to build on armel, so uploading
> this one doesn't make sense.
Yes, indeed. It would be nice if we could get it done just to have it
all in sync but not really a high priority task.
--
Otavio Salvador O.S. Systems
E-mail: ota...@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
Christian Perrier
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I had a look down to iso-scan....
>
> apt-setup
Has trivial changes (merge from Ubuntu which we can assume safely tested)
> auto-install
The changes there are longstanding ones by Phil Hands:
* check for dhcp preseed (closes: #511683)
We can probably safely assume that Phil knows what he does..:)
> cdebconf
CLearly safe changes (unbranding logo)
> clock-setup
Clearly safe changes as well
> finish-install
Safe changes
> grub-installer
> installation-report
Trivial changes
> iso-scan
Changes seem safe. One is a preparation for ext4.
Felix Zielcke
> > Packages that looks OK for upload
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Trivial changes
What about my patch for grub-installer I sent yesterday?
Can this be included in the next upload or would it be better to wait?
Otavio already said on IRC that it's okay for him but I should wait for
more comments.
drivemap is only used on a not yet uploaded grub2 and the UUID stuff
works fine with the lenny grub2.
update-grub in lenny already generates them, it's just the
grub-installer's generated 30_otheros which doestn't use them yet.
--
Felix Zielcke
Christian Perrier
> > > grub-installer
> >
> > Trivial changes
>
> What about my patch for grub-installer I sent yesterday?
> Can this be included in the next upload or would it be better to wait?
> Otavio already said on IRC that it's okay for him but I should wait for
> more comments.
To make it clear: grub-installer changes should not have been
mentioned in my mail. "Trivial changes" above do *only* apply to
installation-report that was following grub-installer in Otavio's
list.
I didn't look at grub-installer bu I suspect that pending changes
there might not be trivial changes.
So, in short, someone familiar with GRUB stuff should look at the package.
Otavio Salvador
On Tue, Jun 9, 2009 at 2:05 PM, Christian Perrier<bub...@debian.org> wrote:
[...]
> To make it clear: grub-installer changes should not have been
> mentioned in my mail. "Trivial changes" above do *only* apply to
> installation-report that was following grub-installer in Otavio's
> list.
Are you going to handle the uploads of the packages you've did a look at?
--
Otavio Salvador O.S. Systems
E-mail: ota...@ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
Christian Perrier
> Hello Christian,
>
> On Tue, Jun 9, 2009 at 2:05 PM, Christian Perrier<bub...@debian.org> wrote:
> [...]
> > To make it clear: grub-installer changes should not have been
> > mentioned in my mail. "Trivial changes" above do *only* apply to
> > installation-report that was following grub-installer in Otavio's
> > list.
>
> Are you going to handle the uploads of the packages you've did a look at?
I can, but not before the week-end.
Christian Perrier
> Packages that looks OK for upload
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
I uploaded a few, namely:
> apt-setup
> auto-install
> clock-setup
> finish-install
> installation-report
> iso-scan
> kickseed
> lilo-installer
> lowmem
Christian Perrier
> main-menu
The following changes are afar from trivial:
* After the debconf priority was lowered because of an error, return to the
default priority in one step when next a component runs successfully.
* Instead of lowering the debconf priority after the user backs up from a
question, match the priority at which the menu is displayed to the current
debconf priority. Closes: #331679.
However, they're pending in the SVN since December and it's certainly
time for us to upload them. I haven't tested them but I'll grant Frans
the usual confidence we have in his changes for being well tested
(would it be changes of line, then I would recommend more
testing...:-))
So, I'll upload.
Christian Perrier
More uploads done:
> main-menu
> mdcfg
> mountmedia
> nobootloader
> partconf
> partman-auto
> partman-auto-lvm
Vincent McIntyre
Can someone check that choose-mirror is the correct version please?
And that it actually works?
I reopened #517644 but have had no response after 3+ weeks.
See also #532840, which might be related.
Hopefully this can be sorted out before 5.0.2 goes out.
Thanks
Vince
Luk Claes
> Can someone check that choose-mirror is the correct version please?
> And that it actually works?
> I reopened #517644 but have had no response after 3+ weeks.
Well, reopening was strange as a fixed version was in proposed-updates
at that time, though as there are no CD images for it, I left it alone
so you and others would not keep reporting it.
Feel free to test with the version in proposed-updates to really make
sure it's fixed.
> See also #532840, which might be related.
That has been fixed in the previous point release of etch
(debian-installer 20070308etch5).
> Hopefully this can be sorted out before 5.0.2 goes out.
As it is in proposed-updates it should make it to 5.0.2 without problems.
Cheers
Luk
Vincent....@csiro.au
> Vincent McIntyre wrote:
> > Can someone check that choose-mirror is the correct version please?
> > And that it actually works?
> > I reopened #517644 but have had no response after 3+ weeks.
>
> Well, reopening was strange as a fixed version was in proposed-updates
> at that time, though as there are no CD images for it, I left it alone
> so you and others would not keep reporting it.
I had no evidence that it was fixed. The version I could access wasn't,
but I expected it should be, going by the dates in the changelogs. So I
thought I should report that fact.
> Feel free to test with the version in proposed-updates to really make
> sure it's fixed.
I'm not completely sure how to do this. From what I can gather from [1]
I need to build my own installer image, which I'll have a go at.
I initially thought would be able to just "patch in" the updated
choose-mirror, but this appears to require building a CD [2].
Am I on the right track here?
> > See also #532840, which might be related.
>
> That has been fixed in the previous point release of etch
> (debian-installer 20070308etch5).
ok, thank you.
Vince
[1] http://wiki.debian.org/DebianInstaller/Build
[2] http://wiki.debian.org/DebianInstaller/Modify
Otavio Salvador
Hash: SHA1
Hello folks,
Here goes the updated list with the still missed packages. Since first
message a total of 34 packages were upload and I'd like to thank people
who worked on it.
Please take a look on the remaining packages and process them if you're
the porter or active on them.
Otavio Salvador <ota...@debian.org> writes:
> Packages that looks OK for upload
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> libdebian-installer
> linux-modules-di-armel-2.6
> linux-modules-di-hppa-2.6
> linux-modules-di-powerpc-2.6
> linux-modules-di-s390-2.6
> localechooser
> partconf
> partitioner # someone need to upload it after we've parted in
> partman-auto
> partman-auto-lvm
> partman-base # i'll take it
> partman-crypto
> partman-ext3
> partman-jfs
> partman-md
> partman-partitioning
> partman-reiserfs
> partman-xfs
> pkgsel
> prep-installer
> quik-installer
> rescue
> silo-installer
> zipl-installer
Bellow goes few details about specific packages.
linux-modules-*
~~~~~~~~~~~~~~~
The remaining linux-modules packages are the ones I couldn't massbuild
since they were not available on mirror.
Linux kernel 2.6.30 is expected to be upload in Sunday and would be nice
if porters could start taking a look at more invasive changes in kernel
that could affect us.
parted related packages
~~~~~~~~~~~~~~~~~~~~~~~
partman-base and partitioner are waiting for parted on NEW. This is also
going to allow us to enable ext4 support for testing.
Thank you folks and let's keep the good work :-)
Cheers,
- --
O T A V I O S A L V A D O R
- ---------------------------------------------
E-mail: ota...@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
- ---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8+ <http://mailcrypt.sourceforge.net/>
iEYEARECAAYFAkoyt/YACgkQLqiZQEml+FWfmgCeMhx+CzhEOOX+K6AwU5x4Wdn0
o9UAoKfpLC/MZL8HO/7C7s/ntd5pQKkw
=uq2Y
Christian Perrier
> > Packages that looks OK for upload
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I uploaded:
> > partconf
> > partman-auto
> > partman-auto-lvm
(those yesterday)
> > partman-crypto
> > partman-ext3
> > partman-jfs
> > partman-md
> > partman-partitioning
> > partman-reiserfs
> > partman-xfs
> > pkgsel
> > rescue
(today)
Remaining:
> > libdebian-installer
I know there's a trick to build it...:-)...but needs to find it again.
> > localechooser
I need to ponder whether I include the parts that are part of
console-setup switch. I think I will as this exposes c-s quite widely
> > partitioner # someone need to upload it after we've parted in
waiting for parted
> > partman-base # i'll take it
ditto
> > prep-installer
> > quik-installer
both need a powerpc porter to upload them
> > silo-installer
needs a Sparc porter
> > zipl-installer
needs an s390 porter
Christian Perrier
> Remaining:
>
> > > libdebian-installer
>
> I know there's a trick to build it...:-)...but needs to find it again.
Uploaded
>
> > > localechooser
>
> I need to ponder whether I include the parts that are part of
> console-setup switch. I think I will as this exposes c-s quite widely
Uploaded with the console-setup changes. After all, we do
want to expose this to user testing don't we?
Christian Perrier
> Packages that has translation-only or really trivial changes
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I worked on those today. After all, many of them had no upload since
September 2008 and thus has numerous translation updates.
While I was at this, I bumped debhelper compatibility levels to 6 (4
is considered deprecated). I did not choose 7 on the (quite vague)
assumption that being N+1 is more or less being on the safe side..:-)
So, I uploaded:
> anna
> cdebconf-entropy
> cdebconf-terminal
> cdrom-checker
> cdrom-detect
> cdrom-retriever
> kbd-chooser
> network-console
> partman-auto-crypto
> partman-basicmethods
> partman-efi
> partman-lvm
> rootskel
> tzsetup
> udpkg
> user-setup
The following was not uploaded because they need to be done by porters:
> aboot-installer
> efi-reader
> elilo-installer
> partman-palo
> partman-prep
> s390-dasd
> s390-netdevice
> vmelilo-installer
The following has not been done...because I jumped over them by mistake..:-)
> lvmcfg
> media-retriever
> net-retriever
> netcfg
I'll try to do them in the next hours|days.
Wouter Verhelst
> Quoting Otavio Salvador (ota...@debian.org):
> The following was not uploaded because they need to be done by porters:
> > vmelilo-installer
vmelilo-installer is specific to a rather rare m68k subarch. It should
not be kicked from the repository (we still do care about m68k), but it
should not be of much concern to d-i development anymore these days.
--
The biometric identification system at the gates of the CIA headquarters
works because there's a guard with a large gun making sure no one is
trying to fool the system.
http://www.schneier.com/blog/archives/2009/01/biometrics.html
Otavio Salvador
> On Sun, Jun 14, 2009 at 07:32:56PM +0200, Christian Perrier wrote:
>> Quoting Otavio Salvador (ota...@debian.org):
> [...]
>> The following was not uploaded because they need to be done by porters:
> [...]
>> > vmelilo-installer
>
> vmelilo-installer is specific to a rather rare m68k subarch. It should
> not be kicked from the repository (we still do care about m68k), but it
> should not be of much concern to d-i development anymore these days.
Yes I agree that we shouldn't worry too much about it but if we can keep
it in sync with rest it is better and makes porter's life easier too.
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: ota...@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
Stephen R Marenka
> Wouter Verhelst <wou...@debian.org> writes:
>
> > On Sun, Jun 14, 2009 at 07:32:56PM +0200, Christian Perrier wrote:
> >> Quoting Otavio Salvador (ota...@debian.org):
> > [...]
> >> The following was not uploaded because they need to be done by porters:
> > [...]
> >> > vmelilo-installer
> >
> > vmelilo-installer is specific to a rather rare m68k subarch. It should
> > not be kicked from the repository (we still do care about m68k), but it
> > should not be of much concern to d-i development anymore these days.
>
> Yes I agree that we shouldn't worry too much about it but if we can keep
> it in sync with rest it is better and makes porter's life easier too.
I can upload it if that would make life easier. :)
Peace,
Stephen
--
Stephen R. Marenka If life's not fun, you're not doing it right!
<ste...@marenka.net>
Colin Watson
> On Mon, Jun 15, 2009 at 10:05:04AM -0300, Otavio Salvador wrote:
> > Wouter Verhelst <wou...@debian.org> writes:
> > > On Sun, Jun 14, 2009 at 07:32:56PM +0200, Christian Perrier wrote:
> > >> Quoting Otavio Salvador (ota...@debian.org):
> > >> > vmelilo-installer
> > >
> > > vmelilo-installer is specific to a rather rare m68k subarch. It should
> > > not be kicked from the repository (we still do care about m68k), but it
> > > should not be of much concern to d-i development anymore these days.
> >
> > Yes I agree that we shouldn't worry too much about it but if we can keep
> > it in sync with rest it is better and makes porter's life easier too.
>
> I can upload it if that would make life easier. :)
Yes please. How does one go about uploading m68k-only packages? Don't
you have to do a source+m68k upload, which presumably the main archive
would reject because it doesn't know about m68k?
--
Colin Watson [cjwa...@debian.org]
Wouter Verhelst
> Yes please. How does one go about uploading m68k-only packages? Don't
> you have to do a source+m68k upload, which presumably the main archive
> would reject because it doesn't know about m68k?
Yes, indeed. We can upload to debian-ports, but not to the main archive
(which is why I suggested not to worry about it ;)
--
The biometric identification system at the gates of the CIA headquarters
works because there's a guard with a large gun making sure no one is
trying to fool the system.
http://www.schneier.com/blog/archives/2009/01/biometrics.html
Stephen R Marenka
> On Thu, Jun 18, 2009 at 02:54:48PM +0100, Colin Watson wrote:
> > Yes please. How does one go about uploading m68k-only packages? Don't
> > you have to do a source+m68k upload, which presumably the main archive
> > would reject because it doesn't know about m68k?
>
> Yes, indeed. We can upload to debian-ports, but not to the main archive
> (which is why I suggested not to worry about it ;)
Argh! I forgot about that. Also uploading source to d-ports is only
allowed for unreleased not for sid.
Goswin von Brederlow
> On Thu, Jun 18, 2009 at 06:08:51PM +0200, Wouter Verhelst wrote:
>> On Thu, Jun 18, 2009 at 02:54:48PM +0100, Colin Watson wrote:
>> > Yes please. How does one go about uploading m68k-only packages? Don't
>> > you have to do a source+m68k upload, which presumably the main archive
>> > would reject because it doesn't know about m68k?
>>
>> Yes, indeed. We can upload to debian-ports, but not to the main archive
>> (which is why I suggested not to worry about it ;)
>
> Argh! I forgot about that. Also uploading source to d-ports is only
> allowed for unreleased not for sid.
>
> Peace,
>
> Stephen
Create some arch:all package by the source and upload source+all.
MfG
Goswin