On 13 August 2014 14:25, Luiz Fernando Ranghetti wrote:

Hi,

Very nice summary!

Just for curiosity, all BNCs listed on it give us Acess Denied :)

Regards,

Luiz

That's an unfortunately side effect of the bugs originating from SUSE's work on the upcoming SUSE Linux Enterprise version 12 - Bugs filed against SLE* are typically private as they may contain things like customer information which probably shouldn't have a wide audience. When those bugs get fixed in SLE* and those fixes incorporated into openSUSE Factory, that's great for for openSUSE, but yes, the bugs typically remain private even though the bug ID's end up in the changelogs I know it's not ideal. The 'easy' (tongue-in-cheke) solution would be to make sure that more people get openSUSE Factory..if openSUSE finds and files all the bugs first, they'll be public bugs and those are the references that should end up in changelogs More seriously, this is something I'm keen to work on and I'm open to suggestions Regards, Richard

2014-08-13 3:55 GMT-03:00 Ludwig Nussel :

...

Changed packages:

==== dnsmasq ====

- Removed Suse and all other OS/Distribution related subdirs from contrib, so only the rest gets packaged. The subdirs are not necessary anymore (bnc#889028). - Removed README.SUSE file, it was to confusing and not necessary (bnc#889972). Information is already present in the upstream documentation. - Split up vendor-files.tar.bz2 into single files - Comply with systemd packaging guidlines

==== kiwi ==== Version update (5.06.142 -> 5.06.145) Subpackages: kiwi-desc-isoboot kiwi-desc-netboot kiwi-desc-oemboot kiwi-desc-vmxboot kiwi-doc kiwi-media-requires kiwi-pxeboot kiwi-templates kiwi-tools

- v5.06.145 released - Added missing handling for recommends in the libsolv path Also fixed passing the patternType value from the XML to the solver module - v5.06.144 released - Fix report files generated by KIWICollect.pm The report files were reduced to only one package per included architecture, everything else was discarded. Fix done by Ruediger Oertel - v5.06.143 released - Update JeOS templates for SLE12 and openSUSE 13.2 * pass splash to the kernel cmdline in order to display the default plymouth splash - Fixed kiwi --describe command * wrong metadata reference still in the code due to a rename * make sure exit code is set correctly * fixed broken jpg menu icons

==== libproxy-devel ==== Subpackages: libproxy1

- Change Supplements to install libproxy1-config-gnome3 only if gnome-session-core is installed to reduce minimal install size (bnc#885455).

==== libproxy1-config-gnome3 ==== Subpackages: libproxy1-config-kde4 libproxy1-networkmanager libproxy1-pacrunner-webkit

- Change Supplements to install libproxy1-config-gnome3 only if gnome-session-core is installed to reduce minimal install size (bnc#885455).

==== parcellite ====

- update to version 1.1.8 revision 532 to fix several bugs * Fixed bug 120, position_history broken. We limit x & y with screen limit -100. * Fixed Bug 123, right-click edit broken. * Fixed bug 124, Enter does not select entry. * Fixed bug 125, Unsolicited error message about xdotool. * Fixed bug 130, Edit clipboard and Clear aren't working in Parcellite 1.1.8 * Added feature request 57, change systray icon. * Updated Spanish translation by jcsl. + it makes parcellite-1.1.7-Spanish-translation-update.patch unnecessary ~> removed * Updated Chinese translation by wenjie. * Cleaned up many warnings. + it makes parcellite-1.1.8-rpmlint-errors.patch unnecessary ~> removed

==== pciutils-ids ====

- update pci.ids to version 2014.08.06 (bnc#885212)

==== polkit-default-privs ====

- polkit-defaultprivs: relaxing rules for SLE12 create-profile in colord (bnc#887511)

==== rubygem-mysql ====

- Rename rpmlintrc to %{name}-rpmlintrc (and remove wrongly named rubygem-mysql.rpmlintrc) Follow the packaging guidelines.

==== yast2-dhcp-server ==== Version update (3.1.2 -> 3.1.3)

- bnc#887139 - selected device has to have an ip assigned. - 3.1.3

==== yast2-ftp-server ====

- Enabled YARD docs, documented the basics of FtpServer.

==== yast2-ldap ==== Version update (3.1.11 -> 3.1.12)

- Set member_attribute to 'member'. We only use rfc2307bis.schema - bnc#889556 - yast2 users can not create ldap groups - 3.1.12

==== yast2-security ==== Version update (3.1.3 -> 3.1.4)

- Speedup Security.ReadServiceSettings (bnc#890349) - Drop obsolete runlevel parameter from some methods - 3.1.4 Removed packages:

Added packages:

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, Aug 13, 2014 at 03:04:52PM +0200, Jan Engelhardt wrote:

On Wednesday 2014-08-13 14:42, Richard Brown wrote:

...

...

Just for curiosity, all BNCs listed on it give us Acess Denied :)

That's an unfortunately side effect of the bugs originating from SUSE's work on the upcoming SUSE Linux Enterprise version 12

More seriously, this is something I'm keen to work on and I'm open to suggestions

Ask the submitter to kindly make his bug report public if possible. A checkbox or something.

Actually, in https://bugzilla.novell.com/enter_bug.cgi?product=openSUSE%20Factory there is already a set of checkbox at the bottom

[ ] This bug is only open to ...

maybe the SLE user just has a different preselection and needs to uncheck it.

No, the SLES product itself is only readable to Novell employees and partners, it is not just a checkbox. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, Aug 13, 2014 at 02:42:35PM +0200, Richard Brown wrote:

On 13 August 2014 14:25, Luiz Fernando Ranghetti wrote:

...

Very nice summary!

Just for curiosity, all BNCs listed on it give us Acess Denied :)

That's an unfortunately side effect of the bugs originating from SUSE's work on the upcoming SUSE Linux Enterprise version 12 - Bugs filed against SLE* are typically private as they may contain things like customer information which probably shouldn't have a wide audience.

But not all these details are confidential. And it causes extra work and irritates community members. It's not the first time people raise this kind of question.

When those bugs get fixed in SLE* and those fixes incorporated into openSUSE Factory, that's great for for openSUSE, but yes, the bugs typically remain private even though the bug ID's end up in the changelogs

I know it's not ideal.

The 'easy' (tongue-in-cheke) solution would be to make sure that more people get openSUSE Factory..if openSUSE finds and files all the bugs first, they'll be public bugs and those are the references that should end up in changelogs

More seriously, this is something I'm keen to work on and I'm open to suggestions

As soon as a product got released bug reports should be opened. If there is still some critical detail included with the report we're able to mark a comment as private. But this approach might not work in all cases. An alternative would be to file an extra and open bug report for openSUSE and reference only this one in the package change log. The SUSE internal one would get a reference to the public one. Cheers, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-08-13 15:13, Lars Müller wrote:

An alternative would be to file an extra and open bug report for openSUSE and reference only this one in the package change log. The SUSE internal one would get a reference to the public one.

Then somebody has to hand-copy the information from one report to the other. It will not do if the /open/ report contains no useful information, which is written in the /closed/ report and inaccessible - - irritating community members even further. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlPrzv8ACgkQtTMYHG2NR9UbRQCeLB0uPSLxCXjIRLW1s/v4lESz QgUAniPe4yqfRN9SnEWHp+u2lk6wqchR =lvV9 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wed, Aug 13, 2014 at 10:47:59PM +0200, Carlos E. R. wrote:

On 2014-08-13 15:13, Lars Müller wrote:

...

An alternative would be to file an extra and open bug report for openSUSE and reference only this one in the package change log. The SUSE internal one would get a reference to the public one.

Then somebody has to hand-copy the information from one report to the other. It will not do if the /open/ report contains no useful information, which is written in the /closed/ report and inaccessible - - irritating community members even further.

Only if something important happened in the public report the bug assigne has to add a pointer to it in the private defect report. As any comment is referenceable with an URL this wouldn't cause much work. There is no need to copy each and every piece over. And I know what I'm speaking about as I'm following this approach already. It doesn't cause much extra work. The goal with this suggestion was to keep all in the loop and to ease the exchange between these two sometimes quite different entities. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team + SUSE Labs SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

В Wed, 13 Aug 2014 14:42:35 +0200 Richard Brown пишет:

On 13 August 2014 14:25, Luiz Fernando Ranghetti wrote:

...

Hi,

Very nice summary!

Just for curiosity, all BNCs listed on it give us Acess Denied :)

Regards,

Luiz

That's an unfortunately side effect of the bugs originating from SUSE's work on the upcoming SUSE Linux Enterprise version 12 - Bugs filed against SLE* are typically private as they may contain things like customer information which probably shouldn't have a wide audience.

When those bugs get fixed in SLE* and those fixes incorporated into openSUSE Factory, that's great for for openSUSE, but yes, the bugs typically remain private even though the bug ID's end up in the changelogs

I know it's not ideal.

The 'easy' (tongue-in-cheke) solution would be to make sure that more people get openSUSE Factory..if openSUSE finds and files all the bugs first, they'll be public bugs and those are the references that should end up in changelogs

Are openSUSE bugs treated with the same priority as SLE bugs? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Thu, Aug 14, 2014 at 5:31 AM, Cristian Rodríguez wrote:

El 13/08/14 a las #4, Ludwig Nussel escribió:

...

Changed packages:

The second stage of the installation from a live KDE medium has been failing for me since quite a while.. orange dialog pops up right after the first reboot and the installer just returns to the first stage on a loop... anyone has the bug number about this issue ?

http://shrib.com/yast2-live-installer-bugs-workarounds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Thu, Aug 14, 2014 at 2:43 PM, Ludwig Nussel wrote:

Jigish Gohil schrieb:

...

On Thu, Aug 14, 2014 at 5:31 AM, Cristian Rodríguez wrote:

...

El 13/08/14 a las #4, Ludwig Nussel escribió:

...

Changed packages:

The second stage of the installation from a live KDE medium has been failing for me since quite a while.. orange dialog pops up right after

I don't know why but the live installer currently not tested in openQA so it's failures are not on the radar.

...

...

the first reboot and the installer just returns to the first stage on a loop... anyone has the bug number about this issue ?

http://shrib.com/yast2-live-installer-bugs-workarounds

Great :-) Would you mind filing submit requests for openSUSE:Factory:Live so we get the released images in shape again?

Factory:Live images are not created same way as the ones in GNOME:Live and KDE:Live, they use kiwi image building feature of OBS, Factory one calls kiwi from within normal .spec file. and those just have workarounds in kiwi's config at the moment, the bugs have to be fixed in relevant packages. There was a talk of dropping live-installer as it is not maintained, these images are just as proof that live-installer is working and does not need any fix, it is other pieces around it that changed breaking it.

At the moment the live DVD doesn't boot at all anymore: https://openqa.opensuse.org/tests/17665

kiwi bug?

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Fri, Aug 15, 2014 at 11:44 AM, Ludwig Nussel wrote:

No matter where the problem turns out to be in the end, the problem is to find someone to take care, debug and fix the issues :-) At the moment the live images don't boot in live mode either: https://openqa.opensuse.org/tests/17940/modules/finish_desktop/steps/1

Do you have an idea how to debug that? If so could you take a look please?

Boot the iso with kiwidebug=1, then cat /var/log/boot.kiwi It is missing mkfs.ext3 in the initrd(created by kiwi), I have no idea why it is missing in factory iso and not gnome-next/plasma5 isos. Cheers -J -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Fri, Aug 15, 2014 at 4:25 PM, Stefan Seyfried wrote:

Am 15.08.2014 um 12:12 schrieb Jigish Gohil:

...

It is missing mkfs.ext3 in the initrd(created by kiwi), I have no idea why it is missing in factory iso and not gnome-next/plasma5 isos.

I just tried to try your plasma-next iso and it did not work, too. Did not debug it, though but went back to 13.1 (I just needed *any* live usb stick...)

Yeah, those are now broken also, so this is some very recent change in kiwi that has removed the required tools from the initrd. http://download.opensuse-education.org/~cyberorg/openSUSE-13.2-livecd-gnome.... is created before this breakage in kiwi. Cheers -J -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Mon, Aug 18, 2014 at 1:13 PM, Ludwig Nussel wrote:

And the console fonts are broken: https://openqa.opensuse.org/tests/18221/modules/yast2_lan/steps/2

https://openqa.opensuse.org/tests/18398/modules/yast2_i/steps/2 shows up fine, and yast2 lan look fine in qemu and virtualbox locally here, may be it is something in qemu setup in openqa. Lot of other tests showing failed also seems to be wrong due to low timeout? for example, kate, firefox, office etc. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org