Occasionally I see a comment "Please test the attached patch" and would like
to do it, usually because it is one lacking broad applicability, and I have
the necessary hardware. https://bugs.freedesktop.org/show_bug.cgi?id=66462
contains one such. https://en.opensuse.org/openSUSE:Build_Service_Tutorial to
non-programmer me looks hopelessly intimidating even via web client. Is it
really as complicated as it seems to apply a patch adding five new lines and
removing one? Is there a shortcut available?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-testing+owner(a)opensuse.org
HTTP method 32 bit minimal X with custom package selection, started with Grub:
install=http://widehat.opensuse.org/factory-snapshot/repo/oss/
hostname=myhost hostip=192.168.1.2/24 gateway=192.168.1.1 nameserver=8.8.8.8
net.ifnames=0 namescheme=by-label kexec_reboot=0 ipv6.disable=1 noresume
video=1152x864@60 vga=794
I had never used net.ifnames=0 before, having installed many times the 4
milestones on multiple machines.
1-I used widehat instead of download because download would not resolve
and/or some of its dirs were redirected to a 404 page
Other than those two things, the startup Grub stanza was as it usually is here.
Among the many packages tabooed was mdadm, a superfluous partner in
https://bugzilla.novell.com/show_bug.cgi?id=786318, which caused breaking
something to do with YaST. Installation seemed to go well until main package
installation process completed, after which several error windows popped up.
To the best of my recollection:
2-~"cannot write resolv.conf"
3-Grub installation failed (yet usable menu.lst was present)
4-mkinitrd reported to have failed (yet working initrd was installed)
Following first boot after some manual configuration booted to 12.3:
5-yast2-firstboot had not been installed (because of mdadm absence?), so did
not run
6-resolv.conf was 0 bytes
7-no /etc/sysconfig/network/routes was created
8-no /etc/udev/rules.d/70-persistent-net.rules was created
9-in spite of local time automatically selected, and retained, during early
installation phase, /etc/adjtime contained UTC instead of LOCAL
10-no networking until manual intervention with 70-pers..., routes,
resolv.conf, etc. and restart.
y2logs stand at the ready, but what if any bug(s) to file?
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-testing+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-testing+owner(a)opensuse.org
