Unieke geschenk voor groot en klein
Deze email nieuwsbrief werd in grafisch HTML formaat verzonden. Als u deze tekstversie ziet, verkiest uw email programma "gewone tekst" emails. U kan de originele nieuwsbrief online bekijken: http://sendmail.itdude.be/zYPbh2 View this email online ( http://sendmail.itdude.be/zYPbh2 ) Bezoek webshop ( http://www.wildandsoftwebshop.com/ ) HET UNIEKE GESCHENK VOOR GROOT EN KLEIN Wild & Soft is een Belgisch bedrijf dat de zachtste woonaccessoires ter wereld creéert. De Wild & Soft dierenkoppen zijn er voor de allerkleinsten, maar ook aan de volwassenen werd gedacht. Bezoek onze webshop ( http://www.wildandsoftwebshop.com/ ) WILLIAM William is van nature wat tegendraads. Met zijn tartan uitzicht schept hij ongetwijfeld een unieke sfeer in het interieur. De Schotse ruit is al eeuwen populair, Reindeer William brengt deze nu op een ludieke manier binnen in de woning. Bezoek William ( http://www.wildandsoftwebshop.com/wildandsoft/abstract-line/william/ ) CARLOS Op zoek naar een fris en vrolijk item om jouw interieur net dat tikkeltje meer te geven? Rhino Carlos voldoet aan al deze eisen. Zijn vorm is pure fun en zijn fluwelen look zorgt voor een intieme, maar toch speelse touch. De kleur is origineel en zorgt steeds voor een zomerse sfeer in huis. Bezoek Carlos ( http://www.wildandsoftwebshop.com/wildandsoft/abstract-line/carlos/ ) BASILE Hey ik ben Basile de ijsbeer. Ik ben groot, sterk, maar vooral heel zacht. Mijn dikke vacht beschermt mij tegen de kou. Maar ik ben er zeker van dat jouw knuffels mij ook zullen verwarmen. Ik vind het fantastisch om me te laten glijden op mijn buik en ben dan ook een echte speelvogel. Maar ik kan ook stilletjes luisteren naar al jouw avonturen. En wees gerust…jouw diepste geheimen zijn veilig bij mij. Bezoek Basile ( http://www.wildandsoftwebshop.com/wildandsoft/plushen-lijn/basile/ ) CESAR Ik ben Cesar en men noemt mij ook wel ‘King of the jungle’. Hoewel ik het leuk vind om de baas te spelen, ben ik heel charmant. Wat je niet mag vergeten is om af en toe door mijn manen te wrijven, want ik ben heel trots op mijn gouden haardos. Ik ben heel sterk, moedig en wijs. Samen kunnen we de wereld aan! Bezoek Cesar ( http://www.wildandsoftwebshop.com/wildandsoft/plushen-lijn/cesar/ ) WWW.WILDANDSOFTWEBSHOP.COM ( HTTP://WWW.WILDANDSOFTWEBSHOP.COM/ ) Copyright 2014 wildandsoftwebshop.com ( http://www.wildandsoftwebshop.com ), All rights reserved. Not interested in our newsletter? unsubscribe ( http://sendmail.itdude.be/ugjwmyejgsghjeeqegyhbggujbejq ).
Re: Bug#767999: base-files: fails to install with pre-jessie debootstrap
Control: tag -1 -patch Control: reassign -1 dpkg 1.17.21 Control: affects -1 debootstrap [ Context: debootstrap/wheezy is now unable to debootstrap either jessie or sid. ] Cyril Brulebois (2014-11-05): > > I'm not calling Adam's proposal insane. His proposal is just wrong. > > What I was calling insane is the fact that we are still having this > > discussion instead of making a debootstrap upload for stable. > > The situation could probably have started (and/or continued) in a better > way if there would have been less fingerpointing/shooting the > messenger/whatever you call it. > > But, from where I stand, several developers were actually checking facts > after I cherry-picked the patch in to the stable branch, and I decided > to wait and see where the situation was going. Apparently there are > several views on the matter, and without commenting on their respective > relevance, I'd like to emphasize several things: > - Developers have limited free time. > - Developers might be getting ready for the imminent freeze. > - Uploading to stable means making sure the fix is right, rather than >uploading hastily. > - Uploads to stable don't appear magically on users' systems a few >hours later; it takes a point release or users' having configured >s-p-u in their sources.list; so I don't think any haste (see previous >point) would help anyway. > - Uploads to stable have to be reviewed by release team members, who >might also be busy dealing with a flood of freeze-related requests at >the moment. > > So I'd suggest taking a step back, reassigning/forcemerging reports when > you have time for that, and waiting for some feedback; probably from me. Tests performed on an amd64 host running wheezy, debootstrapping amd64. Well I bisected the archive and the last debootstrapable jessie release was at 20141102T221202Z; looking at the set of updated packages between that one and the next one, it looks like… dpkg got updated from 1.17.13 to 1.17.21. And unsurprisingly reverting current jessie to dpkg 1.17.13 makes debootstrap work again. A few weeks or even days before the freeze doesn't quite seem to be the right time to introduce (not so) subtle changes in dpkg. Reassigning it to dpkg for now; and cc-ing the release team because of things like the #768346 unblock request. Mraw, KiBi. signature.asc Description: Digital signature
Re: Bug#767999: base-files: fails to install with pre-jessie debootstrap
Control: severity -1 serious Control: retitle -1 dpkg: Correct fix breaks bogus assumptions in old debootstrap On Fri, 2014-11-07 at 02:33:48 +0100, Cyril Brulebois wrote: > Cyril Brulebois (2014-11-05): > > But, from where I stand, several developers were actually checking facts > > after I cherry-picked the patch in to the stable branch, and I decided > > to wait and see where the situation was going. Apparently there are > > several views on the matter, and without commenting on their respective > > relevance, I'd like to emphasize several things: > > - Developers have limited free time. > > - Developers might be getting ready for the imminent freeze. > > - Uploading to stable means making sure the fix is right, rather than > >uploading hastily. > > - Uploads to stable don't appear magically on users' systems a few > >hours later; it takes a point release or users' having configured > >s-p-u in their sources.list; so I don't think any haste (see previous > >point) would help anyway. > > - Uploads to stable have to be reviewed by release team members, who > >might also be busy dealing with a flood of freeze-related requests at > >the moment. > > Tests performed on an amd64 host running wheezy, debootstrapping amd64. > > Well I bisected the archive and the last debootstrapable jessie release > was at 20141102T221202Z; looking at the set of updated packages between > that one and the next one, it looks like… dpkg got updated from 1.17.13 > to 1.17.21. And unsurprisingly reverting current jessie to dpkg 1.17.13 > makes debootstrap work again. What's making the breakage in debootstrap surface is dpkg 1.17.20, commit 9ee62ecfc8937f24a82805a424564997042dd984. At least with my testing using a patched debootstrap, and using --foreign + --second-stage to inject a dpkg with the reverted commit. > A few weeks or even days before the freeze doesn't quite seem to be the > right time to introduce (not so) subtle changes in dpkg. (So we need to actually freeze months in advance of the freeze… right.) The above commit is a *correct* fix for a very old regression, to remove a bogus package queue dependency stage in dpkg. The breakage in debootstrap in older versions is due to incorrect assumptions, which where fixed correctly (not worked around, contrary to what is mentioned on its changelog) in 1.0.56. The change was: - x_core_install base-files base-passwd + x_core_install base-passwd + x_core_install base-files where debootstrap was expecting that dpkg run to process base-passwd first, even though it was passed last. This, on a call to dpkg using --force-depends, for essential packages that do not have any kind of dependency relationship between them, which makes any such assumption be based on something far beyond undefined behavior. > Reassigning it > to dpkg for now; and cc-ing the release team because of things like the > #768346 unblock request. I'm going to revert the commit above (only in 1.17.x, it will be kept in 1.18.x), because it is very minimal, just reintroduces again an unnecessary package queue stage, and such regression is acceptable if it makes buggy bootstrappers work again. But a fixed debootstrap (and maybe cdebootstrap if that fails too) should really be pushed to stable. Guillem -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141107073449.ga11...@gaara.hadrons.org
