SLE 11 SDK

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

SLE 11 SDK

vetter
Hi,
I'm trying to build partclone
(https://build.opensuse.org/project/show/home:asvetter:branches:filesystems)
for SLE_11_SP{2,3}.
OBS says:
nothing provides ntfs-3g = 2011.4.12 needed by ntfs-3g-devel

In the ISO-image of SLE11-SDK-SP3 both  ntfs-3g and ntfs-3g-devel are at
the same level:

zypper se -s ntfs-3g
Loading repository data...
Reading installed packages...

S | Name          | Type       | Version         | Arch   | Repository
--+---------------+------------+-----------------+--------+------------------
i | ntfs-3g       | package    | 2011.4.12-0.7.8 | x86_64 | SLE11-SDK-SP3-BOX
   | ntfs-3g       | srcpackage | 2011.4.12-0.7.8 | noarch | SLE11-SDK-SP3-BOX
   | ntfs-3g-devel | package    | 2011.4.12-0.7.8 | x86_64 | SLE11-SDK-SP3-BOX

Am I doing something wrong, or is it a problem in OBS?
--
Mit freundlichen Gruessen,
   Andreas Vetter
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: SLE 11 SDK

Srinidhi B
 >>> On 7/25/2013 at 06:46 PM, Andreas Vetter <[hidden email]>
wrote:
> Hi,
> I'm trying to build partclone
> (https://build.opensuse.org/project/show/home:asvetter:branches:filesystems)
>
> for SLE_11_SP{2,3}.

Small correction, you are building against SLE_11_SP{2,3} repositories defined in "filesystems" project. Which means, if a package is available in "filesystems" project, then it will take precedence over what is available in base distribution.

> OBS says:
> nothing provides ntfs-3g = 2011.4.12 needed by ntfs-3g-devel
>

In "filesystems" project, you have ntfs-3g-2013.1.13 available:

$ osc ls -b filesystems ntfs-3g_ntfsprogs -r SLE_11_SP2 -a x86_64
_statistics
libntfs-3g-devel-2013.1.13-27.3.x86_64.rpm
libntfs-3g84-2013.1.13-27.3.x86_64.rpm
ntfs-3g-2013.1.13-27.3.x86_64.rpm
ntfs-3g_ntfsprogs-2013.1.13-27.3.src.rpm
ntfs-3g_ntfsprogs-debuginfo-2013.1.13-27.3.x86_64.rpm
ntfs-3g_ntfsprogs-debugsource-2013.1.13-27.3.x86_64.rpm
ntfsprogs-2013.1.13-27.3.x86_64.rpm
rpmlint.log

So this package will take precedence over what is available in SUSE:SLE-11:SP2 repository in OBS. Also note that there is no "ntfs-3g-devel", it is now libntfs-3g-devel.

Hope this helps,
Srinidhi.

> In the ISO-image of SLE11-SDK-SP3 both  ntfs-3g and ntfs-3g-devel are at
> the same level:
>
> zypper se -s ntfs-3g
> Loading repository data...
> Reading installed packages...
>
> S | Name          | Type       | Version         | Arch   | Repository
> --+---------------+------------+-----------------+--------+------------------
> i | ntfs-3g       | package    | 2011.4.12-0.7.8 | x86_64 | SLE11-SDK-SP3-BOX
>    | ntfs-3g       | srcpackage | 2011.4.12-0.7.8 | noarch | SLE11-SDK-SP3-BOX
>    | ntfs-3g-devel | package    | 2011.4.12-0.7.8 | x86_64 | SLE11-SDK-SP3-BOX
>
> Am I doing something wrong, or is it a problem in OBS?
 



--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: SLE 11 SDK

gregfreemyer
On Thu, Jul 25, 2013 at 9:45 AM, Srinidhi B <[hidden email]> wrote:
>  >>> On 7/25/2013 at 06:46 PM, Andreas Vetter <[hidden email]>
> wrote:
>> Hi,
>> I'm trying to build partclone
>> (https://build.opensuse.org/project/show/home:asvetter:branches:filesystems)
>>
>> for SLE_11_SP{2,3}.
>
> Small correction, you are building against SLE_11_SP{2,3} repositories defined in "filesystems" project. Which means, if a package is available in "filesystems" project, then it will take precedence over what is available in base distribution.

You can see that in your repository list:
https://build.opensuse.org/project/repositories/home:asvetter:branches:filesystems

Each one has a reference to filesystems.

You could build against a pure SLE_11_SP3 by adding it as an
additional repo via the "Add repositories" button on that same page
(at the end of the list of repos).

The question you need to decide is if you are trying to build
something truly for SLE released versions, or are you building for a
future release.

If it is for a future release, then the filesystems repos are the
right ones since that is where development takes place.

If it is for the already released versions, then you should probably
just branch your package straight from the SLE repo of choice.  That
is how the maintenance cycle works as an example.  The branches are
made directly from the release repos, not from the devel repos.

Greg
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: SLE 11 SDK

vetter
On Thu, 25 Jul 2013, Greg Freemyer wrote:

> On Thu, Jul 25, 2013 at 9:45 AM, Srinidhi B <[hidden email]> wrote:
>> >>> On 7/25/2013 at 06:46 PM, Andreas Vetter <[hidden email]>
>> wrote:
>>> Hi,
>>> I'm trying to build partclone
>>> (https://build.opensuse.org/project/show/home:asvetter:branches:filesystems)
>>>
>>> for SLE_11_SP{2,3}.
>>
>> Small correction, you are building against SLE_11_SP{2,3} repositories defined in "filesystems" project. Which means, if a package is available in "filesystems" project, then it will take precedence over what is available in base distribution.
>
> You can see that in your repository list:
> https://build.opensuse.org/project/repositories/home:asvetter:branches:filesystems
>
> Each one has a reference to filesystems.
>
> You could build against a pure SLE_11_SP3 by adding it as an
> additional repo via the "Add repositories" button on that same page
> (at the end of the list of repos).
>
> The question you need to decide is if you are trying to build
> something truly for SLE released versions, or are you building for a
> future release.
>
> If it is for a future release, then the filesystems repos are the
> right ones since that is where development takes place.
>
> If it is for the already released versions, then you should probably
> just branch your package straight from the SLE repo of choice.  That
> is how the maintenance cycle works as an example.  The branches are
> made directly from the release repos, not from the devel repos.
>
> Greg
>
Thank you Srinidhi and Greg. I didn't spot the filesystems part in the
Repos.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]