July 2013 - openSUSE Factory - openSUSE Mailing Lists

[opensuse-factory] pdfpc is looking for devel prj
by Mariusz Fik 10 Jul '13

10 Jul '13

Hi, I've been told to push pdfpc forward. At this moment pdfpc[1] is build in my home prj. What devel prj should I choose as new home for pdfpc package? Publishing or something with GNOME in namespace? [1] - https://build.opensuse.org/package/show/home:Fisiu/pdfpc -- Pozdrawiam / Best regards, Mariusz Fik openSUSE Community Member GPG: 5FCE 7241 B3B9 32FD 455B C30E 42D6 6C88 9E83 7C3D

2 2

Re: [opensuse-factory] Milestone #2 and nouveau driver
by Alin M Elena 09 Jul '13

09 Jul '13

I am sorry Patrick... to the downloaded .run from nvidia bash NVIDIA-Linux-x86_64-319.23.run --apply-patch /home/alin/Downloads/nvidia-3.10.patch hope helps, Alin On Tuesday 09 Jul 2013 13:53:50 you wrote: > * Alin M Elena <alinm.elena(a)gmail.com> [07-09-13 11:30]: > > I think this is the patch I used for 319.23 64 bit and kernel 3.10 > > > > I do not remember where I downloaded from... it may be was posted on the > > nvidia or arch forums... > > And for one with "Little Knowledge"(!tm), what did you apply the patch to? > Please give the command line... > > tks, -- Without Questions there are no Answers! _______________________________________________________________ Alin Marin ELENA Advanced Molecular Simulation Research Laboratory School of Physics, University College Dublin http://alin.elenaworld.net/ _______________________________________________________________ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

2 1

Re: [opensuse-factory] BtrFS Usage/Complaints
by Arvin Schnell 09 Jul '13

09 Jul '13

On Sat, Jul 06, 2013 at 06:04:50PM +0200, Jan Ritzerfeld wrote: > Am Samstag, 6. Juli 2013, 15:55:23 schrieb Arvin Schnell: > > On Sat, Jul 06, 2013 at 02:18:44PM +0200, Jan Ritzerfeld wrote: > > > TIMELINE_LIMIT_* does not: > > > TIMELINE_LIMIT_HOURLY=5 keeps the last five snapshots and not only five > > > hourly snapshots per day. And although I set TIMELINE_LIMIT_DAILY=5 and > > > the rest 0, there are still snapshots made eight days ago (five hourly > > > and five daily). > > > > Could be because the cleanup algorithm only runs once a day. > > [...] > > Hmm, no. I manually did a "snapper cleanup timeline". > ATM, I am looking at client/cleanup.cc. And the code indeed does what I > observed. do_cleanup_timeline fetches a full list of timeline snapshots and > then removes the ones that should be kept. The remaining snapshots will be > deleted: > > if (num_hourly < limit_hourly && is_first_hourly(it, tmp.end(), *it)) > { > ++num_hourly; > it = tmp.erase(it); > } > else if (num_daily < limit_daily && is_first_daily(it, tmp.end(), *it)) > { > ++num_daily; > it = tmp.erase(it); > } > else if... > > Obviously, if all snapshots are both the first hourly and the first daily, > they will be only counted for the hourly limit. This is wrong, because you > will get "limit_daily" additional snapshots (if there are enough left). The > same holds true for monthly and yearly. > The correct code would be little bit more complicated: > > bool keep = false; > if (num_hourly < limit_hourly && is_first_hourly(it, tmp.end(), *it)) > { > ++num_hourly; > keep = true; > } > if (num_daily < limit_daily && is_first_daily(it, tmp.end(), *it)) > { > ++num_daily; > keep = true; > } > if (num_monthly < limit_monthly && is_first_monthly(it, tmp.end(), *it)) > { > ++num_monthly; > keep = true; > } > if (num_yearly < limit_yearly && is_first_yearly(it, tmp.end(), *it)) > { > ++num_yearly; > keep = true; > } > if (keep) > { > it = tmp.erase(it); > } > else > { > ++it; > } The result of the modified code is indeed easier to understand. I have changed snapper and also added a manpage snapper-configs(5). Regards, Arvin -- Arvin Schnell, <aschnell(a)suse.de> Senior Software Engineer, Research & Development SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Status: Distribution
by Stephan Kulow 09 Jul '13

09 Jul '13

Hi, Friday I switched to gcc 4.8 and triggered a full rebuild of openSUSE:Factory and yesterday we integrated KDE 4.11 beta. What bothers me at the moment are broken live cds and the fact that I didn't have working DVDs for the last weeks. I still hope we can have M3 this week though. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 2

[opensuse-factory] Submitting python-construct and python-pybeam to Factory.
by Matwey V. Kornilov 09 Jul '13

09 Jul '13

This message is to introduce two packages which are being sent to Factory. python-construct is required by python-pybeam python-pybeam is required by https://github.com/openSUSE/rpmlint-checks/pull/2 (rpmlint) and is being sent to Factory in order to provide dependencies to this pull-requrest. python-construct description is located at its package page at OBS: https://build.opensuse.org/package/show/devel:languages:python/python-const… Summarizing, python-construct is declarative binary data parser for Python, able to parse such things like Ext2fs, Fat, ELF binaries, and so on. python-construct may be interesting not only as requirement for python-pybeam, but as powerful python module for people dealing with binary data format and network protocols. python-pybeam is Erlang VM BEAM format parser, based on python-construct module. python-pybeam makes it possible to do deep inspection of BEAM executable files. Initial purpose for python-pybeam was to implement rpmlint checks for erlang packages. The author of python-pybeam is one of the maintainers of devel:languages:erlang. Brief description of pull request #2 to openSUSE/rpmlint-checks: It adds two basic rpmlint checks for erlang packages. Proposed enhancements have been tested in home:matwey:erlang -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] normal? or bug? renaming config->config.save when no changes
by Linda Walsh 07 Jul '13

07 Jul '13

I don't remember this _always_ being the case (occasionally), but not usually. But now 90% of the time I'm seeing ".rpmsave" files that are identical (including date/time) to the ones added. In some cases, I'm 75-80% sure I've made some change, but that change is gone and it's not in the rpmsave file (a few cases, I know it's changed where I keep an RCS dir to manage changes). I thought rpm only saved off rpmsave files when it had a different MD5sum than the original rpm stated? Has that changed or was that a random property of each rpm package or what? I sure preferred the old method of not creating rpmsave files for files that haven't changed only creating rpmsave or similar when there was a user change. What it boils down to is there are 100's of configs, most of which I know nothing about and if they were to change, I wouldn't know if it was good or bad, so I assume good. I'm really only interested where I had to customize something and then something replaces my customized copy. Then I have to look to see if it is still useful or valid...etc.. So...did something change? If it is random, could something change to make the process more regular -- and only create 'old' files when they've been altered -- AND also, if they are different... (have a bunch of rpmsave files in my font dir that are identical to the new ones...)... Simple enough to fix w/a script, but still ... is it possible to not create them in the first place? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

[opensuse-factory] Any thoughts about openSUSE creating their own font for the desktop environment, wiki and forums
by Roman Bysh 07 Jul '13

07 Jul '13

Hello List mates, Has any one thought about openSUSE creating their own font type for their desktops wiki and forums. Ubuntu, Mac and $Microsoft use their own style. Cheers! Roman ------------------------------------------------------- openSUSE -- Get it! Discover it! Share it! ------------------------------------------------------- http://linuxcounter.net/ #179293 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

4 9

[opensuse-factory] Mismatch in Tumbleweed kernel files
by Vahis 07 Jul '13

07 Jul '13

The kernel and source, as well as other stuff is not same version, 3.9.8-15-1 and 3.9.8-15-2. -- Vahis -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

3 8

Re: [opensuse-factory] BtrFS Usage/Complaints
by Claudio Freire 07 Jul '13

07 Jul '13

On Sat, Jul 6, 2013 at 5:26 PM, Jan Ritzerfeld <suse(a)mailinglists.jan.ritzerfeld.org> wrote: >> But if you were >> focused on saving snapshots, what snapper does is exactly fine. >> [...] > > I also focus on saving snapshots. You could use the same logic as me to say > that there must be never more than "limit_hourly" snapshots in total. That > is because every first daily, first monthly, and first yearly snapshot is an > hourly, too. But my proposed code will not do that. But then it's not an hourly limit, it's just limit. So, limit_hourly works as intended, you want an hypothetical limit_total. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0

Re: [opensuse-factory] BtrFS Usage/Complaints
by Claudio Freire 06 Jul '13

06 Jul '13

On Sat, Jul 6, 2013 at 1:04 PM, Jan Ritzerfeld <suse(a)mailinglists.jan.ritzerfeld.org> wrote: > Obviously, if all snapshots are both the first hourly and the first daily, > they will be only counted for the hourly limit. This is wrong, because you > will get "limit_daily" additional snapshots (if there are enough left). The > same holds true for monthly and yearly. I don't think that's wrong. You're biased because you're focused on saving space. But if you were focused on saving snapshots, what snapper does is exactly fine. You probably want 0 daily and 0 monthly. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org

1 0