February 2015 - openSUSE Users - openSUSE Mailing Lists

RE: [opensuse] RE: Bug Report Zebra 2.0.60 in favour of Zebra 2.0.59 (package idzebra-2.0)
by David Cook 10 Feb '15

10 Feb '15

Thanks for the info, Greg! Bjørn Lie got in touch with me yesterday and was very helpful as well. He gave me the name of the package maintainer, provided a link to a Zebra update he’d already prepared (I think he’d done updates for Zebra in the past as well), and encouraged me to report the bug! At this point, the package maintainer (Karl Eichwalder) has accepted the update request, and forwarded it on to maintenance! I’m not 100% sure where things go from now… I imagine QA then inclusion in a maintenance release of some kind, so that’s a really positive outcome. I didn’t realize that my Bugzilla login would work at build.opensuse.org as well, so that’s good to know! Maybe I’ll contribute more down the road if anything comes up! David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 From: Greg Freemyer [mailto:greg.freemyer@gmail.com] Sent: Wednesday, 11 February 2015 12:09 AM To: David Cook; opensuse(a)opensuse.org Subject: Re: [opensuse] RE: Bug Report Zebra 2.0.60 in favour of Zebra 2.0.59 (package idzebra-2.0) On Monday, February 9, 2015, <greg.freemyer(a)gmail.com> wrote: On February 9, 2015 12:15:50 AM EST, David Cook <dcook(a)prosentient.com.au> wrote: >Hi OpenSuse folks: > >This is my first time interacting with OpenSuse in any way, so I'm not >entirely sure how to go about it. > >Basically, last week I discovered a bug in Indexdata's search engine >Zebra >(package name idzebra-2.0). I filed the bug with Indexdata, and they >released a fix as part of their 2.0.60 release of idzebra-2.0. > >At the moment, we're using OpenSuse 13.2 and version 2.0.59 of >idzebra-2.0, >which we installed using Zypper. > >I'm wondering what the process would be for filing a bug report to >either >upgrade the packages in the package repo for OpenSuse 13.2 or whether >it >would be possible to backport the patch. > >A colleague of mine at a different company recently opened a bug with >Debian >(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777515) which has >all the >relevant information. Basically, tokenization doesn't work correctly in >Zebra 2.0.59 when using ICU indexing. Only the first token would be >used >after the search terms were tokenized when a hyphen existed in a search >term. > >Indexdata only packages Zebra for Debian, Ubuntu, and Redhat, so >ideally >we'd like to use the packages available via the OpenSuse repos rather >than >building from source. > >Please let me know what I need to do. Thanks! > >David Cook >Systems Librarian >Prosentient Systems >72/330 Wattle St, Ultimo, NSW 2007 (Just found this in my drafts) Welcome to openSUSE! See https://en.opensuse.org/openSUSE:Submitting_bug_reports And https://en.opensuse.org/openSUSE:Bug_reporting_FAQ Also, openSUSE is extremely welcoming to contributors, so if you have the technical skills, you can use your bugzilla login to also login to build.opensuse.org and prepare an update to the development version of the package yourself. You do the preparation in your home project, then submit it to the development project. A maintainer will review your work and either accept it or provide feedback about what you need to correct before it accepted. Greg -- -- Greg Freemyer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] how to run a script after mkinitrd
by Michael J Dur 10 Feb '15

10 Feb '15

I have a script that I need to run after mkinitrd. I see in opensuse we have /lib/mkinitrd/scripts and /lib/mkinitrd/setup When I symlink my script into /lib/mkinitrd/setup/ it runs, but is removed (presumably by mkinitrd) after a couple runs. Is this an appropriate place to have a script run after mkinitrd, and if so, how can I allow my symlink to stay? Thanks in advance! -Michael -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] scrambled mdraid setup
by Felix Miata 10 Feb '15

10 Feb '15

I built a new RAID1 using 13.1 YaST2 partitioner. This is the slightly condensed output from mdadm --detail --scan, with appended the 2 sda/sdb partitions making up each device: ARRAY /dev/md/md-tmp metadata=1.0 name=srv10:md-tmp UUID=... # P08 ARRAY /dev/md/mdroot1 metadata=1.0 name=srv10:mdroot1 UUID=... # P09 ARRAY /dev/md/mdroot2 metadata=1.0 name=srv10:mdroot2 UUID=... # P10 ARRAY /dev/md/mdroot3 metadata=1.0 name=srv10:mdroot3 UUID=... # P11 ARRAY /dev/md/mdroot4 metadata=1.0 name=srv10:mdroot4 UUID=... # P12 ARRAY /dev/md/md-srv metadata=1.0 name=srv10:md-srv UUID=... # P13 ARRAY /dev/md/md-usrl metadata=1.0 name=srv10:md-usrl UUID=... # P14 ARRAY /dev/md/md-home metadata=1.0 name=srv10:md-home UUID=... # P15 ARRAY /dev/md/md-pub metadata=1.0 name=srv10:md-pub UUID=... # P16 ARRAY /dev/md/md-isos metadata=1.0 name=srv10:md-isos UUID=... # P17 In using yast to build each md device, I took partitions in order from front to back of disks, so P08 comes from sda8 & sdb8, P09 from sda9 & sdb9, etc. In creating each md device, yast inexplicably skipped over md0 through md9, and used a range from md118 through md127, and assigned most without regard to the order given it. It gave 118 to the first, then 119 to the second, but scrambled the rest in what looks like semi-randomized inverse order: md118 = sda8 + sdb8 label: 1md08tmp md119 = sda9 + sdb9 label: 1md09root1 md120 = sda17 + sdb17 label: 1md17isos md121 = sda16 + sdb16 label: 1md16pub md122 = sda15 + sdb15 label: 1md15home md123 = sda14 + sdb14 label: 1md14usrl md124 = sda13 + sdb13 label: 1md13srv md125 = sda12 + sdb12 label: 1md12root4 md126 = sda10 + sdb10 label: 1md10root2 md127 = sda11 + sdb11 label: 1md11root3 After completing the YaST2 build process, I installed 13.1 on 1md09root1. This is the (condensed) mdadm.conf installation created, with appended the 2 sda/sdb partitions making up each device: DEVICE containers partitions ARRAY /dev/md/srv10:md-home UUID=99e6... ARRAY /dev/md/srv10:md-isos UUID=637f... # P17 ARRAY /dev/md/srv10:md-pub UUID=f825... # P16 ARRAY /dev/md/srv10:md-srv UUID=99d9... # P13 ARRAY /dev/md/srv10:md-tmp UUID=4c61... # P08 ARRAY /dev/md/srv10:md-usrl UUID=919d... # P14 ARRAY /dev/md/srv10:mdroot1 UUID=d0ef... # P09 ARRAY /dev/md/srv10:mdroot2 UUID=c37e... # P10 ARRAY /dev/md/srv10:mdroot3 UUID=b094... # P11 ARRAY /dev/md/srv10:mdroot4 UUID=5577... # P12 I'd like to get back the orderly simplicity of md0-md9 11.2's YaST2 RAID1 installation created. I don't like that yast incorporated the temporary hostname used to install either, so would like to see those gone. In order to try and get where I hope to go, I looked at the mdadm.conf man page. It makes my brain swim in confusion. Anyone know if it tells me I can, or how? Is mdadm.conf even the right place to look? Can I simply edit away the hostname portion, sort the balance into partition order, and have the boot process assign device names in predictable sequence each time? I tried rewriting mdadm.conf, using the following form: ARRAY /dev/md1 UUID=d0ef38d5:1a18ccdd:3fc41f94:5b274f89 # P09 13.1 ARRAY /dev/md2 UUID=c37e5de4:f454e44b:afe26e50:d920a464 # P10 13.2 and also rebuilding initrds via chroot. I can get the md devs recognized as md0-9 by booting something else chrooting from to use that mdadm.conf, but can't seem to get any boot process (initrd) to find any md device either by volume label or by filesystem UUID, even by having the raid modules explicit in /etc/sysconfig/kernel, or in a 13.2 installation rsync'd over from normal partition to the #3 md made from sd[ab]10. WRT 13.2, http://bugzilla.opensuse.org/show_bug.cgi?id=905863 is complicating things further. And, from 13.2 emergency shell, reboot fails, so I have to use the power/reset button to escape. :~( -- "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+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 6

[opensuse] tmp full, crash
by jdd 10 Feb '15

10 Feb '15

Hello, coming to house after two hours out, I found my 13.2 computer with kde session crashed. I could open a root terminal (full text mode), didn't find any problem, at least 35% free space anywhere (and often much more). reboot, same. No X. most operation gives "no space left on device". after several reboots without enhancement, I went to /tmp, did rm -R *... and all ice ok now. what I don't understand is why was all use space only 65%?? nothing said what can't be written. Only special thing I had was a very long upload to my online server, 30Gb total (already 2 days and approx the same to end), copy/paste with dolphin. No problem server side. thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 14

[opensuse] Re: [zypp-devel] Re: [devel] [zypper-1.11.20] NEW global option '--releasever' for distribution upgrades
by Michael Andres 10 Feb '15

10 Feb '15

On Monday 09 February 2015 23:18:24 Gerald Pfeifer wrote: > I tried this on a Factory system where I did get > > % zypper ar -f -d > http://ftp.gwdg.de/pub/linux/packman/suse/\$releasever/Essentials/ packman > Repository 'packman' successfully added > Enabled : No > Autorefresh : Yes > GPG check : Yes > URI : > http://ftp.gwdg.de/pub/linux/packman/suse/20150205/Essentials/ > > So, it seems for Factory we still should hardcode just "Factory" > instead of using "$releasever"? Yes. As the Factory naming schema differs from the OpenSUSE distro, "$releasever" is probably no benefit. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres SUSE LINUX GmbH, Development, ma(a)suse.de Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 74 053-0 +------------------------------------------------------------------+ SUSE Linux GmbH GF: Felix Imendörffer, Jane Smithard, Jennifer Guild Dilip Upmanyu, Graham Norton, HRB 21284 (AG Nürnberg) +------------------------------------------------------------------+ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] openSUSE Conference IRC meeting
by Douglas DeMaio 09 Feb '15

09 Feb '15

We will be having another openSUSE Conference IRC meeting on the opensuse-project channel on Freenode tomorrow at 1300 UTC. Cya there -- Respectfully, Douglas DeMaio douglas.demaio(a)suse.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] RE: Bug Report Zebra 2.0.60 in favour of Zebra 2.0.59 (package idzebra-2.0)
by David Cook 09 Feb '15

09 Feb '15

Hi OpenSuse folks: This is my first time interacting with OpenSuse in any way, so I'm not entirely sure how to go about it. Basically, last week I discovered a bug in Indexdata's search engine Zebra (package name idzebra-2.0). I filed the bug with Indexdata, and they released a fix as part of their 2.0.60 release of idzebra-2.0. At the moment, we're using OpenSuse 13.2 and version 2.0.59 of idzebra-2.0, which we installed using Zypper. I'm wondering what the process would be for filing a bug report to either upgrade the packages in the package repo for OpenSuse 13.2 or whether it would be possible to backport the patch. A colleague of mine at a different company recently opened a bug with Debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777515) which has all the relevant information. Basically, tokenization doesn't work correctly in Zebra 2.0.59 when using ICU indexing. Only the first token would be used after the search terms were tokenized when a hyphen existed in a search term. Indexdata only packages Zebra for Debian, Ubuntu, and Redhat, so ideally we'd like to use the packages available via the OpenSuse repos rather than building from source. Please let me know what I need to do. Thanks! David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] zypper unexpected message (virtualbox)
by jdd 08 Feb '15

08 Feb '15

I get this messags (see below). I don't really see what is this "@system" repo. It is in the view/repos of yast but not (under this name) on the repo list linux-uegt:/home/jdd # zypper lr | grep system linux-uegt:/home/jdd # what is this? thanks jdd File /lib/modules/3.16.7-7-desktop/updates/vboxdrv.ko from install of virtualbox-host-kmp-desktop-4.3.20_k3.16.7_7-7.1.x86_64(openSUSE-13.2-Update) conflicts with file from package virtualbox-host-kmp-desktop-4.3.18_k3.16.7_7-3.1.x86_64(@System) File /lib/modules/3.16.7-7-desktop/updates/vboxnetadp.ko from install of virtualbox-host-kmp-desktop-4.3.20_k3.16.7_7-7.1.x86_64(openSUSE-13.2-Update) conflicts with file from package virtualbox-host-kmp-desktop-4.3.18_k3.16.7_7-3.1.x86_64(@System) File /lib/modules/3.16.7-7-desktop/updates/vboxnetflt.ko from install of virtualbox-host-kmp-desktop-4.3.20_k3.16.7_7-7.1.x86_64(openSUSE-13.2-Update) conflicts with file from package virtualbox-host-kmp-desktop-4.3.18_k3.16.7_7-3.1.x86_64(@System) File /lib/modules/3.16.7-7-desktop/updates/vboxpci.ko from install of virtualbox-host-kmp-desktop-4.3.20_k3.16.7_7-7.1.x86_64(openSUSE-13.2-Update) conflicts with file from package virtualbox-host-kmp-desktop-4.3.18_k3.16.7_7-3.1.x86_64(@System) File conflicts happen when two packages attempt to install files with the same name but different contents. If you continue, conflicting files will be replaced losing the previous content. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 5

[opensuse] Does anyone have a good copy of xorg.conf.install?
by Aaron Digulla 08 Feb '15

08 Feb '15

Hi, After installing VirtualBox 4.3.20 from Tumbleweed yesterday, X didn't want to use my Nvidia drivers anymore. After looking into the Xorg.0.log, I noticed that X loaded vboxvideo and eventually ended up with using the VESA driver. I made nvidia-xconfig create a new xorg.conf but that was ignored. I also saw that X loads /etc/X11/xorg.conf.install So I emptied that file, copied the Device section of the new xorg.conf to /etc/X11/xorg.conf.d/50-device.conf and restarted the display-manager service. After all these changes, I finally got my desktop back in shape. Then I started hunting for the reason of the issue. My first guess was that installing VirtualBox caused it but snapper told me the file /etc/X11/xorg.conf.install was from last year. So I'm a bit puzzled what caused the problem. I also couldn't file a package which installs /etc/X11/xorg.conf.install. Does anyone have a known good copy? Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] Firefox 28 RPM
by James Knott 07 Feb '15

07 Feb '15

I want to temporarily revert to Firefox 28, but can't seem to find the RPM. Anyone know where I might find it? I need the 64 bit version. tnx jk -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 3