[Bug 1197512] New: Failed to remove file on linked package from linked projects
http://bugzilla.opensuse.org/show_bug.cgi?id=1197512 Bug ID: 1197512 Summary: Failed to remove file on linked package from linked projects Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: BuildService Assignee: screening-team-bugs@suse.de Reporter: ralf.habacker@freenet.de QA Contact: adrian.schroeter@suse.com Found By: --- Blocker: --- Created attachment 857358 --> http://bugzilla.opensuse.org/attachment.cgi?id=857358&action=edit Screenshot 1 I have linked the project windows:mingw:win32 with home:rhabacker:linkedprojecttest The project meta data is as: <project name="home:rhabacker:linkedprojecttest"> <title>Testproject to show issues with linked projects</title>. <description/> <link project="windows:mingw:win32"/> <person userid="rhabacker" role="maintainer"/> <build> <disable/> </build> <publish> <disable/> </publish> <repository name="openSUSE_Leap_15.3" linkedbuild="all"> <path project="windows:mingw:win32" repository="openSUSE_Leap_15.3"/> <path project="windows:mingw" repository="openSUSE_Leap_15.3"/> <arch>x86_64</arch> </repository> </project> I checked out the package mingw32-expat with osc, updated the package to a newer version by replacing the tarball and ran osc ci. osc asked me if I wanted to create a local branch, which I confirmed. Some of the packages are links to another project! Create a local branch before committing? (y|N) y Branching mingw32-expat from windows:mingw:win32 to home:rhabacker:linkedprojecttest Delete expat-2.2.4.tar.bz2 Deleting mingw32-expat-2.2.4-rpmlintrc Sending mingw32-expat.changes Shipping mingw32-expat.spec Shipping expat-2.4.7.tar.xz Sending mingw32-expat-rpmlintrc File data transfer .... Transmitted revision 2. In the project view, the package was moved from the "inherited packages" list to the "packages" list (see attached screenshot). The problem is that this project is not linked to the original package, although it was branched. After I added a link afterwards with osc linkpac windows:mingw:win32 mingw32-expat home:rhabacker:linkedprojecttest mingw32-expat the old tarball is still included and cannot be deleted (see screenshot 2). Even clicking on the diff link does not show that the original tarball has been removed. The link points to the latest file <link project="windows:mingw:win32" package="mingw32-expat"> <patches> <!-- <branch /> for a full copy, default case --> <!-- <apply name="patch" /> apply a patch on the source directory --> <!-- <topadd>%define build_with_feature_x 1</topadd> add a line on the top (spec file only) --> <!-- <add name="file.patch" /> add a patch to be applied after %setup (spec file only) --> <!-- <delete name="filename" /> delete a file --> </patches> </link> -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197512 http://bugzilla.opensuse.org/show_bug.cgi?id=1197512#c1 --- Comment #1 from Ralf Habacker <ralf.habacker@freenet.de> --- Created attachment 857359 --> http://bugzilla.opensuse.org/attachment.cgi?id=857359&action=edit Screenshot showing linked package -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197512 Ralf Habacker <ralf.habacker@freenet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://build.opensuse.org/ | |package/show/home:rhabacker | |:linkedprojecttest/mingw32- | |expat -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197512 http://bugzilla.opensuse.org/show_bug.cgi?id=1197512#c2 --- Comment #2 from Ralf Habacker <ralf.habacker@freenet.de> --- As a test I linked another package first with $ osc linkpac windows:mingw:win32 mingw32-freetype home:rhabacker:linkedprojecttest then checked it out with osc co, modified it and checked it in again with osc ci. In this case the problem does not occur. The difference is that in this case the _link file contains the deleted files as patches: <link project="windows:mingw:win32" package="mingw32-freetype" baserev="c1e13cf1c1f60a14cd507945f48ffef9"> <patches> <delete name="freetype-2.4.12-pkgconfig.patch"/> <delete name="freetype-2.4.12.tar.bz2"/> <delete name="freetype-doc-2.4.12.tar.bz2"/> <apply name="project.diff"/> </patches> </link> From this follows that with the described creation of the branched project the creation of the _link file does not work. For testing, osc was used with the following version: $osc --version 0.172.0 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197512 Ralf Habacker <ralf.habacker@freenet.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Failed to remove file on |Failure to create link when |linked package from linked |branching packages from |projects |linked projects -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197512 http://bugzilla.opensuse.org/show_bug.cgi?id=1197512#c3 --- Comment #3 from Ralf Habacker <ralf.habacker@freenet.de> --- (In reply to Ralf Habacker from comment #2)
From this follows that with the described creation of the branched project the creation of the _link file does not work.
Correction: From this follows that with the described creation of the branched package the creation of the _link file does not work. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1197512 http://bugzilla.opensuse.org/show_bug.cgi?id=1197512#c4 --- Comment #4 from Ralf Habacker <ralf.habacker@freenet.de> --- (In reply to Ralf Habacker from comment #0)
The problem is that this project is not linked to the original package, although it was branched.
This issue is still present. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com