Re: Re-planning for 12.6
Hi, On Mon, 01, Apr, 2024 at 01:07:27PM +0100, Adam D. Barratt spoke thus.. > April 13th > - Not great for me for personal reasons, mhy previously said no. I > could probably do if need be 13th is completely out for me. > May 11th > - Should work for me Looks like it'll work at present. Thanks, Mark -- Mark Hymers signature.asc Description: PGP signature
Re: Planning for 12.6
On Mon, 12, Feb, 2024 at 06:04:17PM +, Jonathan Wiltshire spoke thus.. > Hi, > > 12.6 should be around 10th April, so please indicate availability for: > > 7 April > 13 April > 20 April 7th or 20th should be ok, but 13th is out for me. Mark -- Mark Hymers signature.asc Description: PGP signature
Re: Planning for 12.5/11.9
On Tue, 19, Dec, 2023 at 09:25:06PM +, Jonathan Wiltshire spoke thus.. > It's time to set a date for 12.5 (taking account of the emergency .4) and > 11.9. I expect this to be the penultimate update for bullseye before LTS. > > Please indicate availability for: > > Saturday 3rd February (preferred for cadence) > Saturday 10th February > Saturday 17th February Sorry for the delay. I can currently do any of those for ftp. Mark -- Mark Hymers signature.asc Description: PGP signature
Re: 11.8/12.2 planning
On Mon, 24, Jul, 2023 at 07:25:13PM +0100, Jonathan Wiltshire spoke thus.. > Let's say 30 Sep is still preferred, 7th Oct or at a stretch 14th Oct are > options. Please indicate your availability for those three. I can do any of the above for ftp. Mark -- Mark Hymers signature.asc Description: PGP signature
Re: 11.8 planning
On Mon, 19, Jun, 2023 at 10:02:27PM +0100, Jonathan Wiltshire spoke thus.. > Hi, > > I'm sending this separately to a similar mail for 12.1. That's because the > timings are far enough out that they would make sense on separate weekends, > but they could also be stretched[1] and combined. > > Two months from 29th April is around the 1st July, so I propose: > > 1st July > 8th July > 15th July at a push Same as the 12.1 - 15th is out, but 1st and 8th are ok. Mark -- Mark Hymers
Re: 12.1 planning
On Mon, 19, Jun, 2023 at 10:04:06PM +0100, Jonathan Wiltshire spoke thus.. > Hi, > > The promised 4-6 weeks following release for 12.1 looks like: > > 8th July (4) > 15th July (5) > 22nd July (6) > > The first of them would combine with a very stretched 11.8; SRM might > prefer to get 11.8 done earlier and leave more time for 12.1 to mature. I can't do the 15th, so someone else from ftp would have to do it. The other two currently look ok. Mark -- Mark Hymers
Re: 11.6 planning
On Thu, 17, Nov, 2022 at 09:33:33PM +, Adam D. Barratt spoke thus.. > Hi, > > We've managed to slip behind on getting a bullseye point release > sorted, again. :-( I realise we're heading towards the holidays at a > surprising rate of knots, but hopefully we can find a generally > agreeable date. > > Please could you indicate your availability and preferences between: > > - December 3rd > - December 10th > - December 17th > Sadly all three of those weekends are already booked up for me. Sorry, Mark -- Mark Hymers
Re: 11.4 planning
On Fri, 17, Jun, 2022 at 08:31:23PM +0100, Adam D. Barratt spoke thus..
> Hi,
>
> We're (again) running behind in getting the next point release for
> bullseye sorted, and I know we're about to run into the Deb{Camp,Conf}
> period. I think the possible dates that make sense are:
>
> - July 2nd (means freezing next weekend, but so be it)
> - July 9th
I can do the 2nd but not the 9th.
Mark
--
Mark Hymers
Re: 11.3 and 10.12 planning
On Sun, 06, Mar, 2022 at 09:51:57PM +, Adam D. Barratt spoke thus.. > - March 19th (means freezing next weekend, so not ideal) > - March 26th > - April 2nd > - April 9th > I can currently do any of those but it currently looks like March 26th has the biggest availability overlap (unless I missed an email). Mark -- Mark Hymers
Re: 11.2 planning
On Tue, 23, Nov, 2021 at 08:12:11PM +, Adam D. Barratt spoke thus.. > Hi, > > It's (a little past) time that we organised the next point release. As > an "every other" release, this time will only be for stable. > > Any of the first three weekends of December would work for me, although > the 4th is my least preferred as it means freezing over the coming > weekend and I'm not sure if I'll have time to do a fair job of dealing > with things before that. > > tl;dr, suggested dates: > > December 4th [least preferable for me] > December 11th > December 18th I can do the 11th or 18th. Mark -- Mark Hymers signature.asc Description: PGP signature
Re: 10.10 planning
On Sun, 30, May, 2021 at 05:50:09PM +0100, Steve McIntyre spoke thus.. > >Saturday June 12th > >Saturday June 19th > >Saturday June 26th 19th is best for me. Thanks, Mark -- Mark Hymers
Re: Finding a tentative bullseye release date
On Wed, 21, Apr, 2021 at 09:19:17PM +0200, Paul Gevers spoke thus.. > I've seen replies from Steve for CD, from Donald for Press and Cyril for > d-i. Can you please let us know if/when you're available? > May 1 CD, Press > May 8 CD, Press > May 15 CD > May 22 CD, Press > May 29 (CD) > > [d-i: the later the better] > > Seems like our current best option is May 22 if you can make it. I can help out with ftp-master foo on any of those. Mark -- Mark Hymers signature.asc Description: PGP signature
Re: Please dak copy-installer 20210415
On Thu, 15, Apr, 2021 at 04:21:40AM +0200, Cyril Brulebois spoke thus.. > Hi, > > FTP Masters, please sync the installer from sid to testing, as it seems > to be Installed for all release architectures (9 total): > > dak copy-installer 20210415 > > (Release team: FYI, I've urgented it.) Done, Mark -- Mark Hymers signature.asc Description: PGP signature
Re: 10.9 planning
On Mon, 15, Mar, 2021 at 12:33:15PM +, Adam D. Barratt spoke thus.. > Please could you confirm your availability, and any preferences, for > the following: > > - March 27th > - April 3rd > - April 10th I can do any of those for ftp, but would prefer to avoid the 10th April as well (which is convenient) Mark -- Mark Hymers
Re: 10.8 planning
On Sat, 16, Jan, 2021 at 02:38:13PM +, Adam D. Barratt spoke thus.. > Hi, > > It's that time again, when we should get 10.8 out. > > Please could you confirm your availability, and any preferences, for > the following: > > - January 30th (would mean we would have to freeze next weekend, so a > bit tight) > - February 6th > > My personal preference would be the 6th. I can do either for ftp. Thanks, Mark -- Mark Hymers signature.asc Description: PGP signature
Re: 10.7 planning
On Fri, 30, Oct, 2020 at 07:10:20PM +, Adam D. Barratt spoke thus.. > Hi, > > In an attempt to be slightly more efficient than usual at planning a > point release... it's about a month since 10.6, so let's start looking > at dates for 10.7. > > Please could you confirm your availability, and any preferences, for > the following: > > - November 21st > - November 28th > - December 5th I can do any of those for ftp. Thanks, Mark -- Mark Hymers
Re: 10.6 planning
On Wed, 09, Sep, 2020 at 07:24:06PM +0100, Adam D. Barratt spoke thus.. > - September 26/27 > - October 3/4 I can do either of those for ftp-team. I have a slight preference for Sept 26/27th but it's only slight. Thanks, Mark -- Mark Hymers
Re: stretch EOL point release (9.13) and 10.5 planning
On Sat, 18, Jul, 2020 at 10:12:41PM +0100, Adam D. Barratt spoke thus.. > Next weekend is probably a little too soon - I'd at least like to not > jump straight back into freezing - but how about one of: > > - August 1st/2nd Hu, 1st is definitely better for me than the 8th for ftp-side. Thanks, Mark -- Mark Hymers
Re: stretch EOL point release (9.13) and 10.5 planning
On Mon, 15, Jun, 2020 at 05:44:54PM +0100, Adam D. Barratt spoke thus.. > - July 11/12 > - July 18/19 I'm happy to do either of these for ftp. Thanks, Mark -- Mark Hymers signature.asc Description: PGP signature
Re: 10.4 planning
> - April 25th > - May 2nd > - May 9th I can currently do any of the above for ftp-team. Thanks, Mark -- Mark Hymers
Re: Planning 10.3 and 9.12
On Mon, 06, Jan, 2020 at 09:42:29PM +, Adam D. Barratt spoke thus.. > Hi, > > - January 25th > - February 1st > - February 8th > - February 15th Hi, I can do any of the above. Happy to do both on one day if it's easier for others. Thanks, Mark -- Mark Hymers signature.asc Description: PGP signature
Re: Scheduling 10.1 and maybe 9.10
On Sat, 27, Jul, 2019 at 08:21:57PM -0300, Jonathan Wiltshire spoke thus.. > On Sat, Jul 20, 2019 at 08:36:30PM -0300, Jonathan Wiltshire wrote: > > On Sun, Jul 14, 2019 at 07:35:01PM +0100, Jonathan Wiltshire wrote: > > > - Auguest 31st > > > - September 7th > > > > These look like the two options so far. Any other takers? > > I think we're just awaiting FTP masters now - I'd like to get this nailed > down as soon as we can so I can plan the pulses for 10.2 onwards please. I can do either of those. Thanks, Mark -- Mark Hymers signature.asc Description: PGP signature
Re: Scheduling 9.6
On Sat, 06, Oct, 2018 at 05:24:47PM +0100, Adam D. Barratt spoke thus.. > - October 20th (means freezing next weekend) > - October 27th > - November 3rd > - November 10th If no-one else from ftp- is available, I can do the 27th, 3rd or 10th; preferably starting as early in the morning as possible. Thanks, Mark -- Mark Hymers "Everyone is entitled to be stupid but some abuse the privilege." Unknown signature.asc Description: PGP signature
Re: Scheduling 9.5
On Mon, 14, May, 2018 at 06:19:00PM +0100, Jonathan Wiltshire spoke thus.. > Hi, > > We're due a point release any day now. Please indicate your availablility > out of: > > - May 26th (meaning freeze this coming weekend, which might be a big ask) > - Jun 2nd (which may require an unusual SRM) > - Jun 9th (getting quite a way out of cadence, but maybe that can't be >helped) If I'm needed as an ftp-person again, I can do any of the above. Mark -- Mark Hymers Ganneff: I'm confident in your ability to create a flamewar. Extremedura QA/i18n meeting 2008
Re: More frequent debian-installer uploads and CD releases?
On Mon, 14, Oct, 2013 at 12:35:12AM +0200, Cyril Brulebois spoke thus.. I think it would be nice if we could be able to perform something like an upload a month during the whole release cycle. History shows that we sometimes needed to fix a few things and re-upload before performing a release (with CD images), but we could probably stay below 20 uploads a year even with such last minute fix-ups when a CD release is planned / needed. From an ftp point of view, I don't see a problem with that at all. It's relatively small churn compared to the archive as a whole. Cheers, Mark -- Mark Hymers mhy at debian dot org ++?++ Out of Cheese Error. Redo From Start. Interesting Times, Terry Pratchett -- 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/20131015065748.ga7...@hymers.org.uk
Bug#725397: preseed: e/n/i is overwritten after late_command
Package: preseed Version: 1.58 Severity: normal Tags: d-i Hi, I'm not sure if this is a bug in preseed or netcfg. When doing preseed wheezy installs, we came across an issue using late_command. netcfg now has a 55netcfg-copy-config in finish-install.d which unconditionally overwrites /etc/network/interfaces. This makes it impossible for the late_command to ensure that this file is correct. I'm not sure if the netcfg script should be moved earlier, the late_command script later or whether netcfg should just check for the existance of e/n/i and not overwrite it if it's been put in place. This caused us a few issues during initial boot for various automated installs until we worked around it with a local hack of running an extra script from a local udeb after 55netcfg-copy-config. Thanks, Mark -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=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/20131005095259.10085.28143.report...@mhy-sid.ynic.york.ac.uk
Re: Please dak copy-installer 20130415, urgent debian-installer/20130415
On Tue, 16, Apr, 2013 at 07:57:07AM +0200, Cyril Brulebois spoke thus.. Hi folks, short time no see! ftpmasters: please dak copy-installer 20130415 Done, Mark -- Mark Hymers mhy at debian dot org 'I regret nothing?' That's not a song, that's an idiots charter. Andy Hamilton, Old Harry's Game -- 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/20130416072514.ga16...@hymers.org.uk
Re: Please dak copy-installer, urgent debian-installer
On Sat, 13, Apr, 2013 at 04:27:03PM +0200, Cyril Brulebois spoke thus.. Hi folks, long time no see! ftpmasters: please dak copy-installer 20130412 Done, Mark -- Mark Hymers mhy at debian dot org That's why the good die young; it's because Death can't be bothered to check the paperwork. Andy Hamilton, Old Harry's Game -- 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/20130413165734.ga31...@hymers.org.uk
Re: Please dak copy-installer, urgent debian-installer
On Wed, 13, Feb, 2013 at 07:36:25PM +0100, Niels Thykier spoke thus.. On 2013-02-13 19:25, Cyril Brulebois wrote: Hi, this is this time of the release again! ftpmasters: please dak copy-installer 20130211 Urgented. [ ] dak@franck:/home/mhy$ dak copy-installer 20130211 Will copy installer version 20130211 from suite unstable to testing. Architectures to copy: i386, powerpc, mipsel, ia64, amd64, armel, s390x, kfreebsd-i386, mips, armhf, sparc, kfreebsd-amd64, s390 Architectures to skip: Installer has been copied successfully. Mark -- Mark Hymers mhy at debian dot org ++?++ Out of Cheese Error. Redo From Start. Interesting Times, Terry Pratchett -- 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/20130213230405.ga30...@hymers.org.uk
Re: Thank you so much for breaking d-i!
On Sun, 15, Jul, 2012 at 03:09:46PM +0200, Cyril Brulebois spoke thus.. Marco d'Itri m...@linux.it (15/07/2012): WTF are you talking about? Obviously: #681285 At the release / boot team's request, the -udeb and source has been placed back in unstable for now. I've also re-opened the removal bug. Once d-i is properly transitioned to kmod, please let us know and we'll remove it from unstable again. Thanks, Mark -- Mark Hymers mhy at debian dot org ++?++ Out of Cheese Error. Redo From Start. Interesting Times, Terry Pratchett -- 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/20120715140330.ga9...@hymers.org.uk
Re: Finalizing beta1: please dak copy-installer, urgent d-i, build images
On Sat, 14, Jul, 2012 at 02:15:36AM +0200, Cyril Brulebois spoke thus.. Hi ftpmasters, release team, cd team, please respectively, do: - dak copy-installer Done. I'll delete the older d-i from testing in a few days time unless anyone objects. Mark -- Mark Hymers mhy at debian dot org I once absent-mindedly ordered Three Mile Island dressing in a restaurant and, with great presence of mind, they brought Thousand Island Dressing and a bottle of chili sauce. Terry Pratchett, alt.fan.pratchett -- 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/20120714174250.ga25...@hymers.org.uk
Re: Squeeze point release (6.0.5)
On Wed, 25, Apr, 2012 at 09:32:51PM +0100, Steve McIntyre spoke thus.. That will help, but then the issue is more a problem with downloading the images. I've got a full mirror at home, which helps immensely with jigdo downloads. I can try and arrange to have a full local mirror at the BSP which I can sync at work on the Friday beforehand if that'll help. Mark -- Mark Hymers mhy at debian dot org I've had people claim that they actually make the sun rise rise every morning. I've offered to test them by shooting them. So far all these people have not responded to my endeavours. James Randi on BBCi Live Chat -- 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/20120426112218.ga30...@hymers.org.uk
Re: d-i changes
On Thu, 28, Jul, 2011 at 04:50:00PM +0200, Philipp Kern spoke thus.. - GPL compliance: If d-i starts to use Built-Using, it should be safe from a compliance point of view. I don't know what happens if you refer a package that is no longer in the pool. I presume it'd get rejected. I've got some more notes on this D-I stuff but I need to write them up. For now, I'll just confirm that you're correct and the upload would be rejected. Mark -- Mark Hymers mhy at debian dot org The older I grow, the more I distrust the familiar doctrine that age brings wisdom. H.L. Mencken -- 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/20110728152953.ga10...@hymers.org.uk
Re: d-i decruft in sid
On Sun, 10, Apr, 2011 at 03:41:40PM -0300, Otavio Salvador spoke thus.. Can we decruft some of them? The more the better. This is sid/ right? If so, I don't really see why we need to keep version older than the last released, ie 20110106 (+b1). I fully agree with Christian; we just need to have the current release on sid and we really don't need to have the old ones. Ok, done. mhy@franck:/srv/ftp-master.debian.org/ftp/dists/unstable/main$ ls installer-* -l installer-alpha: total 4 drwxr-xr-x 3 dak debadmin 4096 Jan 23 2009 20090123 lrwxrwxrwx 1 dak debadmin8 Jan 23 2009 current - 20090123 installer-amd64: total 4 drwxr-xr-x 3 dak debadmin 4096 Jan 17 13:24 20110106+b1 lrwxrwxrwx 1 dak debadmin 11 Jan 17 17:32 current - 20110106+b1 installer-armel: total 4 drwxr-xr-x 3 dak debadmin 4096 Jan 17 15:17 20110106+b1 lrwxrwxrwx 1 dak debadmin 11 Jan 17 17:02 current - 20110106+b1 installer-hppa: total 4 drwxr-xr-x 3 dak debadmin 4096 Jan 17 13:59 20110106+b1 lrwxrwxrwx 1 dak debadmin 11 Jan 17 16:46 current - 20110106+b1 installer-i386: total 4 drwxr-xr-x 3 dak debadmin 4096 Jan 17 13:23 20110106+b1 lrwxrwxrwx 1 dak debadmin 11 Jan 17 17:32 current - 20110106+b1 installer-ia64: total 4 drwxr-xr-x 3 dak debadmin 4096 Jan 17 13:15 20110106+b1 lrwxrwxrwx 1 dak debadmin 11 Jan 18 09:32 current - 20110106+b1 installer-kfreebsd-amd64: total 4 drwxr-xr-x 3 dak debadmin 4096 Jan 17 13:18 20110106+b1 lrwxrwxrwx 1 dak debadmin 11 Jan 17 14:49 current - 20110106+b1 installer-kfreebsd-i386: total 4 drwxr-xr-x 3 dak debadmin 4096 Jan 17 13:33 20110106+b1 lrwxrwxrwx 1 dak debadmin 11 Jan 17 14:49 current - 20110106+b1 installer-mips: total 4 drwxr-xr-x 3 dak debadmin 4096 Jan 17 15:02 20110106+b1 lrwxrwxrwx 1 dak debadmin 11 Jan 18 09:32 current - 20110106+b1 installer-mipsel: total 4 drwxr-xr-x 3 dak debadmin 4096 Jan 17 13:58 20110106+b1 lrwxrwxrwx 1 dak debadmin 11 Jan 18 09:32 current - 20110106+b1 installer-powerpc: total 4 drwxr-xr-x 3 dak debadmin 4096 Jan 17 13:38 20110106+b1 lrwxrwxrwx 1 dak debadmin 11 Jan 17 15:17 current - 20110106+b1 installer-s390: total 4 drwxr-xr-x 3 dak debadmin 4096 Jan 17 13:15 20110106+b1 lrwxrwxrwx 1 dak debadmin 11 Jan 17 15:02 current - 20110106+b1 installer-sparc: total 4 drwxr-xr-x 3 dak debadmin 4096 Jan 17 13:43 20110106+b1 lrwxrwxrwx 1 dak debadmin 11 Jan 17 14:49 current - 20110106+b1 Thanks, Mark -- Mark Hymers mhy at debian dot org We have three realistic alternatives: (1) Sit here and get blown up, (2) Stand here and get blown up, (3) Jump up and down, shout at me for not being able to think of anything, then get blown up. Holly, Red Dwarf Series III - Bodyswap -- 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/20110411151757.ga14...@hymers.org.uk
Re: d-i decruft in sid
On Sun, 27, Mar, 2011 at 08:42:38AM +0200, Christian PERRIER spoke thus.. This is sid/ right? Yeah. If so, I don't really see why we need to keep version older than the last released, ie 20110106 (+b1). That's the version in testing so that makes sense. I don't see the value added in keeping old D-I releases as the archive is not an historical archive. Agreed, and they will still be on snapshot anyways. So, I'd say keep 20110106+b1 when it's here and the latest one when it is not). Ok, I'll wait for confirmation from other -boot people but as soon as I hear back, I'll clean all but the latest images from unstable for each arch. Mark -- Mark Hymers mhy at debian dot org I'm so gorgeous, there's a six month waiting list for birds to suddenly appear, every time I am near! Cat, Red Dwarf Series VIII - Back in the Red -- 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/20110327072404.ga5...@hymers.org.uk
Bug#619700: Please consider using the build-essential package instead of Build-Essental: yes
Package: debootstrap
Version: 1.0.29
Severity: wishlist
Tags: patch
Hi,
This bug is related to the mail at
http://lists.debian.org/debian-devel/2011/03/msg00978.html
which discusses the existance of both the build-essential package and
the field. Quick summary: we think that in the longer term (i.e. after
squeeze is dropped from the main archive at the ends of its security
support) the field should go and the package should be the definition
(it already is de-facto for most things including cdebootstrap).
On Sat, 26, Mar, 2011 at 10:53:07AM +0100, Joerg Jaspert spoke thus..
As far as we know currently the main user of this field seems to be
debootstrap in its buildd variant mode.
I just went and checked that changing to using the package wouldn't make
any difference (trivial patch at
http://git.debian.org/?p=users/mhy/debootstrap.git;a=commitdiff;h=782b75f69f383e4d0e6f8909c9a69844c9f769af
)
Using lenny squeeze wheezy and sid, I found no differences to dpkg
--get-selections (on amd64) before and after the above patch (using
debootstrap --variant=buildd ${d} ${d} http://mirror/debian/
)
Thanks,
Mark
--
Mark Hymers mhy at debian dot org
But Yossarian *still* didn't understand either how Milo could buy eggs
in Malta for seven cents apiece and sell them at a profit in Pianosa
for five cents.
Catch 22, Joseph Heller
signature.asc
Description: Digital signature
Bug#458663: re debootstrap and bz2 etc
On Sun, 15, Nov, 2009 at 02:40:20PM -0500, Joey Hess spoke thus.. Another reason to avoid bz2 and other more esoteric compressors in debs uded by debootstrap is that debootstrap is run on systems other than d-i and debian. When debootstrap is used on a busybox based embedded system, bzip2 will likely not be available. When debootstrap is used on some old crufty[1] distribution, lzma and xz are likely not available. Adding these to the system before running debootstrap could be significant work. Recommend this bug is cloned to lintian, and lintian has checks added for Priority: required and above. Then the ftpmasters could even autoreject based on those checks (assuming the debs' built-in Priority info is accurate). Just for the record, at the moment dak only allows data.tar.gz and data.tar.bz2 (although I had to check that myself in the source code, I've got documenting what is and isn't supported someone more sane on my TODO list). As I said on -devel recently, the data.tar.bz2 support in dak seems to date from 2005, so it's been around for a while. lzma/xz on the other hand hasn't even been asked for yet as far as I know. Mark -- Mark Hymers mhy at debian dot org That's why the good die young; it's because Death can't be bothered to check the paperwork. Andy Hamilton, Old Harry's Game -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Meeting(s) at FOSDEM
In gmane.linux.debian.devel.kernel, you wrote: On Mon, Feb 09, 2009 at 06:30:00PM -0200, Otavio Salvador wrote: Steve McIntyre st...@einval.com writes: ... The main focus of the meeting was how d-i builds and releases work, and I think we made quite some progress on that. There are a few changes that we think should be made that will help a great deal in building, publishing and releasing d-i. I'm not posting any of the details here just yet because my memory fails me... :-) ... Please let me know those details as soon as possible :-) Oh, of course. :-) My beer-addled memory is not as reliable as it used to be, so I'm hoping that Mark's notes are more reliable. mhy: ping! Ok, here are my notes from that meeting. I'm sure people will correct me when I make mistakes / omissions. Unfortunately, my notes aren't anywhere near as copious as I'd like so if people could jump in, it'd be helpful. People present: broonie, enrico, fjp, Maulkin, mhy, Sledge, sgran, Kinnison, kyllikki, Womble2 Issues Discussed: - Kernel: * The issue of linux-modules-extra binaries having been built using sources which are not referenced within dak (and hence not guaranteed to be kept around for the right length of time was discussed). This was also discussed under D-I Builds [0] D-I Builds: * Some facts about D-I builds were clarified by fjp: * Pulls in d-i source (installer/) * Pull in udebs * Daily builds take udebs from unstable * RC builds take udebs from testing * debian/rules performs a testing build * manual builds using installer uses unstable (?) * D-I builds need to be run as root; fakeroot doesn't suffice (? would it be possible/desirable to use sudo to do builds on a per-package basis?) * D-I changes come from * Installer build system * debs * cd build scripts * Metadata generation * How D-I can declare an interest in certain debs/udebs to assist the release team? Could a file be produced listing the relevant packages? * How we can ensure that source is available for everything in D-I images? [0] * Virtual d-i package for Depends to prevent migration of 'bad stuff' to testing? * debian.org daily builds * Would it be possible / feasible to move the daily builds to the normal autobuilder network? [0] This led to further discussion culminating in a proposal for two new fields in .changes files. This is not a full specification or proposal, which is yet to be fully written: * Built-Using-Binary: * Built-Using-Source: These fields would be placed in a .changes file of a single architecture binary upload (rationale for not putting them in the DEBIAN/control file; we want to avoid bloating udebs and also allow the use of these fields for non-package uploads, such as the debian-installer tarballs which may not contain a control file). They must be specified with a strict versioned Depends; e.g. Built-Using-Binary: foo (= 1.2.1-3). At upload time the archive will check that the version specified is known, in the case of the Built-Using-Binary field resolve it to its source package/version and store a reference that the binary packages uploaded were built using that source package/version. The archive will then refuse to remove source packages from the pool whilst any existing binary still references them. PS - I have to say that having looked at this and thought again, I'm fairly sure that the .changes file is fundamentally the wrong place for this and that we need to discuss it further. Normal packages should just put it in control and we should come up with some other mechanism (maybe some form of extra control file which is uploaded) for things which go through byhand (such as d-i tarballs) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Meeting(s) at FOSDEM
On Thu, 05, Feb, 2009 at 12:30:46PM +, Steve McIntyre spoke thus.. Apologies for the massive cross-posting, but I'm trying to arrange some discussions between the various teams, or at least those members who will be at FOSDEM. Topics I'd like us to talk about include: 1. how the d-i daily builds are done and distributed 2. how the needs of the kernel d-i teams can better be reconciled I'm guessing that quite a number of people may be interested in these, and in other topics. Is there anything else I'm missing that you would like to discuss? Then: when and where would be a good time to meet up? Hello? Anyone? Hi, I agree that it'd be a good idea to meet up and I'll make sure I'm there wearing my ftpteam hat (note, not ftpmaster so I can't finally agree to anything, but I'm willing to put any work in on the ftp side which is needed). I'm around all weekend up until Sunday afternoon at about 3, so whatever works for everyone else will be fine by me. Cheers, Mark -- Mark Hymers mhy at debian dot org 'I regret nothing?' That's not a song, that's an idiots charter. Andy Hamilton, Old Harry's Game signature.asc Description: Digital signature
Re: Source compliance for D-I build dependencies: follow-up
On Fri, 16, Jan, 2009 at 12:21:14PM +0100, Adeodato Simó spoke thus.. Btw, I don't know if it'd be a viable approach or not, but I'll mention it nevertheless: I wonder if for squeeze we should do the debian-installer uploads to t-p-u instead of unstable. We would still have to ensure source compliance, by copying if an update in testing must happen, but we would stop caring if unstable and testing are in sync. The other option, which I've been thinking about for a while, would be to allow binary packages (deb or udeb) to declare a field such as: Source-Depends: foo (= 1.2-1) We could then teach dak to hang on to source packages for as long as they're still referenced by any binary package, thus making all this much easier. That's a post-lenny discussion though, but possibly worth considering on another list somewhere. Mark -- Mark Hymers mhy at debian dot org I've had people claim that they actually make the sun rise rise every morning. I've offered to test them by shooting them. So far all these people have not responded to my endeavours. James Randi on BBCi Live Chat -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#494532: libparted1.7-udeb on armel
On Fri, 15, Aug, 2008 at 10:18:19PM +0100, Adeodato Simó spoke thus.. I think a good first try would be uploading the parted from stable (1.7.1-5.1) with increased version in the changelog to 1.7.1-5.1+b1, with armel binaries if possible. Why can't we just manually re-insert the armel binaries from the morgue? [EMAIL PROTECTED]:/srv/ftp.debian.org/morgue$ find ./ -name *parted*1.7.1-5* ./pool/2008-08-09/libparted1.7-1_1.7.1-5.1_armel.deb ./pool/2008-08-09/parted-udeb_1.7.1-5.1_armel.udeb ./pool/2008-08-09/libparted1.7-udeb_1.7.1-5.1_armel.udeb ./pool/2008-08-09/parted_1.7.1-5.1_armel.deb ./pool/2008-08-09/libparted1.7-dbg_1.7.1-5.1_armel.deb ./pool/2008-08-09/libparted1.7-dev_1.7.1-5.1_armel.deb Mark -- Mark Hymers mhy at debian dot org I got off at Durham... and fell in love with it instantly. Why, it's wonderful - a perfect little city. If you have never been to Durham, go there at once. Take my car. It's wonderful. Notes from a Small Island, Bill Bryson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494532: libparted1.7-udeb on armel
On Fri, 15, Aug, 2008 at 10:54:31PM +0100, Adeodato Simó spoke thus.. ./pool/2008-08-09/libparted1.7-udeb_1.7.1-5.1_armel.udeb As discussed, this should be back in testing on the next dinstall run. Mark -- Mark Hymers mhy at debian dot org Oh, this is John Reid who is 'Cabinet Bruiser' which just means that he's a bit squat, ugly and unpleasant and therefore gets to be called a 'Bruiser'. Jeremy Hardy, The News Quiz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#270136: patch for partman_server
reassign 270136 partman-base
tag 270136 + patch
thanks
Patch attached to make this behaviour a bit more robust (I hope).
Mark
--
Mark Hymers [EMAIL PROTECTED]
But Yossarian *still* didn't understand either how Milo could buy eggs
in Malta for seven cents apiece and sell them at a profit in Pianosa
for five cents.
Catch 22, Joseph Heller
Index: debian/changelog
===
--- debian/changelog(revision 37382)
+++ debian/changelog(working copy)
@@ -1,3 +1,9 @@
+partman-base (83) unstable; urgency=low
+
+ * Add more robust pid file and fifo handling. Closes: #270136.
+
+ -- Mark Hymers [EMAIL PROTECTED] Thu, 18 May 2006 03:37:26 +0100
+
partman-base (82) unstable; urgency=low
[ Frans Pop ]
Index: definitions.sh
===
--- definitions.sh (revision 37382)
+++ definitions.sh (working copy)
@@ -255,8 +255,6 @@
open_infifo
write_line QUIT
close_infifo
-
-rm /var/run/parted_server.pid
}
# Must call stop_parted_server before calling this.
Index: init.d/parted
===
--- init.d/parted (revision 37382)
+++ init.d/parted (working copy)
@@ -5,12 +5,13 @@
. /lib/partman/definitions.sh
if [ ! -f /var/run/parted_server.pid ]; then
-mknod /var/lib/partman/infifo p /dev/null 2/dev/null || true
-mknod /var/lib/partman/outfifo p /dev/null 2/dev/null || true
-mknod /var/lib/partman/stopfifo p /dev/null 2/dev/null || true
[ -d /var/run ] || mkdir /var/run
-parted_server
-echo $! /var/run/parted_server.pid
+parted_server
+RET=$?
+if [ $RET != 0 ]; then
+# TODO: How do we signal we couldn't start partman_server properly?
+exit $RET
+fi
if [ -d /var/lib/partman/old_devices ]; then
rm -rf /var/lib/partman/old_devices
Index: parted_server.c
===
--- parted_server.c (revision 37382)
+++ parted_server.c (working copy)
@@ -8,11 +8,20 @@
#include errno.h
#include stdbool.h
#include ctype.h
+#include signal.h
/**
Logging
**/
+/* This file is used as pid-file. */
+char pidfile_name[] = /var/run/parted_server.pid;
+
+/* These are the communication fifos */
+char infifo_name[] = /var/lib/partman/infifo;
+char outfifo_name[] = /var/lib/partman/outfifo;
+char stopfifo_name[] = /var/lib/partman/stopfifo;
+
/* This file is used as log-file. */
char logfile_name[] = /var/log/partman;
@@ -2053,6 +2062,91 @@
activate_exception_handler();
}
+void
+make_fifo(char* name)
+{
+int status;
+status = mkfifo(name, 0x644);
+if ((status != 0))
+if (errno != EEXIST) {
+perror(Cannot create FIFO);
+exit(252);
+}
+}
+
+void
+make_fifos()
+{
+make_fifo(infifo_name);
+make_fifo(outfifo_name);
+make_fifo(stopfifo_name);
+}
+
+int
+write_pid_file()
+{
+FILE *fd;
+int status;
+pid_t oldpid;
+if ((fd = fopen(pidfile_name, a+)) == NULL)
+return -1;
+
+if (!feof(fd)) {
+status = fscanf(fd, %d, oldpid);
+if (status != 0) {
+// If kill(oldpid, 0) == 0 the process is still alive
+// so we abort
+if (kill(oldpid, 0) == 0) {
+fprintf(stderr, Not starting: process %d
still exists\n, oldpid);
+fclose(fd);
+exit(250);
+}
+}
+// Truncate the pid file and continue
+freopen(pidfile_name, w, fd);
+}
+
+fprintf(fd, %d, (int)(getpid()));
+fclose(fd);
+return 0;
+}
+
+void
+cleanup_and_die()
+{
+if (unlink(pidfile_name) != 0)
+perror(Cannot unlink pid file);
+if (unlink(infifo_name) != 0)
+perror(Cannot unlink input FIFO);
+if (unlink(outfifo_name) != 0)
+perror(Cannot unlink output FIFO);
+if (unlink(stopfifo_name) != 0)
+perror(Cannot unlink stop FIFO);
+}
+
+void
+prnt_sig_hdlr(int signal)
+{
+int status;
+switch(signal) {
+// SIGUSR1 signals that child is ready to take
+// requests (i.e. has finished initialisation)
+case SIGUSR1:
+exit(0);
+break;
+// We'll only get SIGCHLD if our child has pre-deceased us
+// In this case we should exit with its error code
+case SIGCHLD:
+if (waitpid(-1, status, WNOHANG) 0
Bug#270136: patch for partman_server
On Thu, 18, May, 2006 at 12:13:23AM -0500, Joey Hess spoke thus.. Mark Hymers wrote: Patch attached to make this behaviour a bit more robust (I hope). Sweet. Patch looks correct, did you get a chance to test it? Yeah, Steve Gran booted it on his thinkpad qemu session and it seems to work fine. Buyer beware :-) Mark -- Mark Hymers [EMAIL PROTECTED] That's why the good die young; it's because Death can't be bothered to check the paperwork. Andy Hamilton, Old Harry's Game signature.asc Description: Digital signature
Bug#259903: Debian bug #259903
Regarding your installation report for Debian, I'm told that yaboot has the options install and expert but not install-safe. Could you please confirm exactly what you did at the install prompt? Thanks for your installation report. Mark Hymers -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
