January 2017 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 312337] clear /tmp-dir at bootup
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: M K (tux93) Feature #312337, revision 1 Title: clear /tmp-dir at bootup openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: M K (tux93) Partner organization: openSUSE.org Description: Please clear the /tmp-dir at boot-up per default. At the moment this has to be activated manually with every new installation, is there a reason for not doing this out of the box? -- openSUSE Feature: https://features.opensuse.org/312337

1 6

[New: openFATE 309487] Clean out X11 keyboard configuration in YaST
by fate_noreply＠suse.de 24 May '17

24 May '17

Feature added by: Jiří Suchomel (jsuchome) Feature #309487, revision 1 Title: Clean out X11 keyboard configuration in YaST Requested by: Jiří Suchomel (jsuchome) Developer: (Novell) Developer: (Novell) Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2-tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 -- openSUSE Feature: https://features.opensuse.org/309487

1 16

[New: openFATE 320834] Create a /var/cache subvolume
by fate_noreply＠suse.de 17 May '17

17 May '17

Feature added by: Thorsten Kukuk (kukuk) Feature #320834, revision 1 Title: Create a /var/cache subvolume Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org Description: On the openSUSE Factory list, somebody found a valid bug in our current setup for snapshots: /var/cache is part of the snapshot. This means: all RPMs used for an update are part of the snapshot and will be deleted only afterwards. This is a big problem if you regular update online, it will eat up your diskspace very fast. We need to add /var/cache to the list of directories, for which we create a subvolume with btrfs. And (that's why I created a FATE and no bug) we need to add something to the release notes, so that customers are aware of this and can create the subvolume at their own for existing installations. Business case (Partner benefit): openSUSE.org: Save disk space by excluding irrelvant/outdated cached data from snapshots. -- openSUSE Feature: https://features.opensuse.org/320834

1 28

[New: openFATE 320819] DHCPv6-PD - wicked
by fate_noreply＠suse.de 11 May '17

11 May '17

Feature added by: James Knott (james_knott) Feature #320819, revision 1 Title: DHCPv6-PD - wicked openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: James Knott (james_knott) Partner organization: openSUSE.org Description: With more & more ISPs providing IPv6 via DHCPv6, DHCPv6-PD support is essential. This is how a router determines the assigned prefix via DHCP. Later versions of dhcpc support DHCPv6-PD, but wicked apparently doesn't. https://tools.ietf.org/html/rfc3633 -- openSUSE Feature: https://features.opensuse.org/320819

1 3

[New: openFATE 319119] drop not functional yast2-ca-management
by fate_noreply＠suse.de 08 May '17

08 May '17

Feature added by: Michael Calmer (mcalmer) Feature #319119, revision 1 Title: drop not functional yast2-ca-management Requested by: Michael Calmer (mcalmer) Partner organization: openSUSE.org Description: yast2 ca-management cannot be maintained anymore. No resources. So let's drop it. -- openSUSE Feature: https://features.opensuse.org/319119

1 12

[New: openFATE 322036] Move logrotate.status to /var/lib/misc
by fate_noreply＠suse.de 19 Apr '17

19 Apr '17

Feature added by: Thorsten Kukuk (kukuk) Feature #322036, revision 1 Title: Move logrotate.status to /var/lib/misc Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org Description: logrotate.status is in /var/lib. Which is a problem if the root filesystem is read-only like for CASP. Making /var/lib read-write is impossible without breaking snapshots, rollback and transactional updates on all products, not only CASP. According to FHS/LSB, no application is allowed to create single files in /var/lib anyways, the correct directory is /var/lib/misc. Which is writeable. So the logrotate.status file should be moved. -- openSUSE Feature: https://features.opensuse.org/322036

1 5

[New: openFATE 309353] Make hermes working on local OBS installations
by fate_noreply＠suse.de 18 Apr '17

18 Apr '17

Feature added by: Adrian Schröter (adrianSuSE) Feature #309353, revision 1 Title: Make hermes working on local OBS installations Buildservice: Evaluation Priority Requester: Important Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Description: We need to * be able to run without iChain * package Hermes * configure it to be easy usable with OBS. -- openSUSE Feature: https://features.opensuse.org/309353

1 2

[openFATE 307597] Courgette
by fate_noreply＠suse.de 18 Apr '17

18 Apr '17

Feature added by: T. J. Brumfield (enderandrew) Feature #307597, revision 1 Title: Courgette openFATE: Unconfirmed Priority Requester: Important Requested by: T. J. Brumfield (enderandrew) Description: Utilize Courgette for binary diff packages. * This will save on bandwidth costs for Novell and mirrors. * This will make updating quicker and easier for end-users. * This will especially benefit users who have capped bandwidth for downloading updates from their ISPs. * By making the update process easier, it encourages users to stay up-to-date, making systems more secure. http://dev.chromium.org/developers/design-documents/software-updates-courge… (http://dev.chromium.org/developers/design-documents/software-updates-courge…) -- openSUSE Feature: https://features.opensuse.org/307597

1 7

[New: openFATE 309701] osc blame
by fate_noreply＠suse.de 18 Apr '17

18 Apr '17

Feature added by: Ludwig Nussel (lnussel) Feature #309701, revision 1 Title: osc blame Buildservice: Unconfirmed Priority Requester: Desirable Requested by: Ludwig Nussel (lnussel) Description: a feature like "osc blame" or "osc annotate" would be nice to find out who changed what and when -- openSUSE Feature: https://features.opensuse.org/309701

1 3

[New: openFATE 313282] Full automated setup for printers in the network
by fate_noreply＠suse.de 20 Mar '17

20 Mar '17

Feature added by: Johannes Meixner (jsmeix) Feature #313282, revision 1 Title: Full automated setup for printers in the network openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: Johannes Meixner (jsmeix) Partner organization: openSUSE.org Description: I would like to have it evaluated whether or not and/or to what extent it is possible to setup printer devices which are accessible via network in a full automated way. The basic idea behind: For locally connected USB printers there is already full automated setup. I would like to have it evaluated if and/or to what extent this could be extended reagarding printer devices which are accessible via network. FYI: For printer devices which are accessible via a CUPS server there is nothing to do because this works already via the so called "CUPS Browsing". Some use cases: Network printer) A network printer is a printer with a built-in network interface so that the printer device is directly accessible via network. The problem regarding full automated setup is how to autodetect the printer model so that the right driver for this model can be set up. Therefore the problem is how to autodetect the parinter model on a printer device which is directly accessible via network. Usually this is possible via some generic SNMP query. The CUPS tool "lpinfo -l -v" results this for the "socket" device URI e.g.: # lpinfo -l -v Device: uri = socket://10.10.2.92 make-and-model = HP LaserJet 4050 Series Device: uri = lpd://10.10.4.4/ make-and-model = Kyocera FS-C5100DN SMB) A printer device which is accessible via a SMB printer share: In this case the client system must submit readymade printer specific data to the SMB share (i.e. there is no so called "filtering" on a SMB print server). Therefore on the client system usually a printer driver must run. If it is a PostScript printer, the client must at least provide generic PostScript (e.g. when printing image data it must be converted into PostScript on the client system). The problem regarding full automated setup is how to autodetect the printer model so that the right driver for this model can be set up but the printer device is "hidden" behind the SMB share. Therefore the problem is how to autodetect the parinter model via a SMB share. -- openSUSE Feature: https://features.opensuse.org/313282

1 10