| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Including Xsun, silo & yaboot support
Rationale: it's unused/unmaintained for years and those arches are beyond
any hope of being usefull any day...
They just got in the way...
Part of IA64 support is still kept (eg: support for GPT, EFI, right xorg
driver at install, ...) as it might be usefull to extend to other arches
Next to consider: Xbox?
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
we lack the new ones introduced in 3.13...
|
| |
|
|
|
|
|
| |
*** Gtk3::Widget::set_default_direction: passed too many parameters (expected 1, got 2); ignoring excess at /usr/lib/libDrakX/install/gtk.pm line 74.
* error: FATAL: invalid enum GtkTextDirection value Gtk3::Widget, expecting: none / GTK_TEXT_DIR_NONE, ltr / GTK_TEXT_DIR_LTR, rtl / GTK_TEXT_DIR_RTL at /usr/lib/perl5/vendor_perl/5.18.2/i386-linux-thread-multi/Glib/Object/Introspection.pm line 59.
|
|
|
|
|
|
|
| |
Fixes chown'ing user to root when adding existing user
on upgrade.
mga#12375
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The issue being that the help process doesn't know about $::prefix being
/mnt... So we moved the screenshots several times :-(
$ xzgrep fb2png report.bug.xz
* running: fb2png /dev/fb0 /tmp/DrakX-screenshots/1.png 0
* running: fb2png /dev/fb0 //root/DrakX-screenshots/2.png 0
* running: fb2png /dev/fb0 /tmp/DrakX-screenshots/1.png 0
* running: fb2png /dev/fb0 /tmp/DrakX-screenshots/2.png 0
* running: fb2png /dev/fb0 //root/DrakX-screenshots/3.png 0
* running: fb2png /dev/fb0 /tmp/DrakX-screenshots/1.png 0
* running: fb2png /dev/fb0 /tmp/DrakX-screenshots/2.png 0
* running: fb2png /dev/fb0 //root/DrakX-screenshots/4.png 0
* running: fb2png /dev/fb0 /tmp/DrakX-screenshots/1.png 0
* running: fb2png /dev/fb0 /tmp/DrakX-screenshots/2.png 0
* running: fb2png /dev/fb0 //root/DrakX-screenshots/5.png 0
* running: fb2png /dev/fb0 /tmp/DrakX-screenshots/1.png 0
* running: fb2png /dev/fb0 /tmp/DrakX-screenshots/2.png 0
* running: fb2png /dev/fb0 /tmp/DrakX-screenshots/3.png 0
* running: fb2png /dev/fb0 /tmp/DrakX-screenshots/4.png 0
* running: fb2png /dev/fb0 /tmp/DrakX-screenshots/5.png 0
* running: fb2png /dev/fb0 /tmp/DrakX-screenshots/6.png 0
* running: fb2png /dev/fb0 /mnt/root/DrakX-screenshots/7.png 0
* running: fb2png /dev/fb0 /mnt/root/DrakX-screenshots/8.png 0
* running: fb2png /dev/fb0 /mnt/root/DrakX-screenshots/9.png 0
* running: fb2png /dev/fb0 /mnt/root/DrakX-screenshots/10.png 0
(...)
|
|
|
|
| |
first screenshot already exists by this time...
|
| |
|
| |
|
|
|
|
|
| |
as help runs in a one shot process, it doesn't remember the warning has
already been done
|
| |
|
| |
|
|
|
|
|
|
| |
reverting commit 6861dc0526938a22da627308591d652b05b8fbf6
this should results in better sizing if there's a lot a small partitions
as oxygen's ToggleButtons minimum width is bigger
|
| |
|
|
|
|
| |
reverting commit 54dd9e586b59fdacb54bcd2f78d29870d00b1f3e
|
|
|
|
| |
reverting commit 6861dc0526938a22da627308591d652b05b8fbf6
|
|
|
|
|
|
| |
regression introduced in commit fadc8b97ed98977bf264d87d62c33e779f299716
sadly flickering may happen
|
|
|
|
|
| |
ratio would be negative when allocated width was reported as 1 in some
cases since commit 807df2a2b558461a2890f9bec0050f0bd974c92e
|
|
|
|
|
|
| |
thus fixing "basesystem package not selected"
real cause might be some package flags not having been updated
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
screenshots were not working since we moved the actual display of help
in another program.
Switch to install mode and make sure we've a real $::o object.
Today is Marja's birthday!
|
| |
|
|
|
|
| |
should prevent window to move at install time
|
| |
|
| |
|
|
|
|
| |
this error happens when inspecting partitions
|
|
|
|
|
|
|
|
|
|
| |
Basically, there seems to be an issue right now if we do lots of reloads.
It seems to be somewhat racy and systemd gets generally confused when we
do this during boot (which we do) and trigger a reload. The reload isn't
strictly needed, as we do also explicitly start the services we enable
(with --no-block so that we don't cause a deadlock) so all *should* be
99% OK. Using it at runtime might mean we don't have fully up-to-date
enablement status, but being able to boot wins at the moment.
|
| |
|
|
|
|
| |
if it's not enough, we will disable labels on partitions buttons again
|
|
|
|
|
|
|
| |
rationale: it doesn't fix diskdrake issues (mga#11977) whereas it
doesn't draw window decorations w/o any window manager (mga#12218)
basically reverting commit 19a11905a998a1e62fb8f32aeb749f1b5a9bafd6
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
in order to try to workaround diskdrake issues (mga#11790, mga#11989, ...)
as a side effect, stage2 shrinks by 3Mb...
|