Libcdio seems to no longer need it's boot strap package libcdio-mini so I've removed it from multimedia:libs and once the vcdimager test
suite issue has been sorted this change and the major abi changes of the libcdio libraries will make their way to factory next week
sometime. Most packages that play CDs may be affected and also packages that access the` cddb.
BTW my list emails are coming in now.
Dave
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
I thought I might give advance warning that I've updated and removed the need for libcdio-mini in the libcdio package and am about to
submit it to multimedia:libs. I'm also submitting a vcdimager with the test suite disabled as it fails with the updated libcdio but I need
it in multimedia:libs to confirm that there isn't a dependency loop any more. I've already tested this in my home project so it shouldn't
cause any havoc except maybe packages that use vcdimager's libvcdinfo0.
I no longer have the email address that I receive list mail on and am attempting to subscribe with my new list email but the first attempt
failed so please cc my davejplater(a)gmail.com (a nomail account) with any replies.
Dave
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi all,
I have several years linux distribution development skills.I can do some
distribution development jobs.I can do packaging,bash script,python,etc
How can I contribute to opensuse?
Thanks.
flash yan
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
GNOME:Cinnamon currently provides cinnamon 1.4.0 and muffin 1.0.2.
With GNOME 3.4 going to factory the current upstream base code needs
adjustments and it's still unclear to me how upstream is going to fix
a few pending issues.
My belief is that there should be a 1.4 kinda of 'branch' to keep some
maintenance updates for 12.1 / Tumbleweed and some sort of 'trunk' to
keep going and fix the Factory Builds. One good example would probably
be to keep a G:Cinnamon:Factory for active development and devel for
Factory and a general G:Cinnamon to store builds.
Now this raises a few questions:
1) Create a new sub-structure inside G:Cinnamon like on G:STABLE:MAJOR ?
2) disable builds for a given platform and keep going ?
3) Any other ?
Please leave suggestions even from the 'end user' point to view...
consider simplification, avoiding doubled tasks in maintenance, etc
etc.
NM
--
Nelson Marques
// I've stopped trying to understand sandwiches with a third piece of
bread in the middle...
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi,
accountsservice is the service used in GNOME to get info about accounts
on the system. The latest release change the way user filtering works.
See https://bugs.freedesktop.org/show_bug.cgi?id=44408
Quick summary:
- before 0.16.6: we were filtering out users based on UID (do not show
users if uid < UID_MIN, where UID_MIN icomes from /etc/login.defs)
- now: we're filtering out users based on the shell (nologin & false
are hidden)
On top of that, we have a blacklist of users to never show.
That sounds reasonable except that now I see users in gdm, while they
should be filtered out. Those are:
ftp:x:40:49:FTP account:/srv/ftp:/bin/bash
games:x:12:100:Games account:/var/games:/bin/bash
man:x:13:62:Manual pages viewer:/var/cache/man:/bin/bash
suse-ncc:x:106:108:Novell Customer Center User:/var/lib/YaST2/suse-ncc-fakehome:/bin/bash
beagleindex:x:108:111:User for Beagle indexing:/var/cache/beagle:/bin/bash
I guess ftp, games and man are provided by some base package. Is there
any reason those are using bash as shell instead of nologin? Can we fix
this? Or should we just blacklist them?
It's harder for suse-ncc and beagleindex as, as far as I know, those
are purely historical users from older versions of openSUSE that are
still there after upgrading. So I wonder what the right fix is: should
we just blacklist them, or would it be acceptable to change their shell
in %post of accountsservice? That last solution sounds wrong to me, but
it also might fix other issues in the long term...
Thanks,
Vincent
--
Les gens heureux ne sont pas pressés.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org