Hi,
The yast modules are submitted from account zypp-team, which has set
zypp-devel(a)suse.de as email. I can decline and comment as I want on such
requests - the mail to the submitter just bounces.
Please set the email of that account to something actually read - either
by an actual team or by someone who's responsible for the submission.
The current case is https://build.opensuse.org/request/show/211153 -
there is no name associated with that request I can email to ;(
Greetings, Stephan
--
"Someone's been mean to you! Tell me who it is, so I can punch him
tastefully."
-- Ralph Bakshi's Mighty Mouse
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
we have discussed serial console support several times at the meetings,
without much output (except "it should work") without any idea about testing.
I found out that VirtualBox supports also serial port emulation which can
be used for emulating a serial console.
Here is a short HowTo for emulating a serial console in VirtualBox:
- Install "socat" utility ("zypper in socat", it's included in 12.3 and 13.1)
- Create a new virtual machine in VBox, configure it for installing the requested
product (i.e. add the selected ISO image as a virtual CD drive)
- In "Settings" -> "Serial Ports" set "Enable Serial Port", "Port Number": COM1,
"Port Mode": "Host Pipe"
Select "Create Pipe" checkbox, enter path to the created pipe file in
"Port/File Path" (e.g. "/tmp/com1")
- Boot the machine
- In the host run command "socat unix-connect:/tmp/com1 stdio,raw,echo=0,icanon=0"
in a terminal (replace "/tmp/com1" by the path set in the serial port config)
- In the VM boot prompt add "console=ttyS0,115200" option (or you can enter that
using the text menu in the serial console)
- Start the installation
- You should see the boot process and then textmode Yast installer in the serial
console terminal. Install the system as usually, there is nothing specific to
serial console installation (besides it is in textmode).
I have tested the latest NI ISO image and the installation was successful!
After reboot you can log into the machine using the serial console as well.
Summary: The feature still works, we just need to check it later once again
(in some Beta, to make sure we did not break it).
--
Ladislav Slezák
Appliance department / YaST Developer
Lihovarská 1060/12
190 00 Prague 9 / Czech Republic
tel: +420 284 028 960
lslezak(a)suse.com
SUSE
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
[ This change was already done some time ago, I just forgot to announce it.
This announcement is mainly important for the community developers. ]
Introduction
------------
For SLE12/openSUSE-13.2 we switched from *.spec.in files (which were processed by
"create-spec" script from devtools during "make package-local")
to directed *.spec stored in Git.
This is needed because of the new CI integration (it uses "osc build" as a backend
for testing build and we need an easy way to get *.spec, the old way was too
complicated).
This will also make the future maintenance easier, now for generating the *.spec
for SLE11 you need SLE11 devtools which is the most tricky part when preparing a
maintenance update. With *.spec files stored directly in Git this problem is gone...
Moving from *.spec.in to *.spec
--------------------------------
The *.spec.in files provided a flexibility by using some macros which were expanded
by "create-spec". To keep this flexibility we moved the shared code to RPM macros [1]
which is a clean and standard RPM way.
I did the move for most of Yast packages (I skipped the unmaintained/obsolete ones),
but some 3rd party modules will be missing the transition so here is a quick HowTo:
- move *.spec.in to package/*.spec
- replace the @MACROS@:
- @HEADER-COMMENT@ and @HEADER@: replace by the content generated by "create-spec",
look at the generated *.spec or see the generator[2]
- the rest should be replaced by the respective RPM tag and an Yast RPM macro,
see the example in yast2 [3]
- replace the macros also in the %files section (again, see the example)
- @CLEAN@ can be removed (not needed)
- update the BuildRequires dependency to "yast2-devtools >= 3.0.6" (contains the new
RPM macros)
(You could simply use the *.spec generated by "create-spec" script but that's not
recommended, it will miss some future changes as the RPM macros can be updated in the
future.)
If you have any questions or problems with transition in your module then just ask.
[1] https://github.com/yast/yast-devtools/blob/master/build-tools/rpm/macros.ya…
[2] https://github.com/yast/yast-devtools/blob/openSUSE-13_1/devtools/bin/creat…
[3] https://github.com/yast/yast-yast2/commit/e0a77efcfa4feb16dfb2c88779f313b9e…
--
Ladislav Slezák
Appliance department / YaST Developer
Lihovarská 1060/12
190 00 Prague 9 / Czech Republic
tel: +420 284 028 960
lslezak(a)suse.com
SUSE
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
we stored the package version at two places, in VERSION and spec files,
and this lead to inconsistencies because people usually forgot to update the *.spec
files after changing the VERSION file.
I have modified the yast rake tasks and devtools to read the
version directly from *.spec.
And I also removed VERSION files from all Git repositories[1].
(I did it directly in master after approving one commit,
opening 100+ the same pull requests would be useless...)
You need to install rubygem-yast-rake-0.1.5 and yast2-devtools-3.1.10 packages
(or newer) from YaST:Head to make it work properly.
Since now, if you want to update the package version edit the spec files directly
or simply run 'rake version:bump'.
If you find any problem related to missing VERSION just let me know.
Enjoy!
[1] Here is the list of affected repositories
(obsoleted repos or repos not containing VERSION were skipped):
add-on
add-on-creator
apparmor
audit-laf
autoinstallation
bootloader
ca-management
cluster
control-center
control-center-gnome
country
crowbar
dbus-server
dhcp-server
dns-server
drbd
fcoe-client
firewall
firstboot
ftp-server
geo-cluster
hardware-detection
http-server
inetd
installation
instserver
iplb
iscsi-client
iscsi-lio-server
iscsi-server
isns
kdump
kerberos-client
kerberos-server
ldap
ldap-client
ldap-server
live-installer
lxc
mail
mail-server
metapackage
multipath
network
nfs-client
nfs-server
nis-client
nis-server
ntp-client
online-update
online-update-configuration
openvas-security-scanner
packager
pam
perl-bindings
pkg-bindings
pos-installation
printer
product-creator
proxy
python-bindings
rdp
rear
reipl
ruby-bindings
samba-client
samba-server
scanner
security
services-manager
schema
slepos-image-builder
slepos-system-manager
slide-show
slp
slp-server
snapper
sound
squid
storage
sysconfig
s390
testsuite
tftp-server
theme
transfer
tune
update
users
vm
wagon
xml
x11
yast2
ycp-ui-bindings
--
Ladislav Slezák
Appliance department / YaST Developer
Lihovarská 1060/12
190 00 Prague 9 / Czech Republic
tel: +420 284 028 960
lslezak(a)suse.com
SUSE
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
I'm looking for documentation or a guide on how to write a yast module. Is
there anything available? Or is there a module you'd recommend to look at first?
Regards,
Nanuk
--
Nanuk Krinner - Systems Management Engineer
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
Tel: +49-911-74053-577 - nkrinner(a)suse.de
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org