Processed: found 1059050 in 1:1.36.1-9, found 1059050 in 1:1.35.0-4

Processing commands for cont...@bugs.debian.org: > found 1059050 1:1.36.1-9 Bug #1059050 {Done: Salvatore Bonaccorso } [src:busybox] busybox: CVE-2023-42363 Marked as found in versions busybox/1:1.36.1-9. > found 1059050 1:1.35.0-4 Bug #1059050 {Done: Salvatore Bonaccorso } [src:b

Bug#1076609: bullseye-pu: package gtk+3.0/3.24.24-4+deb11u4

|1 gtk/gtkmodules.c |9 + 4 files changed, 44 insertions(+), 7 deletions(-) diff -Nru gtk+3.0-3.24.24/debian/changelog gtk+3.0-3.24.24/debian/changelog --- gtk+3.0-3.24.24/debian/changelog 2023-02-24 19:07:01.0 + +++ gtk+3.0-3

Processed: tagging 1038918, tagging 1038759, tagging 1038954, found 1038887 in 1.16.0+dfsg-4, tagging 1038887 ...

onsole-setup: Build against xkb-data 2.38-2 needed Added tag(s) trixie and sid. > tags 1038954 + sid trixie Bug #1038954 [python3-pdbfixer] python3-pdbfixer depends on python3-simtk no longer built by src:openmm Added tag(s) trixie and sid. > found 1038887 1.16.0+dfsg-4 Bug #1038887 [src:

Re: Upcoming D-I Bookworm RC 4 and pseudo-RC 5

Hi, On 2023-06-03 08:07, Cyril Brulebois wrote: > Since there was good progress on the arm64 console thing (#1036952), and > considering the current results of the investigation as to where vt102 > comes from, and why arm64 isn't quite the deciding factor (a busybox > limitation instead), I'd be h

Re: Upcoming D-I Bookworm RC 4 and pseudo-RC 5

Cyril Brulebois, le sam. 03 juin 2023 20:07:05 +0200, a ecrit: > Unless specifically requested, I don't plan on including the first two > before Bookworm because we don't need it for release architectures. I > /think/ hurd-i386 gets somewhat released from unstable, so that > shouldn't matter… Yes.

Re: Upcoming D-I Bookworm RC 4 and pseudo-RC 5

Hi Holger, Holger Wansing (2023-06-03): > Cyril Brulebois wrote (Sat, 3 Jun 2023 20:07:05 +0200): > > At the moment I've spotted three uploads: > > - apt-setup (1:0.183), for ports architectures. > > - preseed (1.118), for Hurd, even if the changelog is not quite verbose > >about that part

Re: Upcoming D-I Bookworm RC 4 and pseudo-RC 5

Hi, Cyril Brulebois wrote (Sat, 3 Jun 2023 20:07:05 +0200): > At the moment I've spotted three uploads: > - apt-setup (1:0.183), for ports architectures. > - preseed (1.118), for Hurd, even if the changelog is not quite verbose >about that part… > - vte2.91 (0.70.5-1): new upstream (bugfix

Re: Upcoming D-I Bookworm RC 4 and pseudo-RC 5

Hi, Here's a quick update about my current plans regarding the installer and regarding debian-cd dry runs. (Trimming recipients; also, I'm using 12.0.0 below as I'm referring to the version identifier on the debian-cd side, but that's hopefully synonymous with Debian 12.0, i.e. the initial Bookw

Debian Installer Bookworm RC 4 release

The Debian Installer team[1] is pleased to announce the fourth release candidate of the installer for Debian 12 "Bookworm". Improvements in this release * cdebconf: - Improve banner display when the installer logo's width is smaller than the GTK window's w

Upcoming D-I Bookworm RC 4 and pseudo-RC 5

> > 1. https://lists.debian.org/debian-devel-announce/2023/04/msg7.html > > On the d-i side, we'll have a round of translation updates, along > with some last tweaks, before RC 4. We should be all done in a few hours. I might pick a last minute tasksel change as well (for lxqt);

Re: Upcoming D-I Bookworm RC 3 and RC 4

/04/msg7.html On the d-i side, we'll have a round of translation updates[2], along with some last tweaks, before RC 4. As far as I understand, at least at the moment, we aren't expecting a new linux upload before the release. But if the need arises, we should be able to deal with

Re: Bug#1029843: Missing symlinks for RPi 4 (to brcmfmac43455-sdio.raspberrypi,4-model-b.txt)

spaces > in "File: " or "Link: " lines in the WHENCE file: > > diederik@bagend:~/dev/kernel.org/linux-firmware$ grep -E "^Link: .* .* -> .*" > WHENCE > Link: brcm/brcmfmac43455-sdio.Raspberry\ Pi\ Foundation-Raspberry\ Pi\ 4\ > Model\ B.txt -&g

Re: Bug#1029843: Missing symlinks for RPi 4 (to brcmfmac43455-sdio.raspberrypi,4-model-b.txt)

inux-firmware.git -- in fact the RPi4 is the only > affected[1] firmware currently. Triggered by your statement, I did a VERY crude search for spaces in "File: " or "Link: " lines in the WHENCE file: diederik@bagend:~/dev/kernel.org/linux-firmware$ grep -E "^Link: .* .* -&

Bug#1029843: Missing symlinks for RPi 4 (to brcmfmac43455-sdio.raspberrypi,4-model-b.txt)

Package: firmware-brcm80211 Followup-For: Bug #1029843 X-Debbugs-Cc: k...@debian.org, didi.deb...@cknow.org, debian-boot@lists.debian.org, p...@akeo.ie On Mon, 1 May 2023 11:18:03 +0100, James Addison wrote: > > Diederik de Haas (2023-04-30): > > > And that's exactly what happens or will happen

Upcoming D-I Bookworm RC 3 and RC 4

least a dinstall afterward). It might make sense not to wait too much before doing so, in case we end up having to fix a package or two, and re-upload… Regarding the final release, I'm happy to perform a final d-i upload if some packages needed an update since RC 4… but hopefully the last build

Processed: tagging 943040, tagging 1008502, tagging 1024478, notfound 1024417 in 4:22.04-2.2 ...

ccured: unmatched ')' Added tag(s) bookworm and sid. > tags 1024478 + sid bookworm Bug #1024478 [ecryptfs-utils] ecryptfs-utils: FTBFS against libgpgme-dev >= 1.18.0-2 [Cannot locate gpgme] Added tag(s) bookworm and sid. > notfound 1024417 4:22.04-2.2 Bug #1024417 [src:kgpg] kgpg

Re: Bug#1005694: bullseye-pu: package gtk+3.0/3.24.24-4+deb11u1

Hi, Adam D. Barratt (2022-02-19): > Thanks. That looks OK to me, but will need a d-i ack as gtk+3.0 builds > a udeb; tagging and CCing accordingly. d-i in bullseye is still on gtk2 (sorry), so gtk3 should be a no-brainer. :) Cheers, -- Cyril Brulebois (k...@debian.org)

Re: Bug#1005694: bullseye-pu: package gtk+3.0/3.24.24-4+deb11u1

Control: tags -1 + confirmed d-i On Sun, 2022-02-13 at 13:44 +, Simon McVittie wrote: > Typeahead search in the file chooser (File -> Save As... dialog) > doesn't > work on networked filesystems (NFS/CIFS) under some circumstances. > (Having Tracker installed might accidentally avoid the bug,

Bug#1004474: Debian 11.2 arm64`install successed in Phytium CPU FT-2000/4 box, but NIC Atheros 8035 not work

Package: installation-reports Severity: normal Tags: d-i X-Debbugs-Cc: atzli...@sina.com Boot method: USB Image version: https://mirrors.bfsu.edu.cn/debian-cd/11.2.0/arm64/iso-dvd/debian-11.2.0-arm64-DVD-1.iso Date: 2020-01-22 Machine: Phytium CPU FT-2000/4 Partitions: udev devtmpfs

Bug#603444: marked as done (debian-policy: clarifications in appendix b.4 of debian install guide)

Your message dated Tue, 28 Sep 2021 09:10:19 +0200 with message-id <20210928091019.8a67045d6437e2b690ba0...@mailbox.org> and subject line Re: #603444: clarifications in appendix b.4 of debian install guide has caused the Debian Bug report #603444, regarding debian-policy: clarificati

Re: #603444: clarifications in appendix b.4 of debian install guide

Gregory Nowak wrote: > 1. Section b.4.3 states: > > "Use the following settings if you wish to make use of the network-console > # component for remote installation over SSH. This only makes sense if you > # intend to perform the remainder of the installation manually." > > Where can one find

Re: Bug#991830: unblock: linux/5.10.46-4

Salvatore Bonaccorso (2021-08-02): > Would you agree on such a very short timed upload still to be > targetting for bullseye? As discussed separately, from a d-i point of view, this shouldn't be a problem. *IF* we need to reupload d-i before 11.0, we'll pick whatever kernel is in the archive and

Bug#989593: installation report Raspberry Pi 4 UEFI

Hi Cyril, thanks for the analysis. On Thu, Jun 10, 2021 at 05:16:31PM +0200, Cyril Brulebois wrote: > May 25 11:15:32 localechooser: info: System locale > (debian-installer/locale) = 'en_US.UTF-8' > May 25 11:15:32 localechooser: info: Set debian-installer/language = > 'en_US:en' >

Bug#989593: installation report Raspberry Pi 4 UEFI

Marc Haber (2021-06-09): > I have attached the installer's syslog of a new installation. All > issues that I reported were observed during this installation. Thanks, this sticks out: May 25 11:15:32 localechooser: info: System locale (debian-installer/locale) = 'en_US.UTF-8' May 25 11:1

Bug#989593: installation report Raspberry Pi 4 UEFI

On Wed, Jun 09, 2021 at 12:24:33AM +0200, Geert Stappers wrote: > Repeating this: I apologize for waiting for delivery of a new usb stick so that the new installation would not be a complete waste of time. > If you were to retry the installation, saving /var/log/syslog manually > before rebooting

Bug#989593: installation report Raspberry Pi 4 UEFI

> > I guess someone could try various images outside the Pi 4 setup and see > whether/when that regressed. Given the following issue (ssd), I wouldn't > rule out some Pi-specific, but such a trivial thing seems a little > strange… That being said, I test the graphical installer

Bug#989593: installation report Raspberry Pi 4 UEFI

On Tue, Jun 08, 2021 at 09:49:15PM +0200, Marc Haber wrote: > > The more pressing issue IMO is the deletion of /sbin/start-stop-daemon. > Repeating this: If you were to retry the installation, saving /var/log/syslog manually before rebooting into the installed system would be useful. Without it,

Bug#989593: installation report Raspberry Pi 4 UEFI

On Tue, Jun 08, 2021 at 09:27:57PM +0200, Holger Wansing wrote: > I checked with rc1 and the *brandnew* rc2 netinst images on amd64 qemu > VM machine (text installer), and I cannot reproduce such issue with wrong > keyboard layout; German is correctly available immediately after the > "Configure

Bug#989593: installation report Raspberry Pi 4 UEFI

Marc Haber (2021-06-08): > The Raspi 4 has both Wifi and Ethernet interfaces named brcmsomething, > so it's still kind of guessing, but I have verified in the mean time > that it's actually really the Wifi firmware. Alright, thanks for confirming. > Text installer (&quo

Bug#989593: installation report Raspberry Pi 4 UEFI

e > > installed system and the 1000Base-TX interface works fine without. > > AFAICR (I'll get back to that soon enough) you should get a message > indicating which files were expected, so that you don't have to guess. The Raspi 4 has both Wifi and Ethernet interfaces named

Bug#989593: installation report Raspberry Pi 4 UEFI

Hallo Marc, Marc Haber (2021-06-08): > I followed the instructions given on > https://www.raspberrypi.org/forums/viewtopic.php?t=282839 > to install Debian on a Raspberry Pi using the UEFI firmware > available for the raspi. > > This involves unpacking the official Debian 11 image into an ESP >

Bug#989593: installation report Raspberry Pi 4 UEFI

Package: installation-reports Version: 2.78 Severity: normal Tags: d-i Hi, I followed the instructions given on https://www.raspberrypi.org/forums/viewtopic.php?t=282839 to install Debian on a Raspberry Pi using the UEFI firmware available for the raspi. This involves unpacking the official Debi

Processed: bug 988589 is forwarded to https://salsa.debian.org/installer-team/cdebconf/-/merge_requests/4

Processing commands for cont...@bugs.debian.org: > forwarded 988589 > https://salsa.debian.org/installer-team/cdebconf/-/merge_requests/4 Bug #988589 [cdebconf-gtk] cdebconf-gtk: should capture GLib structured logging to syslog in d-i Set Bug forwarded-to-address to 'https://salsa

Re: Bug#987947: unblock (pre-approval): gtk+3.0/3.24.24-4

Hi Simon, Simon McVittie (2021-05-02): > [ Risks ] > This is obviously an important key package that lots of things depend > on. Technically it also has a udeb, although I'm fairly sure d-i is > still using GTK 2 and so the udeb is not actually used for anything > yet. That's absolutely correct:

Bug#987947: unblock (pre-approval): gtk+3.0/3.24.24-4

fixes is something I'm happy to discuss: I've prepared a candidate package with a reasonable set. Does this look acceptable? unblock gtk+3.0/3.24.24-4 [ Reason ] Backport various targeted fixes from upstream 3.24.25 up to 3.24.29, avoiding lower-impact and higher-regression-risk parts (n

Bug#985922: unblock: u-boot/2021.01+dfsg-4

/2021.01+dfsg-4 Thanks for your work managing the release! live well, vagrant diff -Nru u-boot-2021.01+dfsg/debian/bin/u-boot-install-sunxi u-boot-2021.01+dfsg/debian/bin/u-boot-install-sunxi --- u-boot-2021.01+dfsg/debian/bin/u-boot-install-sunxi 2021-02-28 18:14:48.0 -0800 +++ u-boot

Bug#805342: marked as done (Stretch Alpha 4 Installation Report (failed))

Your message dated Fri, 21 Aug 2020 04:58:02 +0200 with message-id <20200821045802.07acb7c9ded347064600d...@mailbox.org> and subject line Re: Mass-closing old installation-report bugs --- round 5 has caused the Debian Bug report #805342, regarding Stretch Alpha 4 Installation Report (fail

Re: Mass-closing old installation-report bugs --- round 4

is no chance to analyse them further and therefore > they are no longer relevant or of any use for current releases: round 4 (for Debian 7 / 8): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809618 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809654 https://bugs.debian.or

Bug#780043: marked as done (installation-reports: installer only has support for XFS and FAT32/FAT16; EXT2/3/4 and BTRFS are missing)

Your message dated Sat, 1 Aug 2020 21:37:54 +0200 with message-id <20200801213754.a0975b80ef846c7df5844...@mailbox.org> and subject line Re: #780043 installation-reports: installer only has support for XFS and FAT32/FAT16; EXT2/3/4 and BTRFS are missing has caused the Debian Bug report #

Re: #780043 installation-reports: installer only has support for XFS and FAT32/FAT16; EXT2/3/4 and BTRFS are missing

Michael Neuffer wrote (8 Mar 2015 17:15:01): > Normal install process, selected one partition in partitioner. > Patrtitioner used ext4 for / (as expected) > but the following mount of the partition failed. > > Back in the partitioner, looking at the available FS type only showed > XFS, FAT32 an

Four(4) problems, individually mentioned by three(3) emails

To, Teams Debian CD and Grub Development, Dear Sirs, Good morning, Sirs. Things are becoming complicated quickly and getting out of hand. This is an introductory email. The following emails shall address one(1) problem separately. Reply ISN'T requested for this email. I have essentially f

Re: Bug#932900: buster-pu: package freetype 2.9.1-4

Adam D. Barratt (2019-07-26): > As freetype produces a udeb, this will need an ack from the d-i release > manager, so CCing and tagging appropriately. No objections, thanks. Cheers, -- Cyril Brulebois (k...@debian.org) D-I release manager -- Release team membe

Re: Bug#932900: buster-pu: package freetype 2.9.1-4

Hi Cyril, On Sat, 27 Jul 2019 at 8:40 pm, Cyril Brulebois wrote: > Adam D. Barratt (2019-07-26): > > As freetype produces a udeb, this will need an ack from the d-i > > release manager, so CCing and tagging appropriately. > > I'll need some time to get that tested properly. How are you getting

Re: Bug#932900: buster-pu: package freetype 2.9.1-4

Thanks to Paul for adding the correct tags and bug information. reportbug doesn't actually support buster-pu yet. In saying that, the next logical step would have been to check which pseudo headers were required. > -4 has already been uploaded to unstable, so this would need to be

Re: Bug#932900: buster-pu: package freetype 2.9.1-4

Hi, Adam D. Barratt (2019-07-26): > -4 has already been uploaded to unstable, so this would need to be > 2.9.1-3+deb10u1. The changelog distribution is also preferred as > "buster", rather than "stable". > > As freetype produces a udeb, this will need an ack

Re: Bug#932900: buster-pu: package freetype 2.9.1-4

FreeType for variable hinted fonts. Firefox is also affected. Google Fonts states that Oswald is used on 8.3M websites. Given that Chromium and Firefox are affected, and the significant presence of variable hinted fonts in use on the internet and elsewhere, I am requesting freetype 2.9.1-4 be

Processed (with 4 errors): Re: console-setup | kbdnames-maker: Call `{bind,}textdomain` after switching locale (!2)

Processing commands for cont...@bugs.debian.org: > clone 924657 -1 Bug #924657 [keyboard-configuration] kbdnames are generated with incorrect translations Bug #922604 [keyboard-configuration] all_kbdnames data structure corrupt Failed to clone 924657: Bug is marked as being merged with others. Us

Bug#929215: unblock: systemd/241-4

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package systemd All patches are cherry-picked from upstream git. Annotated changelog: systemd (241-4) unstable; urgency=medium * journal-remote: Do not request Content

Bug#928506: installation-report: fails to find mirror under OpenBSD vmm(4) hypervisor

Control: tag -1 - d-i Hi Matthew, Matthew T Hoare (2019-05-06): > Dear Maintainer, > >* What led up to the situation? >I ran the installer under OpenBSD's vmm(4) hypervisor. >* What exactly did you do (or not do) that was effective (or > ineffective)? &

Processed: Re: Bug#928506: installation-report: fails to find mirror under OpenBSD vmm(4) hypervisor

Processing control commands: > tag -1 - d-i Bug #928506 [installation-reports] installation-report: fails to find mirror under OpenBSD vmm(4) hypervisor Removed tag(s) d-i. -- 928506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928506 Debian Bug Tracking System Contact

Bug#928506: installation-report: fails to find mirror under OpenBSD vmm(4) hypervisor

Package: installation-reports Version: 2.71 Severity: normal Tags: d-i Dear Maintainer, * What led up to the situation? I ran the installer under OpenBSD's vmm(4) hypervisor. * What exactly did you do (or not do) that was effective (or ineffective)? Tried to connect to a m

Bug#923675: Bug#927111: unblock: wpa/2:2.7+git20190128+0c1e29f-4

Niels Thykier (2019-04-18): > Cyril Brulebois: > > I think it'd be nice to have some tests on a real wireless adapter, > > which I'll try to get to in the next days, because of the amount of > > patching involved. That shouldn't stop you from letting the package > > reach testing first though. As

Bug#926831: unblock: u-boot/2019.01+dfsg-4

+++ u-boot-2019.01+dfsg/debian/changelog2019-04-08 19:47:02.0 -0700 @@ -1,3 +1,13 @@ +u-boot (2019.01+dfsg-4) unstable; urgency=medium + + [ Martyn Welch ] + * [armhf] u-boot-imx: Enable build for NXP SABRE Lite. + + [ Neil Armstrong ] + * [arm64] u-boot-amlogic: Enable nanopi

Re: Bug#926299: unblock: busybox/1:1.30.1-4

979 in busybox-udeb. > > Should we (RT) unblock it now or do you prefer waiting (as I > understand it there is d-i release coming up). > > unblock busybox/1:1.30.1-4 If you see a package that gets uploaded with a patch of mine for a bug report I opened, mentioning I'd like to s

Bug#926299: unblock: busybox/1:1.30.1-4

nd it there is d-i release coming up). unblock busybox/1:1.30.1-4 Thanks, ~Niels

PXE booting a 'netinst' image (was: Debian Installer Buster Alpha 4 release)

On Mon, Dec 17, 2018 at 02:29:27AM +0100, Cyril Brulebois wrote: > Steve McIntyre (2018-12-17): > > But... The problem you're most likely seeing is caused by a simple > > fact. The *netboot* image ends up downloading significant chunks of > > the installer and the base system at runtime from the s

support for OpenRD and Sheevaplug (was Re: Debian Installer Buster Alpha 4 release)

On 2018-12-17, Rick Thomas wrote: >> On Dec 15, 2018, at 2:26 PM, Cyril Brulebois wrote: >> >> Hardware support changes >> >> >> * debian-installer: >> - [armel] Disable OpenRD targets, no longer present in u-boot. > > Does this mean that my OpenRD hardware will no lon

Re: Debian Installer Buster Alpha 4 release

Hi Cyril, thanks for the summary and all your work for the installer. I have not seen any mentioning of supporting Blends in the new installer. I remember that we talked about this at DebConf 16 that chances are good that we finally will get the feature to select Blends right from the installer.

Re: Debian Installer Buster Alpha 4 release

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Le 15/12/2018 à 23:26, Cyril Brulebois a écrit : > The Debian Installer team[1] is pleased to announce the fourth alpha release > of the installer for Debian 10 "Buster". Would it be possible to have remarks about #913431 (partman-base: Ad

Re: Debian Installer Buster Alpha 4 release

> On Dec 15, 2018, at 2:26 PM, Cyril Brulebois wrote: > > Hardware support changes > > > * debian-installer: >- [armel] Disable OpenRD targets, no longer present in u-boot. Does this mean that my OpenRD hardware will no longer be supported in Buster? What about S

Re: Debian Installer Buster Alpha 4 release

On Mon, Dec 17, 2018 at 02:29:27AM +0100, Cyril Brulebois wrote: > Steve McIntyre (2018-12-17): > > But... The problem you're most likely seeing is caused by a simple > > fact. The *netboot* image ends up downloading significant chunks of > > the installer and the base system at runtime from the s

Re: Debian Installer Buster Alpha 4 release

the same > >set of sources as the _netinst_ ? > > The images team doesn't make the _netboot_ image - that comes straight > out of the d-i build. > > So... the path to the current buster netboot image also points to the > same d-i build (20181206) that was used for t

Re: Debian Installer Buster Alpha 4 release

Steve McIntyre (2018-12-17): > But... The problem you're most likely seeing is caused by a simple > fact. The *netboot* image ends up downloading significant chunks of > the installer and the base system at runtime from the suite it > targets. For buster, that is still very much a moving target an

Re: Debian Installer Buster Alpha 4 release

etboot_ image is from the same >set of sources as the _netinst_ ? The images team doesn't make the _netboot_ image - that comes straight out of the d-i build. So... the path to the current buster netboot image also points to the same d-i build (20181206) that was used for the d-i alpha 4

re: Debian Installer Buster Alpha 4 release

Hello I was trying to download the netboot image for amd64, because the one I have (2018-12-06) has a segfault in libc6. The link on the installer team page https://www.debian.org/devel/debian-installer/ for the _netinst_ image points at https://cdimage.debian.org/cdimage/buster_di_alpha4/amd

Debian Installer Buster Alpha 4 release

88 image, as u-boot fails to boot due to #898520. - [armhf] Add image for Sinovoip_BPI_M3. - [arm64] Add u-boot image for pinebook. - [mips*el/loongson-3] add input modules to netboot image (#911664). * flash-kernel: - Add a machine db entry for Helios-4 NAS system (#914016

Bug#914016: marked as done (flash-kernel: please add support for Helios 4 NAS)

Your message dated Sun, 18 Nov 2018 19:19:43 + with message-id and subject line Bug#914016: fixed in flash-kernel 3.96 has caused the Debian Bug report #914016, regarding flash-kernel: please add support for Helios 4 NAS to be marked as done. This means that you claim that the problem has

Bug#914016: flash-kernel: please add support for Helios 4 NAS

Package: flash-kernel Version: 3.95 Severity: wishlist Dear Maintainer, Support for the Helios-4 NAS finally landed in linux 4.19 by acceptance of the DTB. There is 2018.11 based u-boot available, and it can use the generic boot-script: https://github.com/helios-4/u-boot/commits/helios4 Tested

Re: any ETA when debian buster alpha 4 will be released ?

Hi, Am Montag, 22. Oktober 2018 schrieb shirish शिरीष: > https://lists.debian.org/debian-devel-announce/2018/09/msg4.html > > Does it mean we won't have an alpha 4 of Debian buster before freeze > or would there ? > > There is an event happening in India de

any ETA when debian buster alpha 4 will be released ?

;t have an alpha 4 of Debian buster before freeze or would there ? There is an event happening in India debutsav kochi https://debutsav.in Where I was hoping to have a debian buster alpha 4 release if it's on the radar. If not, we could always use the daily release but that is pretty

Re: Towards Debian Buster Alpha 4 -- installation-guide

Hi, Samuel Thibault wrote: > Holger Wansing, le dim. 23 sept. 2018 14:16:21 +0200, a ecrit: > > I would like to have an upload for installation-guide. [...] > > I have prepared an upload, it's getting uploaded. > > Thanks for your work! > Samuel That was quick :-) Thanks Holger --

Re: Towards Debian Buster Alpha 4 -- installation-guide

Hello, Holger Wansing, le dim. 23 sept. 2018 14:16:21 +0200, a ecrit: > Holger Wansing wrote: > > Ah, maybe upload installation-guide? > > Would be a good time for that. Also, to get installation-guide back into > > testing (has been removed two months ago). > > I would like to have an upload fo

Re: Towards Debian Buster Alpha 4 -- installation-guide

Hi Samuel, Holger Wansing wrote: > Ah, maybe upload installation-guide? > Would be a good time for that. Also, to get installation-guide back into > testing (has been removed two months ago). I would like to have an upload for installation-guide. Since currently I am unable to upload this mysel

Re: Towards Debian Buster Alpha 4

Hi! On 08/29/2018 06:04 PM, Cyril Brulebois wrote: >> There is one regression on powerpc/ppc64 (I know, not release architectures) >> as a result of changes in the kernel packaging (linux-bootwrapper package) >> that I would like to get fixed before the next upload. > > OK, I'll try to accomodate

Re: Towards Debian Buster Alpha 4

On 2018/08/29 19:22, Steve McIntyre wrote: >> Turns out August was pretty busy as well… and I haven't been able to prepare >> things as I wanted. Thankfully Holger's been invested with some extra powers >> and we now have a huge bunch of packages uploaded. Let's see if I can manage >> to make the n

Re: Towards Debian Buster Alpha 4

7;s been invested with some extra powers > and we now have a huge bunch of packages uploaded. Let's see if I can manage > to make the new alpha happen in the next few days or weeks. As of now, I uploaded most of the packages with translation updates, and some more trivial uploades too. (T

Re: Towards Debian Buster Alpha 4

On Wed, Aug 29, 2018 at 02:53:16PM +0200, Cyril Brulebois wrote: >Hi, > >Cyril Brulebois (2018-07-31): >> Being back from a rather busy quarter, I'd like to resume releasing d-i >> more frequently. I'd like to publish a new alpha somewhen during the >> next few days/weeks (if that's fine with debi

Re: Towards Debian Buster Alpha 4

John Paul Adrian Glaubitz (2018-08-29): > On 08/29/2018 02:53 PM, Cyril Brulebois wrote: > > Turns out August was pretty busy as well… and I haven't been able to prepare > > things as I wanted. Thankfully Holger's been invested with some extra powers > > and we now have a huge bunch of packages up

Re: Towards Debian Buster Alpha 4

elp from Ben though since I haven't found a suitable solution yet. Should be a small patch though once I know how to fix it and I try to get it committed as soon as possible not to block Alpha 4. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub.

Re: Towards Debian Buster Alpha 4

Hi, Cyril Brulebois (2018-07-31): > Being back from a rather busy quarter, I'd like to resume releasing d-i > more frequently. I'd like to publish a new alpha somewhen during the > next few days/weeks (if that's fine with debian-cd). > > If you have changes pending in master branches that need u

Re: Towards Debian Buster Alpha 4

Hi, On Tue, 31 Jul 2018 02:06:40 +0200 Cyril Brulebois wrote: > If you have changes pending in master branches that need uploading, or > specific packages that need to reach testing, please mention which, and > why. I failed to upload debootstrap 1.0.107 but will do it after DebConf. And will

Re: Towards Debian Buster Alpha 4

Hi Cyril, Cyril Brulebois writes: > Hi, > > Being back from a rather busy quarter, I'd like to resume releasing d-i > more frequently. I'd like to publish a new alpha somewhen during the > next few days/weeks (if that's fine with debian-cd). > > If you have changes pending in master branches tha

Re: Towards Debian Buster Alpha 4

On Tue, Jul 31, 2018 at 11:10:01AM +0200, Cyril Brulebois wrote: >Steve McIntyre (2018-07-31): >> I can take a look for this release myself too. Maybe we should add a >> monitor to check on any outstanding things that have not been >> uploaded... > >We have those already: > https://d-i.debian.org

Re: Towards Debian Buster Alpha 4

Hi, Cyril Brulebois wrote: > Hi Holger, > > Holger Wansing (2018-07-31): > > Cyril Brulebois wrote: > > > Hi, > > > > > > Being back from a rather busy quarter, I'd like to resume releasing d-i > > > more frequently. I'd like to publish a new alpha somewhen during the > > > next few days/week

Re: Towards Debian Buster Alpha 4

Hi, Steve McIntyre wrote: > >> You are most likely aware of the big bunch of d-i packages with pending > >> l10n uploads? Christians upload work is really missing here ... :-( > > > >I cannot commit to doing that work, because there are only that many > >hours in a single day. I might end up doin

Re: Towards Debian Buster Alpha 4

Steve McIntyre (2018-07-31): > I can take a look for this release myself too. Maybe we should add a > monitor to check on any outstanding things that have not been > uploaded... We have those already: https://d-i.debian.org/translations.txt https://d-i.debian.org/git-summary.html Cheers, --

Re: Towards Debian Buster Alpha 4

On Tue, Jul 31, 2018 at 10:30:32AM +0200, Cyril Brulebois wrote: >Hi Holger, > >Holger Wansing (2018-07-31): >> Cyril Brulebois wrote: >> > Hi, >> > >> > Being back from a rather busy quarter, I'd like to resume releasing d-i >> > more frequently. I'd like to publish a new alpha somewhen during

Re: Towards Debian Buster Alpha 4

Hi Holger, Holger Wansing (2018-07-31): > Cyril Brulebois wrote: > > Hi, > > > > Being back from a rather busy quarter, I'd like to resume releasing d-i > > more frequently. I'd like to publish a new alpha somewhen during the > > next few days/weeks (if that's fine with debian-cd). > > > > If

Re: Towards Debian Buster Alpha 4

Hi, Cyril Brulebois wrote: > Hi, > > Being back from a rather busy quarter, I'd like to resume releasing d-i > more frequently. I'd like to publish a new alpha somewhen during the > next few days/weeks (if that's fine with debian-cd). > > If you have changes pending in master branches that need

Re: Towards Debian Buster Alpha 4

Hi, Cyril Brulebois (2018-07-31): > Being back from a rather busy quarter, I'd like to resume releasing d-i > more frequently. I'd like to publish a new alpha somewhen during the > next few days/weeks (if that's fine with debian-cd). Got confirmation from Steve: that looks fine. > If you have c

Towards Debian Buster Alpha 4

Hi, Being back from a rather busy quarter, I'd like to resume releasing d-i more frequently. I'd like to publish a new alpha somewhen during the next few days/weeks (if that's fine with debian-cd). If you have changes pending in master branches that need uploading, or specific packages that need

Bug#872181: marked as done (debootstrap: error processing argument #4)

Your message dated Thu, 22 Mar 2018 06:58:05 +0900 with message-id <20180322065805.5114a61145af956c345ad...@iijmio-mail.jp> and subject line Re: Bug#872181: debootstrap: error processing argument #4 has caused the Debian Bug report #872181, regarding debootstrap: error processing argument #4

Processed: notfixed 820416 in 17.0~beta5+dfsg1-4, fixed 820416 in 2:17.0~beta5+dfsg1-4, fixed 502180 in 3.14.1-2 ...

Processing commands for cont...@bugs.debian.org: > # fixing up bug metadata to allow archival > notfixed 820416 17.0~beta5+dfsg1-4 Bug #820416 {Done: Santiago Vila } [src:kodi] kodi: FTBFS in testing (Segmentation fault) The source 'kodi' and version '17.0~beta5+dfsg1-4&#x

Bug#872181: debootstrap: error processing argument #4

Hello Kibi: On Thu, Aug 17, 2017 at 01:37:44AM +0200, Cyril Brulebois wrote: > Control: tag -1 moreinfo .. > I'm not sure what you're suggesting. 1.0.91 has SCRIPT="$4" AFAICT. > Ditto for 1.0.67+deb8u1. Agreed. Perhaps the 'diff' arguments were in

Processed: Re: Bug#872181: debootstrap: error processing argument #4

Processing control commands: > tag -1 moreinfo Bug #872181 [debootstrap] debootstrap: error processing argument #4 Added tag(s) moreinfo. -- 872181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#872181: debootstrap: error processing argument #4

uot; > fi > > >* What was the outcome of this action? > >rootstrap failed. > >* What outcome did you expect instead? > >rootstrap to succeed. > > suggested patch from: > diff downloads/debootstrap-1.0.91/debootstrap /usr/sbin/deboot

Bug#872181: debootstrap: error processing argument #4

d patch from: diff downloads/debootstrap-1.0.91/debootstrap /usr/sbin/debootstrap : 416c395 < SCRIPT="$DEBOOTSTRAP_DIR/scripts/$4" --- > SCRIPT="$4" Thanks, Douglas. -- System Information: Debian Release: 8.9 APT prefers oldstable-updates

Re: Debian Installer Stretch RC 4 release

Andrew M.A. Cater (2017-05-27): > Is it possible to link bootnetx from the debian installer in the same > way that pxelinux is linked? It would help enormously for PXE booting > UEFI if bootnetx were immediately visible and available. It would be > really good if this could be done prior to releas

Re: Debian Installer Stretch RC 4 release

On Sat, May 27, 2017 at 04:47:57PM +0200, Cyril Brulebois wrote: > The Debian Installer team[1] is pleased to announce the fourth release > candidate of the installer for Debian 9 "Stretch". > > > Improvements in this release > > > * apt-setup: > - Switch defaul

Debian Installer Stretch RC 4 release

The Debian Installer team[1] is pleased to announce the fourth release candidate of the installer for Debian 9 "Stretch". Improvements in this release * apt-setup: - Switch default hostname from ftp.debian.org to deb.debian.org in the 92updates and 93backp

  1   2   3   4   5   6   7   >