Public bug reported:

[Impact]
The script/is_rust_module.sh has been removed with commit "UBUNTU: SAUCE: 
scripts: rust: drop is_rust_module.sh" (LP: #2007654). But the 
debian.master/reconstruct is not updated for this.

Consequently we will see this error message when running "fakeroot debian/rules 
clean" command:
chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory

We didn't notice this as this is not a show-stopper.

[Fix]
Remove corresponding lines from debian.master/reconstruct

[Test Plan]
Run "fakeroot debian/rules clean" and this error message should not exist 
anymore.

[Where problems could occur]
Removing command line operation on a non-existing file, this should not cause 
any regression.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Fix Released

** Affects: linux (Ubuntu Lunar)
     Importance: Undecided
     Assignee: Po-Hsu Lin (cypressyew)
         Status: In Progress

** Affects: linux (Ubuntu Mantic)
     Importance: Undecided
         Status: Fix Committed

** Affects: linux (Ubuntu Noble)
     Importance: Undecided
         Status: Fix Released

** Also affects: linux (Ubuntu Noble)
   Importance: Undecided
     Assignee: Po-Hsu Lin (cypressyew)
       Status: New

** Also affects: linux (Ubuntu Mantic)
   Importance: Undecided
       Status: New

** Also affects: linux (Ubuntu Lunar)
   Importance: Undecided
       Status: New

** Changed in: linux (Ubuntu Lunar)
     Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

** Changed in: linux (Ubuntu Lunar)
       Status: New => In Progress

** Changed in: linux (Ubuntu Mantic)
       Status: New => In Progress

** Changed in: linux (Ubuntu Noble)
       Status: New => In Progress

** Description changed:

  [Impact]
- The script/is_rust_module.sh has been removed. But the 
debian.master/reconstruct is not updated for this.
+ The script/is_rust_module.sh has been removed with commit "UBUNTU: SAUCE: 
scripts: rust: drop is_rust_module.sh" (LP: #2007654). But the 
debian.master/reconstruct is not updated for this.
  
- Therefore we will see this error message when running "fakeroot debian/rules 
clean":
+ Consequently we will see this error message when running "fakeroot 
debian/rules clean" command:
  chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory
  
- As this is not a show-stopper, it can be easily ignored.
+ We didn't notice this as this is not a show-stopper.
  
  [Fix]
  Remove corresponding lines from debian.master/reconstruct
  
  [Test Plan]
  Run "fakeroot debian/rules clean" and this error message should not exist 
anymore.
  
  [Where problems could occur]
- Removing command line operation on non-existing file, this should not cause 
any regression.
+ Removing command line operation on a non-existing file, this should not cause 
any regression.

** Summary changed:

- Update debian.master/reconstruct for is_rust_module.sh removal on L/M 
+ Update debian.master/reconstruct for is_rust_module.sh removal on L

** Changed in: linux (Ubuntu Mantic)
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2045636

Title:
  Update debian.master/reconstruct for is_rust_module.sh removal on L

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Lunar:
  In Progress
Status in linux source package in Mantic:
  Fix Committed
Status in linux source package in Noble:
  Fix Released

Bug description:
  [Impact]
  The script/is_rust_module.sh has been removed with commit "UBUNTU: SAUCE: 
scripts: rust: drop is_rust_module.sh" (LP: #2007654). But the 
debian.master/reconstruct is not updated for this.

  Consequently we will see this error message when running "fakeroot 
debian/rules clean" command:
  chmod: cannot access 'scripts/is_rust_module.sh': No such file or directory

  We didn't notice this as this is not a show-stopper.

  [Fix]
  Remove corresponding lines from debian.master/reconstruct

  [Test Plan]
  Run "fakeroot debian/rules clean" and this error message should not exist 
anymore.

  [Where problems could occur]
  Removing command line operation on a non-existing file, this should not cause 
any regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045636/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to