t 4:29 AM, Steve McIntyre wrote:
>
>On Fri, Jun 30, 2017 at 08:43:28PM +0530, user01 wrote:
>
>Package: debian-installer Version: 20170615 Severity: important Dear
>Maintainer,
>
>* What led up to the situation?
>
>Debian stretch i
nonfree/amd64/iso-cd/firmware-9.0.0-amd64-netinst.iso
and I see no such issue. Are you *sure* you weren't using a live image?
--
Steve McIntyre, Cambridge, UK.st...@einval.com
Can't keep my eyes from the circling sky,
Tongue-tied & twisted, Just an earth-bound misfit, I...
;error,
>"failed to determine the codename for the release." and fails.
You don't say explicitly, but from the symptoms you're describing
you're trying to use the live installer?
--
Steve McIntyre, Cambridge, UK.st...@einval.com
We don't need no education.
We don't need no thought control.
;firmware MATE versions. About to try it with Gnome (standard). All instances
>use the full DVD image ~ 2.2Gb.
Then you're most likely seeing a very different error, I'm afraid. If
you switch to VT4 (Ctrl-Alt-F4), what error(s) do you see in the syslog?
--
Steve McIntyre, Cambrid
t;Malayalam, I expect to be able to type in Malayalam. But Malayalam and
>all Indian Language layouts are available only in ibus-m17n (ibus is
>already installed).
>
>This should also be included in installer DVD1 and xfce cd1.
ACK, reassigning to the correct place.
Package: openstack-debian-images
Version: 1.19
Severity: serious
Tags: patch
The code is currently *only* adding security sources into
apt/sources.list when building for wheezy or jessie. This is clearly
wrong. I've just had to rebuild our stretch images again (9.0.1 to
9.0.2) to get expected upda
md64/iso-hybrid/debian-live-9.0.1-amd64-mate+nonfree.iso
I've just done a test installation using that exact image with no
problems. Are you *sure* you're using 9.0.1? This is one of the things
that was fixed in the 9.0.1 rebuild...
--
Steve McIntyre, Cambridge, UK.
0341d0,0)PCI(1f,6)MAC(MAC(4ccc6a07d477,0)..BO
>Boot0003 UEFI: IP6 Intel(R) Ethernet Connection (H) I219-V
>ACPI(a0341d0,0)PCI(1f,6)MAC(MAC(4ccc6a07d477,0)030d3c40..BO
>
>
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"... th
y Steve (“the Packages
>files in the image point to .debs using full path, not relative to the
>stuff in the image”). Reassigning to live-installer, which might not be
>the correct package, but is probably better than just debian-installer.
That's fair enough. I think I've fou
5.0-6+deb8u2
ii mbr 1.1.11-5+b1
ii parted 3.2-7
ii qemu-utils 1:2.1+dfsg-12+deb8u6
openstack-debian-images recommends no packages.
openstack-debian-images suggests no packages.
-- no debconf information
>From 12c5e3a7de103e6cb73235cff6d11180a225c98c Mon Sep 17 00
>efibootmgr: option requires an argument -- 'd'
>efibootmgr version 14
OK, that's odd. Can you run "grub-install -v --target=arm64-efi" and
grab the output please? Curious to see exactly what the full command
line for efibootmgr is here...
--
Steve McIntyre, Cambridge
On Thu, Feb 02, 2017 at 02:42:26PM +0100, Jens Reyer wrote:
>On 02/02/2017 02:30 PM, Steve McIntyre wrote:
>> Dropping the -nostdlib argument to the gcc call inside sonames2elf
>> makes a difference - it'll add libc6 to the mix and force the output
>> to match the syste
Hi,
On Thu, Feb 02, 2017 at 05:10:14AM +0100, Guillem Jover wrote:
>On Wed, 2017-02-01 at 15:34:04 +0000, Steve McIntyre wrote:
>>
>> Please don't go down that route, the ABI flags are intended to save
>> people from that. I'm curious what's going wrong with
On Wed, Feb 01, 2017 at 05:03:13PM +0100, Jens Reyer wrote:
>On 02/01/2017 04:34 PM, Steve McIntyre wrote:
>>
>> Please don't go down that route, the ABI flags are intended to save
>> people from that. I'm curious what's going wrong with libgsm1 here
>>
ng consistent ABI flags.
If you're worried about EABIv4, does the logic of the dpkg checker not
match the checks we added in glibc itself?
--
Steve McIntyre, Cambridge, UK.st...@einval.com
Mature Sporty Personal
More Innovation More Adult
A Man in Dandism
Powered Midship Specialty
On Mon, Jan 30, 2017 at 06:32:00PM +, Steve McIntyre wrote:
>Package: grub2-common
>Version: 2.02~beta2-22+deb8u1
>Severity: serious
>Tags: upstream
>
>Hi,
>
>As can be seen in #852513 (for example), grub-install will happily
>ignore errors from efibootmgr and claim
ignores errors from efibootmgr
I have a simple fix for this which I'm about to post upstream.
* #853237 (efibootmgr): ENOSPC errors should be more helpful
Data from you would be helpful here!
Thanks!
--
Steve McIntyre, Cambridge, UK.st...@einval.com
Welco
Package: grub2-common
Version: 2.02~beta2-22+deb8u1
Severity: serious
Tags: upstream
Hi,
As can be seen in #852513 (for example), grub-install will happily
ignore errors from efibootmgr and claim "Installation finished. No
error reported". This is clearly bogus, and can lead to users with
unboota
which would help. While that's not implemented, at the very least
I'm thinking about error checking in grub-install. Simply
suggesting the user looks in /sys/fs/pstore and maybe delete things
would be better than the current "can't boot" issue.
--
Steve McI
Control: severity -1 important
Agreed that this is important, but we don't have lots of similar
reports since jessie d-i RC1 ~two years ago.
Heiko - could you possibly try a newer version of the installer and
see if the problem still exists please?
--
Steve McIntyre, Cambridg
Simple fix for build failure is to add --no-dynamic-linker to the
linker command lines. Here's the NMU diff; this is in incoming now...
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"You can't barbecue lettuce!" -- Ellie Crane
diff -Nr
ied gparted locally and it seemed to work OK for me. Could
you give us more information about exactly what you did to trigger
this please?
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"We're the technical experts. We were hired so that management could
ignore our recommendations and tell us how to do our jobs." -- Mike Andrews
I'm uploading this to unstable now rather than to DELAYED; there's not
been any obvious maintainer activity here for ages...
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"Since phone messaging became popular, the young generation has lost the
came up. I tried
>several combinations of --target --boot-directory --recheck
>--efi-directory but with no luck.
>
> * What outcome did you expect instead?
>
>I expected grub to use 'main's grub.cfg instead of 'rescue's.
How exactly are you booting each of the systems?
--
Steve McIntyre, Cambridge, UK.st...@einval.com
You raise the blade, you make the change... You re-arrange me 'til I'm sane...
64 (x86_64)
>
>Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
>Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
>Shell: /bin/sh linked to /bin/dash
>Init: systemd (via /run/systemd/system)
>
>
--
Steve McIntyre, Cambridge, UK.st...
we could do to fail the build if versions are out of
sync, rather than let a broken build through?
--
Steve McIntyre, Cambridge, UK.st...@einval.com
< Aardvark> I dislike C++ to start with. C++11 just seems to be
handing rope-creating factories for users to hang multiple
instances of themselves.
VM install it is clear that the
>local DNS server returns the correct response, but this is being ignored
>or lost by the D-I initrd.
For the sake of completeness, I can confirm that the same problem
shows up when running on a different network too. I also see this
using the oldest amd64 dai
Control: tag -1 +pending
On Wed, Jan 04, 2017 at 07:04:59PM +, Steve McIntyre wrote:
>On Thu, Dec 29, 2016 at 03:22:02PM +, Chris West (Faux) wrote:
>>
>>The package fails to build on armhf:
...
>Confirmed - just seen the same build failure on a porter box. Looks
&g
cross objects may fail
>collect2: error: ld returned 1 exit status
>/build/1st/efibootmgr-14/Make.rules:21: recipe for target 'efibootmgr' failed
Confirmed - just seen the same build failure on a porter box. Looks
like YA issue found with newer gcc. I'll look for a fix.
--
Control: severity -1 important
[ Please CC the bug report address 845...@bug.debian.org so other
people can follow this conversation too... ]
On Sat, Nov 19, 2016 at 08:08:58PM +0300, Vladimir Stavrinov wrote:
>On Sat, Nov 19, 2016 at 03:55:43PM +0000, Steve McIntyre wrote:
>
>>
the command line you're using. I'd expect to
see something more like:
efibootmgr -c -L debian -l \EFI\debian\grubx64.efi
(maybe along with some other options).
grub-install -v will show you exactly what commands grub is trying to
use.
--
Steve McIntyre, Cambridge, UK.
urgency=medium
+
+ * NMU
+ * Fix build for dpkg-buildpackage -A. Thanks to Santiago Vila for the
+patch. Closes: #806068
+
+ -- Steve McIntyre <93...@debian.org> Mon, 26 Sep 2016 12:08:40 -0700
+
linaro-image-tools (2014.11-1) unstable; urgency=medium
* New upstream release.
diff -N
Control: close -1 4.12-3
Gah, not awake yet today.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
You raise the blade, you make the change... You re-arrange me 'til I'm sane...
Control: notfound -1 4.12-3
I didn't close this automatically with 4.12-3, was waiting to see it
worked. Closing now.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
You lock the door
And throw away the key
There's someone in my head but it's not me
On Fri, Apr 29, 2016 at 07:31:11PM +0200, pollux wrote:
>On 04/29/2016 06:58 PM, Steve McIntyre wrote:
>> On Fri, Apr 29, 2016 at 06:20:55PM +0200, pollux wrote:
>>> Indeed, on PC architectures, EFI executables are 64-bits EXE files.
>>
>> Ummm, what? 32-bit i386 (
h: foreign, however that would cover only the
>embedded EFI files, not the tools to access UEFI variables.
>That said, these tools use the efivars pseudo-filesystem and will only
>work on Linux.
>
>So, I think the next upload will restrict the package to linux-amd64 only.
Please don
On Tue, Apr 26, 2016 at 12:33:38AM +0100, Steve McIntyre wrote:
>On Mon, Apr 25, 2016 at 09:57:00AM +0200, Aurelien Jarno wrote:
>
>>Could you please ensure that all the binaries in the archive that still
>>needs these patches are rebuilt?
>
>I'll look again for brok
On Mon, Apr 25, 2016 at 09:57:00AM +0200, Aurelien Jarno wrote:
>On 2016-04-25 00:30, Steve McIntyre wrote:
>> Package: libc6-bin
>> Severity: serious
>> Version: 2.22-7
>> Tags: patch
>>
>> Hi folks,
>>
>> Steev has reported some crashing using
is the obvious fix - enforce using ELF32 types for
all arches.
It seems that we still have some older packages without the ABI flags
attached - libshout3 is one such. :-(
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"I can't ever sleep on planes
ch system at all. Could you
tell us a little more about your setup please?
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"C++ ate my sanity" -- Jon Rabone
Package: cdimage.debian.org
Severity: grave
Tags: d-i
Version: daily-image-20160129
There's a major bug in debootstrap today (#813124) which will cause
all installations to fail. A fix has been uploaded, but DO NOT USE the
daily images until that has hit the archive - wait until 30th January
at l
Package: debootstrap
Version: 1.0.77
Severity: grave
Tags: d-i patch
The fix for #812811 is broken and shows a lack of adequate
testing. Using the --mode=$mode argument for mknod is fine on a normal
system, but in d-i we're using busybox mknod and it doesn't support
the long option --mode at all.
Sarge images in the archive
>rather than having to rebuild the Sarge images themselves.
ACK, thanks for the suggestion. I could also check the files that were
in use and compare to the stuff on snapshot.d.o for the dates in
question. It would be very hard to rebuild the sarge images now after
;I wouldn't release stretch with that behaviour, but having it in
>stretch/sid for a while is probably ok.
Right now, it's going to stop people from being able to install
stretch at all. Please take out this retarded mis-feature. By all
means, complain and warn about the problem,
On Sun, Sep 13, 2015 at 04:30:21AM +0200, Cyril Brulebois wrote:
>Steve McIntyre (2015-08-27):
>> tags 795844 + pending
>> thanks
>
>Is it OK for me to assume this is fixed for Stretch Alpha 3? That
>doesn't seem obvious while looking at /home/debian-cd/build.stretc
ore enabling such a
broken mis-feature in the first place?
We already have a packaging system that works for upgrades in place
without needing reboots like this. I strongly object to this kind of
crap being added to Debian for the sake of certain broken upstream
soft
Package: cdimage.debian.org
Severity: serious
Tags: d-i
As mentioned by bwh: existing armel and armhf installer CDs are
currently missing vmlinuz and the initramfs...
-- System Information:
Debian Release: 8.1
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign
Package: src:acpica-unix
Version: 20150515-2
Severity: serious
Tags: upstream
Hi,
Prompted by kernel log messages on the buildd (arm-linaro-03), I can
see that aapits is crashing a lot during the package build on
arm64. The test suite crashing is worrying; the package build
continuing on is worse
Package: linux-image-4.0.0-trunk-arm64
Version: 4.0-1~exp1
Severity: serious
As mentioned on IRC, this package is missing all the DTBs for arm64
machines. Looks like it's a change to the DTB layout in the upstream
tree causing it.
-- System Information:
Debian Release: 7.8
APT prefers oldoldsta
Package: src:linux
Version: 3.16.7-ckt9-3~deb8u1
Severity: serious
Hi guys,
Just debugged on harris.debian.org (imx53, Debian porter box) -
there's a missing patch that's needed for the imx53 sata controller to
work. At some point, it looks like the code in drivers/ata/ahci_imx.c
has changed and
On Wed, Apr 01, 2015 at 08:08:50PM +0200, Cyril Brulebois wrote:
>Steve McIntyre (2015-04-01):
>> As it stands, this is only for removable media which people have not
>> already set up as part of their systems. The whole issue here is that
>> this is not useful any more. If
On Wed, Apr 01, 2015 at 07:20:02PM +0200, Cyril Brulebois wrote:
>Hi Steve,
>
>Steve McIntyre (2015-03-30):
>> Right, it seems that was too conservative and still left hd-media
>> devices listed. We probably don't want those either. Let's try this:
>> don&
On Sun, Jan 25, 2015 at 11:21:08PM +, Steve McIntyre wrote:
>On Sun, Jan 25, 2015 at 11:45:40PM +0100, Cyril Brulebois wrote:
>>Steve McIntyre (2015-01-17):
>>> I'm thinking the best way to go with this is to simply drop this misc
>>> USB device support alt
Control: tag -1 +pending
On Fri, Mar 20, 2015 at 04:13:20PM +, Steve McIntyre wrote:
>Package: src:linux
>Version: 3.16.7-ckt7-1
>Severity: grave
>Tags: upstream
>
>Hi folks,
>
>We've upgraded a couple of our Marvell Armada XP based (armel/armhf)
>buildd machin
Package: src:linux
Version: 3.16.7-ckt7-1
Severity: grave
Tags: upstream
Hi folks,
We've upgraded a couple of our Marvell Armada XP based (armel/armhf)
buildd machines to Jessie, and they've almost immediately fallen over
with symptoms of really bad data corruption. On further investigation
and d
On Thu, Mar 19, 2015 at 01:23:26PM +0100, Cyril Brulebois wrote:
>(Adding Ansgar to the loop since he already commented on this bug
>report.)
>
>Steve McIntyre (2015-03-19):
>> Maybe we've got a misunderstanding here. The change is only expected
>> to stop *other* U
On Wed, Mar 18, 2015 at 11:03:26PM +0100, Cyril Brulebois wrote:
>Hi,
>
>Christian Perrier (2015-01-26):
>> partman-target (94) unstable; urgency=medium
>> .
>>[ Steve McIntyre ]
>>* Don't add entries for random USB media to /etc/fstab, they're
s invoking might be of interest, as
>would then rerunning that same command manually under strace.
In fact, for EFI just grub-install -v should tell you a lot more.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"I've only once written '
lar changes are already in git for the regular builds, just not in
the archive yet for v3.1.17. Expecting an upload shortly.
Again, curious why you're looking at 3.1.13...
--
Steve McIntyre, Cambridge, UK.st...@einval.com
Is there anybody out there?
--
T
Package: src:linux
Version: 3.16.7-ckt4-2
Severity: grave
Tags: patch upstream
The latest upstream stable kernel pull is broken on arm64. The system
panics during early boot in arch_timer setup.
The cause is simple. Commit 0b46b8a718c6e90910a1b1b0fe797be3c167e186
was pulled into stable, but a lat
On Fri, Jan 30, 2015 at 02:47:20AM +0100, Guillem Jover wrote:
>Hi!
>
>On Sun, 2015-01-25 at 20:34:48 +0000, Steve McIntyre wrote:
>>
>> I still have my backup of the VM image at the time, so it should be
>> possible to try upgrading it using snapshot.d.o from that tim
Control: severity -1 important
Control: clone -1 -2
Control: retitle -2 Installation manual should warn about the use of LVM
partition types
Control: reassign -2 installation-guide
On Sun, Jan 18, 2015 at 04:24:43PM +, Steve McIntyre wrote:
>On Wed, Nov 19, 2014 at 03:36:19PM -0600, Dr
On Sun, Jan 25, 2015 at 11:45:40PM +0100, Cyril Brulebois wrote:
>Steve McIntyre (2015-01-17):
>> I'm thinking the best way to go with this is to simply drop this misc
>> USB device support altogether from partman-target. Any objections?
>
>Not from me.
OK
rading it using snapshot.d.o from that time too, if
it's likely to be useful.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
Can't keep my eyes from the circling sky,
Tongue-tied & twisted, Just an earth-bound misfit, I...
--
To UNSUBSCRIBE,
Control: tags -1 -moreinfo
On Sun, Jan 25, 2015 at 12:30:51PM +0100, Niels Thykier wrote:
>Control: tags -1 moreinfo
>
>On Thu, 4 Dec 2014 00:56:48 +0000 Steve McIntyre wrote:
>> This is reproducible on demand \o/
>>
>> I realised that the VM image had a few
On Wed, Jan 21, 2015 at 06:55:05AM +0900, Mike Hommey wrote:
>On Tue, Jan 20, 2015 at 01:44:37PM +0000, Steve McIntyre wrote:
>>
>> The automatic setup of grub-install calling efibootmgr won't be
>> touching the "grub" entry at all - it's set up to on
On Mon, Jan 19, 2015 at 07:42:37AM +0900, Mike Hommey wrote:
>On Sun, Jan 18, 2015 at 11:37:28AM +0000, Steve McIntyre wrote:
>> The ENOSPC handling has been bad in the past, but it's not clear that
>> was the cause of your original bug. :-/ *Now* it's a very bad state t
7;t warn other
>users using UNetbootin.
I know that, but a warning for Debian users would help too. I'm also
tempted to look into how to detect unetbootin media within d-i so that
we can potentially flash up a warning to the user. I *know* it may be
a useful tool for some folks (and it use
Source: unetbootin
Severity: serious
Tags: d-i
Justification: wasting massive amounts of developer and user time
I've already added one wishlist bug for d-i to add code to detect
unetbootin usage and complain about it, but I've not got there
yet. unetbootin used to be a helpful tool for many peopl
filesystem/blkid contents; OR
(b) Warn about such partitions and ask the user what to do.
2(a) looks much easier, I'll be honest, so that's my plan for now.
As a point of information, you weren't sure what the "K" tag means in
the d-i partitioner. Ironical
no longer works of course.
Well, as another person with a chiark account I can see that Neil is
still using his login there and has been active in the last
week. Whether or not he's reading email there, I don't know...
I'll prod too.
--
Steve McIntyre, Cambridge, UK.
67 write(2, ": ", 2) = 2
>9167 write(2, "No such file or directory\n", 26) = 26
>9167 write(2, "efibootmgr: ", 12) = 12
>9167 write(2, "Could not prepare boot variable", 31) = 31
>9167 write(2, ": ", 2)
On Sun, Jan 18, 2015 at 08:16:51AM +0900, Mike Hommey wrote:
>On Sat, Jan 17, 2015 at 05:22:52PM +0000, Steve McIntyre wrote:
>> On Sat, Jan 17, 2015 at 04:16:56PM +0900, Mike Hommey wrote:
>> >On Fri, Jan 16, 2015 at 10:28:51PM +0000, Steve McIntyre wrote:
>> >>
to you as the maintainer, but I'd be very tempted to file for
removal at this point.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"...In the UNIX world, people tend to interpret `non-technical user'
as meaning someone who's only ever written o
On Sat, Jan 17, 2015 at 04:16:56PM +0900, Mike Hommey wrote:
>On Fri, Jan 16, 2015 at 10:28:51PM +0000, Steve McIntyre wrote:
>> Hi Mike,
>>
>> Have you seen this again recently? Is it still happening for you?
>
>As a matter of fact, it hasn't happened rec
UB. What would be nice is a warning at
grub-install(?) time if lots of devices are needed for /boot: "your
system may not boot like this".
Mike: I'm afraid the only way you're going to get your system back
properly is to re-arrange your filesystems. Maybe re-shuffle th
d. I've personally at least encountered 3 people having problems
>with using USB media under desktop environments (KDE or GNOME) due to
>these entries in /etc/fstab.
I'm thinking the best way to go with this is to simply drop this misc
USB device support altogether from partm
* have it. Downgrading and retitling
appropriately. I'll see what I can do to add support for something
like that soon.
In a related(ish) sense, we could do with some similar extra work to
make EFI systems and RAID play nicely too... :-/
--
Steve McIntyre, Cambridge, UK.
1,
>Boot* Windows Boot Manager
>Boot0001* Windows Boot Manager
>Boot0002* grub
>Boot0003* debian
...
>
> 4534 drwxr-xr-x 2 root root 4096 1月 8 2014
> /boot/efi/EFI/Boot
> 455 1580 -rwxr-xr-x 1 root root 1617240 4月 27
\\0001\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 2084) =
>-1 ENOSPC (No space left on device)
>umask(0)= 022
...
That ENOSPC error is the cause of your problem - your firmware has
filled up the EFI variable space, so the system cannot add new EFI
variables. I suggest you look
Package: gnome-shell
Version: 3.14.2-3+b1
Severity: serious
Hi,
During testing of the Jessie d-i RC1 CD build, I installed lots and
lots of different variations of virtual systems using KVM. All the
others worked OK given sufficient packages (access to a mirror, etc.),
but installing Gnome on i38
to it, which is no bad thing. :-)
I was more tempted to do some version-detection code for eyeD3, but
this is safer right now I guess. Thanks!
--
Steve McIntyre, Cambridge, UK.st...@einval.com
The two hard things in computing:
* naming things
* cache invalidati
nd I'm not
>confident that dpkg will work fully/safely without all the POSIX-ish
>semantics (hardlinks, atomic updates and the like), might want to handle
>that by installing via the postinst instead of shipping in /boot/EFI.
Definitely, yes. dpkg directly on VFAT is a no-go.
--
St
d get a shim upload for
Jessie that still hasn't happened. :-( I now think it's now way too
late to add a new package like that for Jessie, hence I've been
continuing down this route.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"I used to
On Tue, Dec 16, 2014 at 02:45:47PM +, Steve McIntyre wrote:
>On Mon, Dec 15, 2014 at 01:38:34PM -0600, D. Jared Dominguez wrote:
>>
>>Once you test against unstable's efibootmgr, Peter Jones (upstream)
>>can help us try to triage this bug more.
>
>Same behav
are, I guess, and how important they
look. There are serious issues here, but not all of the changes are
just serious bugfixes AFAICS?
--
Steve McIntyre, Cambridge, UK.st...@einval.com
Into the distance, a ribbon of black
Stretched to the point of no turning back
On Mon, Dec 08, 2014 at 07:29:56PM +, Ian Campbell wrote:
>On Mon, 2014-12-08 at 01:36 +0000, Steve McIntyre wrote:
>> >The current package in sid (-17) is unblocked and I think ought to
>> >transition tomorrow (or perhaps Tuesday depending on TZ). I propose to
>> &
On Sun, Dec 07, 2014 at 04:38:37PM +, Ian Campbell wrote:
>Control: tag -1 +pending
>On Wed, 2014-12-03 at 15:27 +, Steve McIntyre wrote:
>>
>> Cool. I don't (think I) have push access to the git repo, so if you
>> could do the honours and apply, that would be
at somebody picked up jigdo-file and
maintained it I guess. I'll add it to my list.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"This dress doesn't reverse." -- Alden Spiess
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
-front and the upgrade did
*not* block in the same way.
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"I've only once written 'SQL is my bitch' in a comment. But that code
is in use on a military site..." -- Simon Booth
--
To UNSUBSCR
Package: upgrade-reports
Severity: serious
Hi,
Doing and upgrade in a VM. Started from a fairly minimal wheezy
system, then ran apt-get update and apt-get dist-upgrade to do the
upgrade. Things appeared to be running smoothly, until dpkg hung at
this point:
...
Unpacking libsepol1:amd64 (2.3-2)
On Wed, Dec 03, 2014 at 04:18:23PM +, Steve McIntyre wrote:
>
>A more generic fix would be to add to a list of filesystems that need
>unmounting, and trap to a new shell function that unmounts that
>list. Not too hard, I think - I'll see if I can do that and get it
>test
On Wed, Dec 03, 2014 at 09:44:08AM +, Ian Campbell wrote:
>On Wed, 2014-12-03 at 02:10 +0000, Steve McIntyre wrote:
>> >
>> >> +mountvirtfs () {
>> >> + fstype="$1"
>> >> + path="$2"
>> >> + if
On Wed, Dec 03, 2014 at 09:42:20AM +, Ian Campbell wrote:
>On Wed, 2014-12-03 at 01:55 +0000, Steve McIntyre wrote:
>> On Tue, Dec 02, 2014 at 08:36:31AM +, Ian Campbell wrote:
>> >On Mon, 2014-12-01 at 13:57 +0000, Steve McIntyre wrote:
>> >
>> >Start
On Tue, Dec 02, 2014 at 08:51:24AM +, Ian Campbell wrote:
>On Mon, 2014-12-01 at 13:57 +0000, Steve McIntyre wrote:
>
>grub-installer-rescue-UEFI-removable.patch:
>
>> diff --git a/debian/grub-installer.templates
>> b/debian/grub-installer.templates
>> index e4
On Tue, Dec 02, 2014 at 08:36:31AM +, Ian Campbell wrote:
>On Mon, 2014-12-01 at 13:57 +0000, Steve McIntyre wrote:
>
>Starting with grub-install-fallback.patch:
>
>> >From e384e597914b6e1b1dcbf96ef6782cf9bcc2313b Mon Sep 17 00:00:00 2001
>> debian/patches/grub-in
On Mon, Dec 01, 2014 at 03:52:51PM +0100, Cyril Brulebois wrote:
>Steve McIntyre (2014-12-01):
>> Control: severity 767037 serious
>> Control: tag 767037 +patch
>>
>> [ Raising severity to serious as I've heard more and more reports of
>> the problems here
Control: reassign -1 partman-efi
Gah, typos in package names... :-(
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"C++ ate my sanity" -- Jon Rabone
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubs
Package: partmen-efi
Severity: serious
Tags: d-i
Not sure if partman-efi is the right place for this bug to be filed,
but it's where things are showing up. Maybe parted is a better place?
Older versions of the installer (up to and including at least jessie
d-i alpha 1, 2014-03-18) use the correct
>it?
Definitely, *unless* you're actually providing a cleanly compatible
implementation in all respects - headers, libraries, API and ABI. If
you're not, then don't pretend to be in the packaging system.
--
Steve McIntyre, Cambridge, UK.st...@ein
201 - 300 of 518 matches
Mail list logo
